Forum Replies Created
-
Posts
-
Hugo,
As to the file types that support split topologies, I was thinking about gmsh’s physical groups that allow smaller pieces of the mesh to be identified while preparing the mesh file. Now that I understand that this likely isn’t implemented I’ll manage it in python.
That means yes, I consider this resolved.
It looks like that is what I need. I will read over this new documentation. But I still have the loader question, let me re-phrase it. If I have a subset of topology defined in the mesh file that I load into SOFA can that subset of the topology be accessed in SOFA or do I need to re-define it?
Hugo,
Thank you for your help!
I do want what is in @ loader.position but I would like it dumped to a file. (So that I can look at it later.) Currently I use something like:
<PlaneROI name=”TooHard” />
<Monitor indices=”@TooHard.indices” ExportPositions=”1″ />And I can’t see how to use @loader.position more directly.
As for the cylinder. I was hoping for something more out of the box as I am not yet ready to extend the functionality. Let me ask a different but related question. If I have set or group defined within the mesh can the loader extract and use that information? Or does that get lost in the process?
Ben
