BHoM / BHoM/BHoM_Engine

Geometry_Engine: Treatment of tolerances descriptions

Open
#1,774 0 comments 0 reactions 0 assignees View on GitHub
type:question
Dominant language
C#
Stars
30
Forks
13
Avg merge
7d 10h
Merged PRs (30d)
5

Description

Following discussion @al-fisher @pawelbaran @IsakNaslundBh

Tolerances are fun in many ways, two main questions

### The extent of descriptions for tolerances
What does the user and/or developer need to know from a tolerance description
- How descriptive should it be of what happens with the value?
1. General use of it
2. Which methods it's used for
3. What those methods do with it
4. Suggestions for different uses

The two ends of this one seems to be,
to general and there's no point to them and to specific will both be a big load now and to keep up to date in the future.

### The format of descriptions for tolerances
There are different kinds of tolerances, noteworthy in Geometry is numerical and geometrical ones
Should we add something along the lines of the quantities types for different kinds of tolerances to get a standardised base description on tolerance inputs?

This would also centralise the main description for a geometrical tolerance and help with sanity for tolerance descriptions.

related to #1773

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.