The Open FUSION Toolkit 1.0.0-8905cc5
Modeling tools for plasma and fusion research and engineering
|
The primary way to load meshes into the Open FUSION Toolkit (OFT) is through OFT's native mesh description format, which utilizes HDF5 for data storage. As OFT only provides mesh generation capability for selected cases, most files will be generated by one of the provided conversion scripts described below.
In order to load a native mesh file cad_type = 0
must be specified in the mesh_options
group (see Mesh settings). The mesh filename and some native-specific options are specified at runtime in the cubit_options
group. The options available in this group are listed below.
Option group: native_mesh_options
| Option | Description | Type [dim] | |-—|-—|-—| filename,reflect,ref_periodic | filename=""
| Name of mesh file | str(OFT_PATH_SLEN) | | reflect=F
| Reflect mesh about xy-plane? | bool | | ref_periodic=F
| Make mesh periodic in z-direction following reflection? | int |
As OFT only provides mesh generation capability for selected cases, most files will be generated by one of the provided conversion scripts from software-specfic formats (eg. CUBIT, gmsh, etc.).
To convert from CUBIT meshes saved using the Exodus/Gensis file format use the convert_cubit.py
script (as below). The --in_file
argument must be specified and by default a new file is created in native format with the same name, but *.h5
extension, in the current working directory. Additional options to control inclusion of periodicity information are available (use --help
for more information).
~$ python /path/to/oft/bin/convert_cubit.py --in_file=/path/to/cubit_mesh.g
To convert from Gmsh meshes saved using the MSH file format use the convert_gmsh.py
script (as below). The --in_file
argument must be specified and by default a new file is created in native format with the same name, but *.h5
extension, in the current working directory.
~$ python /path/to/oft/bin/convert_gmsh.py --in_file=/path/to/gmsh_mesh.msh