Hello, does the DAGMC export feature only export a surface mesh? Im trying to run mesh tallies on OpenMC and when I use DAGMC export it is only exporting the surface mesh not my tetmesh.
Thanks
Hi @thallam,
yes the DAGMC export does only export the surface meshes.
So you would need the tetmesh for OpenMC in the .h5m?
Correct, I believe for the unstructured mesh tallies for openmc it requires a volumetric tetmesh so openmc can tally the data onto the mesh. As I understand there are two ways to utilize unstructured meshes in openmc. The first being the .h5m and moab and the other is .e and libmesh. I have tried the libmesh way but im running into errors on writing the data to the exodus mesh but I cant utilize the moab way because cubit is exporting the surfaces only.
Do you know how the data structure for the mesh should be in the .h5m?
The way I typically get an unstructured mesh for my mesh tallies in openmc is to create the volumetric mesh in Cubit, then export it to exodus, then use the MOAB mbconvert command line utility (available thru conda or however you want to get moab) to convert it to h5m, which is then suitable for OpenMC. If you mesh the surface of your volume using the same mesh settings as you did for the DAGMC export, then use the tetmesh feature in cubit, you can get an unstructured mesh that perfectly aligns with the geometry used for neutron transport, which can be nice.