Hii .I have one gh file in which i want to store dendro volume in result .It is working for mesh output but getting null if trying to store results.Here attaching image of gh file
c# code for storing result
Any suggestions on this will be helpful.
c# code for storing result
Any suggestions on this will be helpful.
Hello, as I understand, only serializable objects can be ‘stored’. It seems like Dendro Volume does not implement a ‘serializable’ interface. So, there is no way of doing what you want.
Thank you @mikity_kogekoge for your reply. This dendro mesh to volume and volume intersection takes lot of time .That’s why we want to split this component in separate files.Did you have any idea about 100sec timeout which i get on GrasshopperCompute.EvaluateDefinition(ghFileName, trees)?
Hi, because Dendro computes three-dimensional voxels, the computation takes a lot of time in general. If there is no need to recycle voxels, perhaps you can convert them to a mesh (and use ReduceMesh in LunchBox) and store/internalize them.
Hii @mikity_kogekoge here attaching image of my whole lattice gh file.Can you please guide me wher eto add reduce mesh?
@mikity_kogekoge But I am getting timeout issue on mesh to volume component only.So maybe need to add after mesh joining only?
The lattice output getting after reduce mesh before volume mesh is not correct .Mesh is totally split.
No, If timeout occurs on mesh to volume component, you need to reduce the resolution of voxels, which can be controlled through vSettings. But I think the easiest way is to find a way to extend the timeout threshold. The reason I’m suggesting using the reducemesh component is that, usually, the mesh created based on a Dendro Volume is unnecessarily high resolution.
Btw, why are you using Rhino.Compute?
Dendro is computationally very expensive, so the computation takes time. That’s normal.
If you just want to convert a wireframe lattice into a ‘thick’ lattice,
instead of tossing data to Rhino.Compute, just make a simple Grasshopper script, run it, and wait. Even if it takes time, you will eventually get a result, unless Dendro runs out of RAM.
I want to run this whole in headless mode.That’s why using rhino compute.I have one endpoint which call the c# code where this evalute defination is written.
If you really want this to run in a headless mode, I have a few suggestions.
- Dendro’s computation physically takes time. You need to find out where the timeout threshold is written and adjust it to a longer value.
- Tweak the parameters of vSettings to lower the resolution of the voxels.
- Dendro Volume does not implement a serializable interface, meaning ‘store’ or ‘internalize’ is impossible. You need to convert the DendroVolume into a mesh to ‘store’ or ‘internalize’. In that case, because an excessively high-res mesh is usually obtained, I recommend calling ReduceMesh to lower the resolution of the mesh.
Do you really need this to run in a headless mode?
A possible workaround would be a 'semi-automated mode. The first GH definition(the one that has Dendro) has a Bake button, which allows the user to bake the output mesh into a specific layer in Rhino. The second GH definition(the one that retrieves the output mesh) also has a ‘read’ button, through which the user can read the output mesh from the same layer.