tyFlow Forum
"Event Age" Option: Only process INCOMING particles (for Voronoi etc. important) - Printable Version

+- tyFlow Forum (https://forum.tyflow.com)
+-- Forum: tyFlow Discussion (https://forum.tyflow.com/forum-1.html)
+--- Forum: Feature Requests (https://forum.tyflow.com/forum-4.html)
+--- Thread: "Event Age" Option: Only process INCOMING particles (for Voronoi etc. important) (/thread-4499.html)



"Event Age" Option: Only process INCOMING particles (for Voronoi etc. important) - Alexx31 - 10-01-2024

Hello,

I want to set a certain event age only for INCOMING particles, not for particles new born inside the event itself.

Example: If I have a Voronoi on Event Age I don't want it to process it's own fragments again.
Especially as small mistakes here can cause many minutes of waiting time and crashes.

Please see Screenshots with NOTES in the event.

Many thanks

         
It should be the same amount of particles possible with both evaluation methods.


RE: "Event Age" Option: Only process INCOMING particles (for Voronoi etc. important) - tyFlow - 10-03-2024

Add a Custom Properties operator after the Voronoi operator and have it assign a non-zero value to some channel. Then enable a filter in your Voronoi Fracture operator that causes it to only process particles with a zero value in that channel. Or just send the fractures to another event.


RE: "Event Age" Option: Only process INCOMING particles (for Voronoi etc. important) - Alexx31 - 10-03-2024

Thanks, I will use it.
But maybe an integration makes sense? "Don't process children"
It's one operator less needed and needs no science with channels Wink

Topic "new Events":
New events are something I try always to avoid! Therefore the Option to lead them out is not a real option for me.
If I have three such "needs" for a new event, I get a blown up nodetree just for three simple modifications.

p.s. Therefore I would be most happy if a "surface test" could be integrated as a "filter" into any operator – without a need to create again a new event for it.
I will write an own feature request topic for this :-D