I wonder how does it go in Shapediver, when I have a heavy part of the script (let’s say a heavy analysis that takes a few seconds to run)…
Can the user run this simulation only once, and then exploring different visualization methods to the results (much lighter calculation time) without re-running the heavy analysis everytime they change the visualization method?
Is it possible, like in grasshopper?
Sorry if this was answered elsewhere
ShapeDiver is based on a scalable set of servers running computations, which means every new request sent from a ShapeDiver model to the backend might reach a completely different server than the previous one. For this reason, it is not possible to cache and reuse a part of the solution in further computations for a model.
A solution to this would be to split the logic between several Grasshopper definitions and upload them individually to ShapeDiver. You would then be able to connect the outputs of a model with the inputs of a second one, using the viewer API for example. In the future, we want to enable this kind of workflows directly in the platform, but at the moment only this programmatic solution is possible.
I understand, thank you Mathieu