Grasshopper

algorithmic modeling for Rhino

Hi,

Thanks, this is an amazing plugin... its really really great!!

 

I'm getting duplicate geometry when i select the append data option and run for a few iterations. I understand that this is because the hoopsnake re-calculate for all the inputs  and that include the geometry from previous iterations.

I attach two images where i use "remove duplicates" to show the difference in the number of elements.

 

Is there a way to "fix" this, so the hoopsnake calculate only the geometry from the last iteration and just "preserve" the rest?

 

If im not missing some hidden option... Can you add this to the wish list? :D

I dont think that it will be to difficult because when you dont select the append option, it only calculate the geometry from the last iteration so we only need some kind of "bypass" for the other geometry ;-)

 

Thanks again!

 

 

 

 

Views: 597

Attachments:

Replies to This Discussion

Wow, just asked the perfect question. Similiar question except with a dead simple branching technique.
Attachments:

You can also hierarchize the data you give to the next iteration :

branch 0 stores the objects to work on

branch 1 stores the objects from previous iterations

 

Hello Manuel,

 

I have made a change to the append function in 0.6.0: Instead of appending the new data, it actually appends the existing data to the new (i.e. prepending new data). So, if you flatten the output the new data will be on top of the list. This I considered more useful for keeping history of iteration steps and still easily having access to data from the latest iteration (e.g. with a simple list picker).

There is an example together with the new release that shows exactly the append functionality together with a list item picker.

 

Yiannis

Hi Yiannis, thanks for the new version.

 

I manage to get it working and eliminate those duplicates :D

 

Now for the wish list:

Hoopsnake doesnt separate each iteration in separate paths / branchs... if the inputs its a flatten list, it produce a flatten list... if the inputs its a graft list, it produce a graft list for the new data and append the "old data" in the last branch in a flatten list.

 

I think that if you keep the path structure from the input data to the new data, we can use that and change the path for every new iteration using the iteration number output (i actually tried that but it didnt work).

 

Here some pics...

 

Thanks again.

 

Attachments:

Hi Manuel,

 

Indeed the data using the append method is simply appended to the new structure. Haven't given much thought to that apparently ;') I will give more options to that in the next release. Thanks!

RSS

About

Translate

Search

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service