Hi Luis,

I'm not quite following what is the result you are after.

Do you want to have 2 different parallel non-interacting simulations happening through the same Kangaroo component ? What would this be useful for ?

The only Kangaroo input that currently uses Tree access is the Geometry input. All the others have only Item access.

As you know, normally with item access inputs on a component or script, if you provide that input with a list or a tree, it behaves roughly as though you have multiple separate copies of the same component with each of those branches or list items as an input.

However, because I store information (such as particle positions) between iterations, it looks as though trying to use multiple branches for things like the Kangaroo Force input doesn't work, because the data from separate branches ends up mixing.

One time this is useful is that you can provide 'Reset' with a list of 'True,False,False,False...' and get multiple frames or instants in time as an output (and I guess this shows that it is not really keeping things separate like with other components, because each item in the list is using the result from the previous item).

If you want to simulate several things in parallel (e.g. relaxing 10 different meshes at once), you can always just input them all into the same simulation, but don't include any interactions between them. If you need to keep the results in separate branches for downstream operations, then you can do so using the Geometry input.

So I can't see much advantage in being able to have different simulations running in different branches - except maybe if you wanted to do something like run each of the relaxations with a different timestep - and this currently doesn't seem worth the headache it would be trying to get all the paths to operate separately. Though if you have a compelling reason why it would be useful then I'd reconsider.

I hope that makes things clearer