Open connoramoreno opened 4 months ago
Sorry to hear the meshing part in export_cad_to_dagmc
is not working and thanks for trying.
Out of interest does export_gmsh_mesh_file
manage to produce a mesh?
Another thing to try is exporting the step file and then opening it with gmsh to take a look at the geometry and see if it can be manually meshed in the gmsh gui.
Another thing to try is reducing the min_mesh_size
argument for export_cad_to_dagmc
, it defaults to 1 but it can go smaller
I was just looking into adding another method of surface meshing so perhaps this is a good reason to add that extra meshing option
Looks like export_gmsh_mesh_file
fails similarly on surface 10 as above. Same goes for using min_mesh_size=0.5
.
We'd like to be able to automate this process within ParaStell, rather than needing to manually mesh the geometry, though it may be a good idea to look at the geometry in the Gmsh GUI for any obvious issues.
When trying to export a DAGMC model of the test in-vessel build geometry using the
export_cad_to_dagmc
method of theInVesselBuild
class, I am running into the following error during the 2-D meshing step:I am unsure if this error is specific to ParaStell or CAD-to-DAGMC. The geometry used is that of the test in-vessel build; that is, the geometry includes a plasma (yellow), scrape-off layer (green), and a single generic component (purple/pink), pictured below.
Interestingly, as the 2-D meshing occurs after surface merging, there should only be 3 BSpline surfaces (surfaces 1, 4, and 7). This has been cross-checked against the WISTELL-D stellarator configuration, using the same workflow and geometry definition, and against the same testing configuration where a reduced geometry definition is used, such that the toroidal extent is reduced to 30 degrees rather than 90 (both alternatives mesh successfully and don't include surface 10).
It is this mysterious surface 10 that is causing the error, but I'm unsure why the surface is there at all. Perhaps @shimwell has a better idea of what's going on?