Grasshopper

algorithmic modeling for Rhino

Hi!

I am making a project that i want to be able to copy it a lot of times, and I was wondering if this is possible to become automatic. I want to make a polyline through points, and I want to refeed the next point from informations produced from the previews ones. I can do this manually by copying new compoments but I wont be able to do this thing all the time if for instance the number of copies changes or the parameters on the curve. 


I also want to be able to provide some informations through a list. On the file the point on curve i want to be able to provide a list that will give for the first circle one integear from the second another...etc. 

Views: 1674

Attachments:

Replies to This Discussion

I have made the complete precedure. Now I am asking if there is any way to make it more sleak and clean, or if I could control all the "Eval.L" through a List.

 

I was thinking that I could somehow solve the problem with Sequences and Functions but I don't realy know how to use them in grasshopper...

Attachments:

Hi Stamatis, i can't open your recent file but i was playing a bit with a hoopsnake component and it could be maybe something which solve a part of this problem. I was also wondering sometimes how to deal with repeating the same part of the script many times. Up to the certain limit it's still ok but when u have to do it 100 times than it's better to look for easier solution.

Have a look of this example and try to run hoopsnake loop. I'm not sure but it seems to draw the curve based on the randomly evaluated chain of circles.

Attachments:

Hi Stamanis.

 

As @adam states, Hoopsnake is definitely the solution for you here. Programming that huge bunch of clusters is senseless...

 

I have implemented the generation of this curve with HS in the attached files. I have used a random generator of 0.0-1.0 values for the rotational variation, but feel free to change it to a fixed list of values if you are looking for greater control.

 

The strangest thing came to when implementing the out-of-loop condition. Since two points are generated at first instance, before running the script, it seemed natural to ask for a (number of iterations - 2) break condition. Surprisingly though, I had to use n-4 for rule, apparently since the HS actually stops at n+1 iterations, plus it already deploys the last geometry generated... Any suggestions on this Yiannis?

 

Best!

 

 

PS: Rhino v5, GH 0.8.0010, HS 0.5.5

Attachments:

hmm, this is strange, normally from 0.5.5 onwards (see also 0.5.6) the end condition behaves normally and in 0.5.6 it can also be seen hovering over the B* parameter...

I'll check out the file you posted.

Ok I checked the file. I think the problem has to do with the iteration count...probably one of the "-1"s is because iteration starts from 0 I suppose...but the other....

Anyway, I will address that in the next release, in the next few days.

Just a reminder, if you are visualizing the geometry AFTER your generative code (i.e. not from the Hoopsnake output), naturally the result will include an extra iteration of generated geometry. So, if you are at step 0 (initial condition), and you visualize the output of "Ins" (as in your file, you will essentially get step 1 (the next step), because your generative code has already been run once, even though not yet "captured" by Hoopsnake.

Thanks a lot for your intrest. I was messing around with Hoopsnake but you seem to bit me with it :P

 

I opened the ghx file but the line doesn't seem random to me. I was having the same problem when I was trying to make something with hoopsnake myself. Any ideas?

Attachments:

Have you checked your software versions match the ones I posted?

 

Can you post the ghx file with the parameters you chose?

I haven't change anything, just pressed next. The truth is I didn't had the same hoopsnake soft, but now I have the latest and it behaves the same. Also I didn't opened the rhino file, just the grasshopper one, I don't think it matters though....

This file is saved as file after some steps
Attachments:
Garcia thanks for adding this work ! It helps to understand the mechanism of this component.


Adam
You are welcome dude!

I know what you mean. The definition doesn't work when using it with manual step-by-step, since the HS component does not move forward on the iteration count when pressing step. The randomness in this definition relies on the iteration count. This was probably a programming decision by Yiannis, he probably has his reasons for it.

Just try the definition with the loop mode.

RSS

About

Translate

Search

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service