I am using Trelis 17.0. I am trying to mesh an irregular (but flattish) surface for which I have a regular point cloud (it is already meshed actually!)
Here is a toy script that reproduce the issues (you may want to run until the first save in terminal version, it is much quicker this way)
import cubit import random # Generate rough surface from a regular mesh of sample points listOfVertices =  listOfCurves =  for i in range(50): for j in range(50): randz = 0.2*(random.random()-0.5) # Random z coordinate to mimic my data cubit.cmd("create vertex "+str(i)+" "+str(j)+" "+str(randz)) listOfVertices.append(cubit.get_last_id('vertex')) listOfVerticesStr = " ".join(str(e) for e in listOfVertices) # From e.g. [0,1,2] get "0 1 2" cubit.cmd("create curve spline location vertex "+listOfVerticesStr+" delete") listOfCurves.append(cubit.get_last_id('curve')) listOfVertices =  listOfCurvesStr = " ".join(str(e) for e in listOfCurves) # From e.g. [0,1,2] get "0 1 2" cubit.cmd("create surface skin curve "+listOfCurvesStr) cubit.cmd("delete curve "+listOfCurvesStr) # Here we have generated the rough surface... # There is a first problem here. Let us save it first: cubit.cmd("save trelis './example.trelis' overwrite journal") # This weighs 3.6 Mb... looks huge to me but I can admit this # Let's webcut it now cubit.cmd("webcut body 1 with plane yplane offset 45") # Takes a lot of time... but ok cubit.cmd("webcut body 2 with plane xplane offset 45") cubit.cmd("delete surface 2 5") # Delete big surfaces and keep the small one cubit.cmd("compress") # Alright, here we end up with a tiny slice of the initial surface, let save it to file... cubit.cmd("save trelis './example_2.trelis' overwrite journal") # This weighs: ...7.1 Mb!!?? # This looks like a bug, you tell me. # Ok anyways, now let's forget this and get back to the initial surface cubit.cmd("reset") cubit.cmd("open './example.trelis'") # Takes a lot of time but ok... # Let's mesh it cubit.cmd("surface 1 size 0.5") # Nothing crazy here... cubit.cmd("mesh surface 1") # This takes ~10min and this duration evolves exponentially with the number of points used to describe the initial surface... which makes it completely intractable for any realistic purpose. I have tried other meshing schemes as well: same # It does it eventually though... but this is not over. Working with the mesh is impossible anyways # Checking quality metrics, for example, takes (at least) 20 min...
Is it any workaround for this? How can I get a usable mesh for my point cloud without having to use “skin curve”?
Thank you very much for your help,
Marine Physical Laboratory
Scripps Institution of Oceanography