How to filter locations?

[wesserbro]

Hi! I want to pass locations further only if their weights match certain conditions.
"get Self.PointNeighbors" //got location array of n neighbors -> MAGIC -> array of n-x filtered locations
Is it possible?

[Bullit]

You have to put the values of what you want to test and conditions i think.

[Mathaeus]

As Bullit said, there should be small setup for filtering. There's one in factory 'Get Neighboring Particles', used to exclude the 'self' searching point, should be easy to adapt it for something else. So, something based on 'Find In Array' node.
By the way, you can put an array as an searching input in some other geo queries too, like Raycast, or Get CLosest Location - in this case they will return the array, too. Let's say if you want to simulate ambient occlusion with ray casting. Or, to test some volume by looking from long array in 3d space, of 'probe points', using Get Closest Location.

[wesserbro]

Is this setup right?

I will be able to see if it works only after much more complex setup...
I'm not quite sure how ICE internally loops through arrays. May be it just passing one location per ICEtree execution....

[rray]

something like this shoud work, it returns an array of only those weights that are > 0.5 (using the "find in array" as Mathaeus suggested)

[wesserbro]

Right, we find indexes in weights array, then select by those indexes from location array. Stupid me!
Thanks, guys!

P.S. I'm trying to make directional tension map. Like you paint weights every other edge loop, which define "direction". And then known tension algorithm is modified to take average only from the neighbors with the same weight value, so only the stretch along the "direction" counts.

[rray]

That's a really cool application, you could even have different weightmaps and tension maps that way. I was doing that some time ago using an edge cluster but the look up whether points are connected by the cluster wasn't so nice (get edge neighbors, filter by cluster, get points of those edges, filter away current point and some more) ..weightmap approach is better because you have more control (if you paint everything gray you'll have a normal tension effect)

[Pooby]

I did one of these, but I didn't use neighbours, I just stored a location that was along the correct direction and compared its distance as the mesh stretched.
This way you're not evaluating larger arrays and dropping redundant values, you're just placing the one (or two) you intend to use.

[wesserbro]

Who would doubt the most sensible solution will come from Pooby )
By the way, Paul, where can we see your character work in production? Want to see your non-disclosable ICE muscles in action)