Operations on Kangaroo data trees output from simulation geomtery, nodes

If multiple springs are used in a kangaroo model, they all force into one input. THere is also only one output for all these grouped elements.

My challenge is Post-processing operations on there data sets when they are lumped as one now (flattened to run).

Each group of springs may also have variable lengths within them (like the hangers on a suspension bridge), and operations on them (i.e. math, add, subtraction, etc), needs to separate them from other spring elements, such as main cables or back stays.

Additionally, the mainline cable may have equal length divisions, however, the backstay may not (due to length dfferentials, same division number), so again, splitting them out of the geometry out back to their individual elements for post-processing is tricky?

Any input, feedback, discussion is appreciated.

Replies to This Discussion

Permalink Reply by Daniel Piker on March 14, 2013 at 1:42am

Hi Michael,
While the force objects need to be flattened, the 'geometry' input doesn't. So you can use data trees for your different lists of elements here. The output geometry then keeps the same data structure, so they can be compared to get deformations separately.
I had been thinking about ways of improving this, as most intuitive seems like it would be to have the outputs like deformations come directly from the force object components, but there doesn't appear to be an obvious way of doing this without breaking the GH flow, and outputting data upstream of where it is generated... Any ideas welcome

Permalink Reply by Omar Helmy on March 16, 2013 at 1:33am