Tolerance issue?

Replies to This Discussion

Permalink Reply by MarcGrasshopper on March 27, 2017 at 11:07am

Maybe if you post your definition as a grasshopper file...

Permalink Reply by Joseph Oster on March 27, 2017 at 11:15am

Without being able to examine your code, there is no way to tell from the image if the data is as implied.  It truly baffles me that so many expect so much from so little (screen shots or text descriptions instead of code/data!)?

Permalink Reply by Aristo Compasso on March 27, 2017 at 3:00pm

GH definition

Attachments:

• 170327_definitionSections.gh, 38 KB

Permalink Reply by MarcGrasshopper on March 27, 2017 at 4:38pm

It seems to be a tolerance issue, but you can solve it by explicitly declaring everything as an integer. Then it will work both with a 'member index' as 'equality'. But I have to agree, it is a little bit weird...

Attachments:

• 170327_definitionSections.gh, 43 KB

Permalink Reply by Joseph Oster on March 27, 2017 at 5:26pm

It looks peculiar, especially since using 'Similar' instead of 'Equals' makes no difference!

There are anomalies in the data though:

Interesting to see that this code works with your raw data (points):

http://www.grasshopper3d.com/forum/topics/set-member-index-example-...

Attachments:

• definitionSections_2017Mar27.gh, 49 KB

Permalink Reply by Hyungsoo Kim on March 28, 2017 at 3:14am

Hi. Aristo.

It's one of recurrently asked question and obviously one of tolerance issue.

Please refer to "here" for a detailed explanation.

The same numbers on the panel may not be the same.

By using the formatting pattern {0:R}, you can see the number without any rounding.

Attachments:

• 170327_definitionSections_re.gh, 46 KB

Permalink Reply by Aristo Compasso on March 28, 2017 at 3:39am

Thanks all for your tips in troubleshooting. I'll have to keep tolerances in mind when dealing with selections in the future.