I am currently working on an optimization script. To repeat the steps to optimize i'm using hoopsnake. Since there are several inputs i need to update in each step, I decided to pack a little data bundle to hand it to hoopsnake (using the entwine - and tree explode command)
Now I am facing a big Problem:
Hoopsnake somehow doesn't accept and process the tree structure in the D* input correctly. As you can see in the picture below, the output "A" shows a structure of {0;0} N = 3 {0;1} N = 3
but the mouseover on the input "D*" in hoopsnake shows a different structure
{0;0} N = 4 {0;1} N = 2
There are no commands or anything inbetween.
Has anyone of you faced similar issues and maybe knows how to deal with it??? Is it a bug or am I doing something wrong? Any help would be greatly appreciated
Cheers, Benjamin
Edit: btw, the problem also occurs when i don't use the data delay command. So that's not the problem
Hoopsnake
566 members
Description
Update:
Hoopsnake is now Open Source!
Check out the repo in Github!
Fork it and fix it :)
Hoopsnake is a component that allows feedback loops within Grasshopper.
Hoopsnake Tree structure - Bug??
by Benjamin Felbrich
Aug 2, 2013
Hi there,

I am currently working on an optimization script. To repeat the steps to optimize i'm using hoopsnake.
Since there are several inputs i need to update in each step, I decided to pack a little data bundle to hand it to hoopsnake (using the entwine - and tree explode command)
Now I am facing a big Problem:
Hoopsnake somehow doesn't accept and process the tree structure in the D* input correctly.
As you can see in the picture below, the output "A" shows a structure of
{0;0} N = 3
{0;1} N = 3
but the mouseover on the input "D*" in hoopsnake shows a different structure
{0;0} N = 4
{0;1} N = 2
There are no commands or anything inbetween.
Has anyone of you faced similar issues and maybe knows how to deal with it??? Is it a bug or am I doing something wrong?
Any help would be greatly appreciated
Cheers,
Benjamin
Edit:
btw, the problem also occurs when i don't use the data delay command. So that's not the problem