Heavy definition must split / cache / pipeline !

Hello everyone and happy 2017!
I am having trouble handling a GH definition in terms of size. I need to split or pipeline or cache or whatever the file to be able to continue working on a fresh grasshopper.

I have been using Flux but it's unstable , crashes every time I wanna upload geometry.

Speckle also has its own issues.

Any advice on how to tackle this problem ? My Rhino scene is almost empty so i can't merely use geometry pipeline.

can combo of geometry cache and geometry pipeline be the answer ? Or fabtools advanced bake ?

Cheers

Shahrokh

Replies to This Discussion

Permalink Reply by Matt Gaydon on January 9, 2017 at 1:31pm

Here's an example geometry cache i wrote for someone on the forum but can't find the post now.

Its all in one GH file but i have used Geometry cache over multiple GH files a few years ago when i need to process a heavy code in stages.

Note:

Geometry Cache works with itself Geometry Pipeline is a different component not linked to geometry cache.

Also Geo-Cache Bakes to the top layer in the Rhino Layer table and not the current layer selected. If you have a empty rhino file it maybe a good idea clear all layers but one and name that Geo-Cache. then add any other layers required.

Hope this is some help.

Attachments:

Geo-Cache Explained.3dm, 397 KB
Geo-Cache Explained.gh, 37 KB

Permalink Reply by Shahrokh Kamyab on January 10, 2017 at 2:38am

Thank you.

One question since you have both cache out and in , in one file :

I suppose you can cache out in one gh file, close that file, open a new gh file and cache in (with the same name) , as long as you have the same Rhino file open? right?

regards

Permalink Reply by Matt Gaydon on January 10, 2017 at 3:57am

Yes That's Correct.

I just had them in the same file as it was easier to explain in a single screen shot.

Permalink Reply by martyn hogg on January 10, 2017 at 5:01am

Data dams are good too!

Permalink Reply by Shahrokh Kamyab on January 10, 2017 at 7:25am

Data delays data flow

Can you explain more.

Permalink Reply by martyn hogg on January 10, 2017 at 11:39am

If you use the Data Dam component you can run sections of your definition instead of the whole definition each time a parameter changes.

When the data to the left of the Data Dam changes, components to the right of it won't update until you click the Data Dam to let the new data through.

So you can change parameters and when you are ready, click the Dam and let the remainder of the definition run.

RSS