-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature] Tolerance in cable lengths #306
Comments
It would be nice if this didn't require an additional key/value in the YAML, but if it could be parsed within the Some suggestions for YAML input: length: 100 # assume default unit
length: 200 mm # explicit unit
length: 300 ±5 mm # place unit before or after tolerance? allow both?
length: 400 +-5 mm # allow +- instead of ± for easier input
length: 500 +5 -0 # allow asymmetric tolerance
length: 600 ±10% # allow percentages?
# show as percentage in output or do the math?
# maybe as a second step later on
length: 700~750 # allow length range? |
How should similar entries with such lengths be summed up in the BOM?
If specifying length range is allowed as input - hence no nominal specified, then only the latter alternative above might be possible. If different lengths in #268 also will be implemented, then care must be taken how to present that combined with different length tolerances for each length. |
BOM should probably show a sum of nominal lengths. The last possibility (specifying a length range without a singular nominal length, e.g. Tolerances (sum of positives, sum of negatives) could become their own column in the BOM, but it might be overkill to actually display them? |
Yes, I guess that's what most users would expect.
It's also possible to define a length range input to be regarded as equal to a nominal length = range middle and ±tolerance = half range length - e.g.
I guess tolerance columns in BOM could be optional, e.g. like this:
|
Hi there,
My name is Diogo. So often manufacturers ask to include tolerances in the cable lengths. I think it would make sense to have a key/value for that. The way I've implemented that was by mostly cloning the length key... The only change I did in that was to inherit the units from the length if none is provided instead of assuming 'm' like length does. Ideally, it would process different tolerances like -10mm and +15mm, but I did not have time to mess with that.
Let me know if you want any help implementing that.
Best regards,
DIogo
The text was updated successfully, but these errors were encountered: