Evaluate component doesn't work as expected

[Michael_Pryor (ekim)]

Read these

Is one one?

Panel output = A String (text). The text 1 = the text 1 that you are testing against. The output of absolute value reads as 1 but is likely some floating point number behind the scenes. The issue here is tolerance vs decimal display. You should test in this case if Abs|A-B| < tolerance (it is good practice to always do that anyway, in scripting as well) The real culprit here in tricking you is this option in File > Preferences > Display called “Special Case Integers” which you may want to turn…

Same parameters, different curves

Precision and floating point error. You can change the amount of decimals in grasshoppers settings. File>Preferences>Display. [Capture] For instance change it to 2 and you can get. [Capture2] However this will still give you issues with components like equality which use the actual numbers. [Capture3] Which is why you should always check things like equality between numbers with a tolerance. You can see ways to do that here: EQUALS component not working Side note, you don’t need to rep…

What's the trouble with this expression (if..)?

It is no mystery https://docs.oracle.com/cd/E19957-01/806-3568/ncg_goldberg.html It is pretty common knowledge in computational design, engineering, architecture, etc. you should consider everything as tolerance based, not absolute. Even Rhino itself is tolerance based (See Options>Units in Rhino to see your tolerances). Long story short, unless you are using integers, never ask if A=B, always ask if abs(A-B)<tolerance