<output>

Frozen Surface Geometry

<output> - <general> - <frozen_surface_geometry>

true: The “frozen geometry” output combines the geometry inside the Overset Mesh region at its initial state with the associated transient data. This facilitates the creation of dB maps for rotating geometries and advanced other data processing. Additional *_frozenGeometry.geo, *_frozenGeometry.case, and *_frozenGeometry.sos files are created for the general surface output. The *.data files are reused from the rotating (non-frozen) output.
false (default)

<output> - <partial_surface> - <partial_surface_instance> - <frozen_surface_geometry>

true: Similar to the general surface output, the “frozen geometry” output for partial surfaces combines the geometry inside the Overset Mesh region at its initial state with the associated transient data. Additional *_frozenGeometry.geo, *_frozenGeometry.case, and *_frozenGeometry.sos files are created for the respective partial surface output. The *.data files are reused from the rotating (non-frozen) output.
false (default)

High Fidelity Mapping

<output>- <high_fidelity_mapping>

High-fidelity mapping improves the mapping of boundary voxel data to a (in relation to the local voxel size) coarser surface mesh. For this purpose, the surface mesh is internally split into finer virtual triangles, and the data obtained is then averaged and written on the original coarse output triangles. This feature improves the output quality for CAA/GHN purposes while maintaining a reasonable output size and is controlled by the following parameters:

true: When activated, the triangles on the surface which it is applied to are split to the local voxel’s size (temporarily). The average of the quantities is used to calculate the value on the coarse input triangle (from the internally created fine triangles, weighted with their respective area). The information is propagated back to the coarse input triangles. Applying HFM on a surface does incur computational cost and should be applied with caution as such.
false (default)

<max_relative_edge_length>

Default value: 1.0

This factor is applied to the local voxel size to determine a splitting threshold for the triangle edges. Any triangle edge in the considered surface mesh exceeding the threshold is split in half until the resulting edges are below the threshold. Setting this factor to zero or a negative value makes the variable inactive.

The category <high_fidelity_mapping> can (optionally) have an arbitrary number of children named <high_fidelity_mapping_instance> which share the parameters above but additionally specify part names:

<output>- <high_fidelity_mapping> - <high_fidelity_mapping_instance>

true: Similar to the general surface output, the high-fidelity mapping on a specific surface.
false (default)

<max_relative_edge_length> (see above)

<parts>

<name>: The part(s) on which the high-fidelity mapping should be output. Several parts can be called in the same instance. The specified names must exactly match the respective part names in the STL file.

Specific for Overset Cases

Cases using overset mesh have updated information on the location of the rotating voxels and surface elements at each time step. For all output instances requesting data at different time steps, the current geometry information will be exported into a .geo file.

As this can be time and memory consuming, you can choose to export only variable data for all times t>0, while the geometry is only exported at t=0 (initial time step). When using EnSight format, this will result in a single .geo file with the initial geometry and multiple .data files according to the requested time steps. For h3d format, the initial geometry and updated variable data per time step are included in a single file.

<output>- <general> - <time_varying_geometry_output>

true (default): Geometry information is written at every time step that requests data output, that is, data can be visualized on the correct current geometry.
false: Geometry data for this instance is only written at the initial time step, not at the step that the requested output starts. When data is visualized, values of subsequent time steps are therefore shown at the initial position of the respective voxel/surface element, producing the equivalent of <frozen_surface_geometry> output. In order to recover the movement of the mesh, a variable tracking the displacement of the voxels can be requested (see below).

Note: For rotating geometries, a difference can be observed between EnSight and h3d format for outputs that cover only a part of the geometry, for example, section cuts or partial volumes. If <time_varying_geometry_output> is true (default), current geometry information is written at each time step for both EnSight and h3d formats. However, for outputs covering a subset of surface and volume elements, a second factor needs to be considered: the output instance needs to identify the volume and surface elements that are currently in the selected area and update the topology of exported elements accordingly. This happens by default for EnSight outputs, but is not supported by the .h3d format. For that reason, the time varying geometry output written in .h3d format will follow the initially identified elements in the requested plane or volume and update their position rather than assigning new elements to the requested output.

<output>- <general> - <mesh_displacement>

true: If set to true, a variable tracking the movement of the mesh will be written out. This variable can then be used to recover the current position of the mesh for use in, for example, animations of moving mesh parts for cases where a moving geometry is not exported at every time step, that is, the parameter <time_varying_geometry_output> is set to false.; Can be used everywhere except for monitoring surfaces and probe output.
false (default)

Snapping Probe Points to a Specified Part

Note: Cannot be combined with probes using a specific probe radius.

Surface probes retrieve data from the triangle center nearest to the indicated location. It is possible to indicate the part that is targeted for the surface probe to avoid probing on an undesired part, for example, in geometries with small gaps between parts. This is indicated in the solver deck as follows:

<output><single_probe><single_probe_instance>

<parts>

<name>: List of part names that contain the eligible triangles for this probe. The probe will snap to the triangle whose center is closest.

<output><probe_file><probe_file_instance>

<parts>

<name>: List of part names that contain the eligible triangles for this probe. The probe will snap to the triangle whose center is closest.

<output><probe_file><probe_file_instance><source_file>

Another option is extending the probe file with a target part name. The probe_file.csv should then contain the following columns:

<x_pos>;<y_pos>;<z_pos>;<description>;<part_name>

Note: Part names indicated in the probe_file.csv will be used, even if <probe_file_instance> points to another part, that is, the parameter <parts><name> has lower priority than the entry in the probe_file.csv file.

Note: Parts can be those listed in the input .stl file, but also internally created parts: triangles located on a part inside an overset zone can be assigned as original_part_name.uFX_overset; triangles located on baffles can be assigned by original_baffle_part_name.uFX_baffle_front or original_baffle_part_name.uFX_baffle_back. If a baffle part is used without specifying .uFX_baffle_front or .uFX_baffle_back, then the front side will be used.