Data is being remapped by component inconsistently, why?

[bureauproberts (BPParametric)]

Hi all! I have an issue with a cluster which outputs data mapped inconsistently and I don’t know why.

Same Cluster later within the same definition, different geometry but same data structure and I get this

Can you please help? I have no idea what’s going on

Cheers

Gio

[bureauproberts (BPParametric)]

I applied a Data Match component to fix the remapping issue and I think I found the culprit- the PointInCurve Component is not working properly, returning all points as outside of the region- which still does not explain why the data is being remapped… Can someone kindly suggest a workaround for this point in curve issue/bug? Cheers

[inno]

please post your gh file with internalized geometry as example

[bureauproberts (BPParametric)]

Hi Inno I must apologize, the project is confidential and I am not authorized to share files. I think there may be a bug affecting the point in curve component, apparently it’s a thing

Point In Curve Bug

Point in Curve Bug.gh (3.7 KB) Point in Curve Bug.3dm (39.3 KB) [image] I just discovered a weird bug where a point is not registering as “inside” a curve. If the point is moved at all, it registers as “inside”. Already tried projecting everything to a common plane, checking for closed curves, etc. While I’ve never found/noticed this before, it happened in 4 cases on a single scope of a single project. Not an issue this time, but could be in other cases if Point In Curve component is fo…

[inno]

I don’t see problems with the Point in Curve component as for today (I’m on V8 SR17 8.17.25056.13001, 2025-02-25)

knowing you can’t post gh files, if I had to guess where the problem is in this screenshot, my best guess would be a data tree problem (not a Component bug), specifically happening in this case when ALL the branches in A have a path starting with {8; …}

Simplify removes the overlap shared among ALL branches, so if they all identically start with {8; something_else} simplifying the output would result into just {something_else} like in the screenshot

I’d remove this Simplify and see how it goes:

[bureauproberts (BPParametric)]

Hi Inno, thank you for your response. I think it had to do with the splitter input curve. If I work with a simple rectangle I get the data structure I want- like in the example

The index of the first number is not always 8, it goes from 0 to 1500 something, but thank you for that suggestion, you increased my understanding of the simplify operation. As you can see the data was already simplified prior to tree stat so in theory the 8 shoud’ve vanished.

I ended up flattening the tree because I found I actually dont need the tree structure and working in smaller segments and so far with rectangular shapes it’s working perfectly. Thank you!