I am building a workflow where some geometry is generated, then it is baked into rhino in case the user would want to adjust the geometry. Then the geometry is referenced through the pipeline back into rhino. Now if it is few objects it works fine. But if we have more objects, the following thing starts to happen. Once some portion is baked, they are being referenced and the downstream computation is carried. As new batches of geometry arrives to rhino the reference runs again and so on. The whole scipt ends of computing several times before reaching the final result. In the image a attached a Heteroptera tap to count for how many time geometry was referenced and the amount is massive. How can we make it wait until the whole baking process is finished and only then to run the referencing? @andheum please help.
Baking and referencing issue.gh (71.9 KB)
Here is what I tried. I wrote a python code that would reference the objects with their GUIDs as they are coming out from bake only after the baking is finished.
Drawbacks:
-
Now additional geometry can be introduced to the layer for referencing.
-
Doesn’t listen to changes.
So I assume these two things can be added to create a custom made geometry pipeline component, but is there an easier way?
I think you can disable the attribute update in human and use metahopper to recompute the component on clicking a button once you have done the changes in rhino. But it’s pretty similar to what you said.
Don’t know if this helps haha.
Try eleFront? Only bakes when you click.
It doesn’t 
the thing I am looking for is how to create awarness between baking and referencing, so that referencing happens only once baking process is finished.
Human also works like that, so there is no difference. The issue is more about how to make the referencing wait until the baking is done.