Hi all and hi @DanielPiker,
I’d like to ask some clarifications about Kangaroo2.
I used Kangaroo for a while and I have noticed that there is a recurrent problem which is the fact that with particular strengths values and goal conditions some moving points are overshot in the motion direction which may generate a perpetual motion or the explosion of the whole system.
I attach a file as reference:
fold overshooting.gh (15.8 KB)
Why does it happens? And since Kangaroo tries to minimize the error how am I able to generate a perpetiual motion generating motion from nowhere?
I would like to know if it is possible to have some constraints that are 100 accurate. For example the anchor points. Is there any way to fix it univocally in a specific place without making them move at all? I think this is not possible at the moment but maybe there is a way to implement the solver formulation to make it processing only some specific goal nodes as springs and consider others as fixed starting points that do not behave like springs.
Sometimes I have troubles to split the output results.
For example, if I input two different lists of segments in two different goal nodes, and let say that I need to re-use them preserving the original order after processed them with kangaroo, how can I do it efficiently? Maybe it would be useful to have an additional node that takes as input one or more “Show” nodes and the Kangaroo solver which would return the list of the same elements input in the “Show” node after processing them with the solver preserving the order of the original elements.