You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _docs/Custom-Output.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,9 +14,9 @@ Let's define some terminology first.
14
14
-**Output field**: A single scalar value for screen and history output or a vector of a scalar quantity at every node in the mesh for the volume output.
15
15
-**Output group**: A collection of output fields.
16
16
17
-
## Customizing the screen and history output
17
+
## Customizing the screen and history output ##
18
18
19
-
### Screen output
19
+
### Screen output ###
20
20
You can define the output fields you want to have on screen by using the config option `SCREEN_OUTPUT`.
21
21
That fields available depend on the solver you are using. Fields available for **all solvers** are the following:
22
22
@@ -32,13 +32,13 @@ That fields available depend on the solver you are using. Fields available for *
32
32
If you run a multizone problem, the convergence history of the individual zones (i.e. the convergence of the inner iteration) is disabled by default and only the convergence of the outer iteration is shown. That means `SCREEN_OUTPUT` in the sub-config files is ignored. You can still print fields from individual zones by using the field name and the zone index. For example in an Fluid-Structure interaction problem the drag in zone 0 and the von-Mises stress in zone 1 can be used as fields by adding `DRAG[0]` and/or `VMS[1]` to the screen output in the main config file. It is possible to force the output of the full inner convergence history per zone by setting `WRT_ZONE_CONV` to `YES`.
33
33
34
34
35
-
### History output
35
+
### History output ###
36
36
37
37
The history output can be customized in a similar fashion to the screen output by using the `HISTORY_OUTPUT` option. In fact, screen and history outputs share all fields which means that everything that can written to screen can be written also to the history file and vice versa. However, instead of specifying single output fields, for the history output it is **only possible** to specify output groups by using the group name.
38
38
39
39
If you run a multizone problem, in addition to the history files per zone, a file (default: `history_multizone.dat`) will be created where the convergence history of the outer iteration is stored. Groups for this output can be by using the `HISTORY_OUTPUT` option in the main config file.
40
40
41
-
### Example
41
+
### Example ###
42
42
43
43
For the compressible Navier-Stokes solver (i.e. `PHYSICAL_PROBLEM=NAVIER_STOKES`), a **non-exhaustive list** of possible fields/groups is the following:
44
44
@@ -66,11 +66,11 @@ For the compressible Navier-Stokes solver (i.e. `PHYSICAL_PROBLEM=NAVIER_STOKES`
66
66
|`FORCE-Z`| Total Force in z direction.|`AERO_COEFF`|
67
67
|`EFFICIENCY`| Total Lift-to-drag ratio. |`AERO_COEFF`|
68
68
69
-
## Volume Output
69
+
## Volume Output ##
70
70
71
71
The `VOLUME_OUTPUT` option can be used to set fields for the restart and visualization files. Here you have the option to specify either single fields and/or groups.
72
72
73
-
### Example
73
+
### Example ###
74
74
75
75
For the compressible Navier-Stokes solver (i.e. `PHYSICAL_PROBLEM=NAVIER_STOKES`), a **non-exhaustive list** of possible fields/groups is the following:
0 commit comments