Gismo _runit and _bakeit slowness - how to manage?

Hi,

I'm brand new to Gismo. It's very exciting to be able to generate urban 3d models that once took days to create.

I have a simple question about managing Gismo definitions. I've been adapting the included example file "create_3dbuildings_trees_streets.gh" for my own projects. I am keeping the radius modest: no more than 500 and that produces a pretty small amount of geometry. However, when I toggle the boolean to True for any _runit the definition can hang for minutes at a time. _bakeit can also take a long time. Finally, if I save the defnition and leave the boolean toggles set to True, opening takes very long (the sum of all load times for each True?) and can crash Rhino.

My question is: Assuming the load and bake times are normal, how are people best managing their definitions to mitigate this? I want to distribute definitions to students and would rather not crash their rhino or make the definitions unworkably long.

Thanks

Replies to This Discussion

Permalink Reply by djordje on April 11, 2020 at 12:06am

Hi Josh,
Thank you for reaching out.

On shortening the time it takes for the definition to run: one way may be to internalized certain inputs or even outputs of components and then compare the loading time with regular "set Toggle to True" approach.

Here is one such example.

About crashing of Rhino:

Can you attach one such definition where the crash happens?
Thank you.

Permalink Reply by Josh Draper on April 13, 2020 at 1:16pm

Hi Djorde,

Thanks that makes sense. I'll try internalizing data.

For the "crashing Rhino", I'm sorry, I already changed the definition and don't want to recreate it! It takes so long to do it :) Sorry. It was just this: The included example file "create_3dbuildings_trees_streets.gh" with every Boolean Toggle set to TRUE for _run inputs and also a Boolean Toggle set to TRUE for each _bake input. I carefully built this up and was able to generate and bake a layered map. I then saved this definition and later reopened it. It crashed Rhino twice. Another time it just took a very long time to run and bake. I also found it takes a long time to turn off or delete a Boolean Toggle.

Thanks.

Permalink Reply by djordje on April 13, 2020 at 1:41pm

Hi Josh,

Can I ask you for a favor?
If you ever get the same crash, after the crash of Rhino, please run the Rhino and Grasshopper again.
In Grasshopper's application menu choose "Solution->Disable Solver".
Then open your .gh file again. The following screen will appear:

Choose "Open Recovery File".
Choose "File->Save Document" in Grasshopper's application menu. Close the .gh file and attach it here.
I thank you in advance for this.