Would anyone know why UniqueItems sometimes would not filter some items?
The values coming inside the list node of the GetItemAtIndex are Y values from points calculated by Dynamo.
If you have any idea this happens or a solution to troubleshoot this issue that would help me a lot.
After posting I was trying to make it work using strings but there is something else that is being messed up afterward.
=> The output is then used as an item in a “List.AllIndicesOf” that does not seem to understand the new items input I guess. (I tried to turn back the items to number with “String.ToNumber” still messing the rest of the nodes)
I built the node sequence and code in a much smaller file to reuse it in a much bigger project. In the smaller file, it works perfectly no problem.
It only happens in the 130k item program.
I never used python I am going to give it a try right now, and keep you updated
It is possible to share but everything is extracted from a mesh file. (format unsupported to share by the forum) So I have to find a way to share this OBJ.
And the Dyn file contains a lot of code /nodes (I don’t know how crowded other dynamo users’ files usually are…)
@mzjensen the run seems to have run correctly though I got a negative indices error notification at the last GetItem (probably a level or lacing issue I think). Due to the list it was treating, it took about 2hrs to run, so I did not correct and tried the Rounding idea.
@paris@Kulkul@SeanP Rounding worked perfectly. It took slightly more time than without but corrected all the errors!
Thank you to each one of you for your time and knowledge sharing ! Greatly appreciated