Grasshopper

algorithmic modeling for Rhino

Hi all!

I'm using Grasshopper for a while and with every new project the definition becomes bigger and bigger, i have started to think about code organisation/optimisation. 

so it is a general question.

I have a big model, the calculations take an around minute or so. It is a big mess of wires but the problem is it is hard to tune the initial parameters, and it is hard to build further because of the long calculation time.

So wat is the best practice to divide definition to steps?

Is here a way like in Solidworks prevent calculations made before some step recalculate constantly?

Or maybe there is some way to assign the stop points? Like a you have some mesh wich easy to adjust but when you start to replace wires by pipes of a certain cross-section, and add some elements to connected points changing initial parameters became a pain. If here would be some break point to prevent calculation before or after this could be a bit easier to work with such definition. First step the mesh and general form, second pipes and section etc

I use a kind of this to organise the steps but this doesn't look pretty, and i couldn't use the enable/disable from the remote panel.

Views: 571

Attachments:

Replies to This Discussion

Thank you Tom!

Haven't known about params -> util -> data dam will check it looks like it is what i'm looking for indeed.

As for other advices, i'm weak coder, and i have such illness - "just to prevent 2 hours of monotone work" and enjoy it a lot :)

I like clusters although as result there is the more repetitive calculation in each cluster.

There is no way to avoid trees i think

RSS

About

Translate

Search

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service