CAS Mesh

This utility saves FLUENT CAS/MSH files. These files contain volume and surface components used to specify boundary conditions. CAS/MSH files are imported by CFX with the added advantage that names used for all boundary zones (to impose boundary conditions) are imported into CFX without change. This facilitates the task of specifying boundary conditions for large models.

Read

Reads FLUENT .cas/.msh files in binary or ASCII format. Both 3D and 2D (plane/axisymmetric) models are supported.

Write

Writes FLUENT .cas or .msh files containing all the elements currently displayed. Before you start this writing process, display only the components/collectors that you want to export, such as the final 3D fluid domains (and any solid domains if present) and the components containing boundary zones (surface) to specify boundary conditions. Surface components should be extracted from ^faces collectors generated from the volume elements. In the case of 2D (plane or axisymmetric) models, all nodes in the mesh should have the same Z coordinate and perimeter zones for boundary conditions should be defined with components extracted from ^edges collectors generated from the 2D components defining the flow domain.

If the current mesh was previously imported from a .cas file (for example to make mesh modifications), you can reuse simulation settings and boundary conditions from the original/existing .cas file. While exporting, you are asked if you want to reuse model settings/boundary conditions. If you do, then you will be prompted for the name of the .cas file.  

If the component name starts with "Interior-<Comp name>" it is considered as "Interior." If the name of the component starts with "Interface-<Comp name>" it is considered as "Interface."            

If the component between two volumes is defined as "Interface", it will split the domain in FLUENT.

Write (batch mode)

Execute the following command:

hmbatch.exe-tclfluent_batch.tcl

where fluent_batch.tcl has the following contents:

set ALTAIR_HOME [hm_info -appinfo ALTAIR_HOME]

set output_template "$ALTAIR_HOME/templates/feoutput/cfd/general"

*templatefileset "$output_template"

*readfile "C:/home/pipe.hm"

*set fileName "C:/home/pipe_out.cas"

*evaltclscript "$ALTAIR_HOME/hm/scripts/cfd/cfd_comm_proc.tcl" 0

*evaltclscript "$ALTAIR_HOME/hm/scripts/cfd/cfd_proc.tbc" 0

*evaltclstring "CfdCommProc_Fluent_save_msh$fileName"0

This will read in pipe.hm and export the mesh as pipe_out.cas in FLUENT format.  

Read

Reads native StarCD .vrt, .cel, and optionally .bnd files in binary or ASCII format.

Write

Writes StarCD .vrt, .cel, and .bnd files and also a .setup file that can be executed in pro-Star as an input file; this setup file imports the mesh from the .vrt / .cel files and creates all the boundary condition zones with default settings. Before you start this writing process, display only the components / collectors that you want to export, such as the final 3D fluid domains (any solid domains if present) and the components containing boundary zones to specify boundary conditions. Currently only StarCD V3 is supported for import/export.

Read

Reads native binary CFD++ files: cellsin.bin, nodesin.bin, exbcin.bin, mcfd.bc, and so on. Both 3D and 2D (plane/axisymmetric) models are supported.

Write

Writes displayed components as native binary CFD++ files: cellsin.bin, nodesin.bin, exbcin.bin, mcfd.bc, and so on. Before you start this writing process, display only the components/collectors that you want to export, such as the final 3D fluid domains (and any solid domains, if present) and the components containing boundary zones (surface) to specify boundary conditions. Surface components should be extracted from ^faces collectors generated from the volume elements. In the case of 2D (plane or axisymmetric) models, all nodes in the mesh should have the same Z coordinate and perimeter zones for boundary conditions should be defined with components extracted from ^edges collectors generated from the 2D components defining the flow domain.

Read

Reads complete AcuSolve file sets. Only supports face-based BCs.

Write

Writes native AcuSolve file sets: .arm, .inp, .crd, .cnn, .ebc. Only components that will have card images such as Fluid, Solid, Inflow, Outflow, Wall, Symmetry, Slip and Far Field will be exported. Any components with the None card image will not be exported. If the volume elements do not have any associated shell elements, surface components should be extracted from ^faces collectors generated from volume components. During specific .arm export, instead of .inp export, all components will be exported.            

Write (batch mode)

Execute the following command:

hmbatch.exe-tcl acusolve_batch.tcl

where acusolve_batch.tcl has the following contents:

set ALTAIR_HOME [hm_info -appinfo ALTAIR_HOME]

set output_template "$ALTAIR_HOME/templates/feoutput/cfd/general"

*templatefileset "$output_template"

*readfile "C:/home/pipe.hm"

*set fileName "C:/home/pipe_out.inp"

*evaltclscript "$ALTAIR_HOME/hm/scripts/cfd/cfd_comm_proc.tcl" 0

*evaltclscript "$ALTAIR_HOME/hm/scripts/cfd/cfd_proc.tbc" 0

*evaltclstring "CfdCommProc_Acusolve_write_msh$fileName"0

This will read in pipe.hm and export the mesh as pipe_out.inp in AcuSolve format.

Read

Reads CGNS files. Both 3D and 2D (plane/axisymmetric) models are supported.

Write

Writes all the displayed components to a CGNS file. Typically you will display only the 3D components / collectors representing fluid domains (any solid domains if present) and the components containing boundary zones (surface) to specify boundary conditions. Surface components should be extracted from ^faces collectors generated from volume components.

Write (batch mode)

Execute the following command:

hmbatch.exe-tclcgns_batch.tcl

where cgns_batch.tcl has the following contents:

set ALTAIR_HOME [hm_info -appinfo ALTAIR_HOME]

set output_template "$ALTAIR_HOME/templates/feoutput/cfd/general"

*templatefileset "$output_template"

*readfile "C:/home/pipe.hm"

set fileName "C:/home/pipe_out.cgns"

*evaltclscript "$ALTAIR_HOME/hm/scripts/cfd/cfd_comm_proc.tcl" 0

*evaltclscript "$ALTAIR_HOME/hm/scripts/cfd/cfd_proc.tbc" 0

*evaltclstring "CfdCommProc_cgns_write $fileName" 0

This will read in pipe.hm and export the mesh as pipe_out.cgns in CGNS format.

Write

Both 3D and 2D (plane/axisymmetric) models are supported. Writes all the displayed elements to a structured CGNS file. Typically you will display only the 3D components / collectors representing fluid domains (any solid domains if present) and the components containing boundary zones (surface) to specify boundary conditions. Surface components should be extracted from the ^faces collectors generated from volume components. The name of a surface component should contain the name of the volume component to which the shells are attached to and the type of  boundary condition applied to this zone, for example, fluid_wall, fluid_inlet, or interface_fluid_solid.

Read

Reads native SC/tetra *.pre files (only 3D models are supported).

Write

Writes native SC/tetra *.pre files. Only face-based BCs are written for all the displayed components containing surface elements. Before you start this writing process, display only the components/collectors that you want to export, such as the final 3D fluid domains (any solid domains, if present) and the components containing boundary zones (surface) to specify boundary conditions. Surface components should be extracted from the ^faces collectors generated from volume components (only 3D models are supported).

Read

Reads native OpenFoam mesh files, only 3D models are supported. For import, select the folder name containing the directory constant, which also contains the directory polymesh. In polymesh you have files such as faceZones or cellZones.

As an example, for a file structure like test/constant/polymesh, select the directory test for importing the mesh.

Write

Writes native OpenFoam mesh files in the OpenFoam specific directory structure. Only face-based BCs are written for all the displayed components containing surface elements. Before you start this writing process, display only the components/collectors that you want to export, such as the final 3D fluid domains (any solid domains, if present) and the components containing boundary zones (surface) to specify boundary conditions. Surface components should be extracted from the ^faces collectors generated from volume components. If the name of the component has "Interface" in it then it is considered as "Interface."