VI-1. Output Mesh Files#
EMSolution writes mesh files for post-processing and verification. Specify the file format with POST_DATA_FILE(10.2) in Section 10.2, Output Files.
For standard file formats (other than CADAS and HyperView output), each distribution quantity is written to a separate file.
For CADAS output, all distribution quantities are written in CADAS format to the single post.cad file. Specify POST_DATA_FILE=6 to use CADAS format. You can use the result as a CADAS input file by concatenating the separately written post_geom mesh file before this file. The following lists physical-quantity names (VNAME) in CADAS files.
For HyperView output, as with CADAS output, all distribution quantities are written in HyperView format to the single post.hwascii file.
File post_geom#
When MESH(10.3) =1 is specified, the three-dimensional mesh data used in the calculation are written. The unit is m regardless of UNIT(10.1).
Caution
UNIT(10.1) applies only to input mesh data files. It does not apply to output mesh data files.
Mesh data with the material-property IDs specified by OUTPUT_MATS(10.2) are written. If omitted, all meshes are written.
When the analysis includes sliding motion, mesh data combining the stationary and moving parts are written.
When the external current and magnetic-field source COIL(17.1) is used, COIL is also written as mesh data in addition to the finite-element mesh. However, MESHED_COIL MESH(17.1.7) is not written.
To suppress COIL mesh output, specify COIL_OPTION(10.2) =1.
Gap elements GAP_ELEMENT(16.2)
Not written when SUF_OPTION(10.2)=0.
Written when SUF_OPTION(10.2)=1 is specified.
For POST_DATA_FILE(10.2) =5, FEMAP neutral format also writes property data in addition to node and element data.
File boundary_surface#
When the output file format POST_DATA_FILE(10.2)>0 is used, surface elements on boundary surfaces are written to the boundary_surface file in the specified mesh format. The material-property IDs (MAT_ID) of surface elements are assigned as follows according to the configured boundary conditions. Even when NODE_ORDER=2 in Section 4, Shape Function Order and Additional Features, and a second-order nodal element contacts a boundary surface, it is written as a first-order surface element.
Boundary Type |
MAT_ID |
MAT_ID |
MAT_ID |
|---|---|---|---|
pre_geom |
rotor_mesh |
rotor_mesh n (n = 2–7) |
|
Ht=0 surface |
1 |
101 |
n 01 (example: 201) |
Bn=0 surface |
2 |
102 |
n 02 (example: 202) |
Far-field boundary surface (other than an infinite boundary) |
3 |
103 |
n 03 (example: 203) |
Surface impedance |
4 |
104 |
n 04 (example: 204) |
Infinite-boundary element surface |
5 |
105 |
n 05 (example: 205) |
Sliding surface |
11 |
111 |
n 11 (example: 211) |
Periodic boundary surface |
21, 22 |
121, 122 |
n 21, n 22 (example: 221, 222) |
Important
Use boundary_surface to check whether the specified surfaces are configured correctly and whether duplicate nodes or similar issues have created unintended far-field boundary surfaces inside the model.
Note
Configure the Ht=0 and Bn=0 surfaces by specifying coordinates (see Section 13, Boundary Conditions, 13_Boundary_Conditions, for details).
Specify a sliding surface by edge elements defined on the sliding surface (point elements for a two-dimensional mesh) or by straight-line coordinate input. See Section 14, Periodic Boundary Conditions, 14_Periodic_Boundary_Conditions, for details.
A periodic boundary surface is assigned when a boundary surface overlaps its original position after translation by the specified rotational periodic angle or translational periodic length. The original boundary surface is recognized as the start side (for example, MAT_ID =21), and the overlapping boundary surface as the end side (for example, MAT_ID =22). For 180° rotational periodic symmetry, the start and end sides cannot be distinguished; therefore, SEPARATE_ANGLE(14) must be specified.
These boundary surfaces are identified by whether node coordinates on the surface lie within the specified range ( DISTANCE_JUDGE(13) ) of the specified coordinates. Elements containing nodes outside the coordinate range, and boundary surfaces that are not specified, are identified as far-field boundary surfaces. Consequently, discontinuous surfaces inside the model or elements separated by duplicate nodes may also be identified as far-field boundary surfaces. In that case, display the boundary_surface file and check that it contains no unintended far-field boundary surfaces.
Set DISTANCE_JUDGE(13) to a value smaller than the minimum distance between nodes.
File t_r_interface#
When the external current and magnetic-field source COIL(17.1) is used, the potential-boundary surface-element output file t_r_interface writes the potential boundary surfaces between the total-potential and reduced-potential regions, together with the COIL(17.1) mesh. You can use it to check whether COIL(17.1) enters the total-potential region.
In particular, when the total-potential region is extended with EXTEND_TOTAL_for_COIL(16) =1, the potential boundary surfaces change. Display and check this file. Potential boundary surfaces are written with MAT_ID =1.