Step 3: Forces export
Introduction
In this part, the method to export a computation of surface magnetic forces on Flux mesh is presented.
It is available through the menu
or through the icon .Export for VirtualLab
The export for Virtual lab allows exporting the temporal forces in a .UNV file. Consequently it is available only in transient magnetic application.
In the export box user has to specify:
- The computation name
- The number of elements in depth*
- The force unit
- The .UNV file name
Number of elements in the depth
In 2D, the number of elements in the depth is required in order to project the results on the depth (by dividing the values in order to always have the same total sum).
In Skew, the number of elements is defined in the application of the project, and in 3D the forces are calculated on the nodes of the mesh.
Export for HyperMesh
The export for HyperMesh allows exporting the forces into a file in HyperMesh format. In HyperMesh, it is possible to choose at the beginning a working profile which can be OptiStruct or Nastran.
For the export for HyperMesh, user has more options:
- Computation name
- The number of elements in depth
- The export format: Nastran/OptiStruct
- The file name
- The force evolution type: static/temporal/frequency
- Static forces: forces exported from a steady state application project (magneto static or steady state AC) or on one time step in magnetic transient (in this case, the computation should be done only on the interesting step, otherwise the first step is taken)
- The force unit
- Advanced options:
- Number of harmonics (if empty, all harmonics are exported)
- DLOAD card ID: this ID allows distinguishing the exports done on the same project (especially when solving with multi-physical parameters) to import all files correctly in HyperMesh. By default (DLOAD=0), the computation ID is attributed, but user can choose it manually in this option.
- Simple or double precision: it defines the exported values precision.
Export into a data file
It is also possible to export the static or temporal forces into a .dat file