Hi,
Want to get your advice, @WojciechKarnowka , regarding best practices for the meshing geometry in cyclops.
Urban configurations can be challenging on this respect. I suggest adding an example using OSM [or other sources] where a workflow can be recommended, from meshing to simulation.
Thanks,
-A.
Hi ayezioro,
The meshing really depends on what level of detail you need for your analysis and what type of geometry you are meshing.
Iād say as a general rule you want the simples possible mesh without loosing detail that is relevant to the specific analysis case.
There is a component that comes with Cyclops that tries to extract the display mesh from the geometry, this can sometimes make the process more efficient but again it depends on the usecase. Get Clean Mesh - Cyclops
Regarding static larger scale geometries, like urban models that are use as context. We would usually mesh those in Rhino and keep them referenced from the Rhino file to avoid Grasshopper having to mesh all geometry each time you run the Grasshopper script. You can also potentially keep the meshed context in a separate Rhino file and load it straight into Grasshopper and Cyclops using the Read 3dm component, to avoid slowing down Rhino.