![]() |
programmer's documentation
|
User subroutines for input of calculation parameters (Fortran modules). These subroutines are called in all cases.
If the Code_Saturne GUI is used, this file is not required (but may be used to override parameters entered through the GUI, and to set parameters not accessible through the GUI).
Several routines are present in the file, each destined to defined specific parameters.
To modify the default value of parameters which do not appear in the examples provided, code should be placed as follows:
As a convention, "specific physics" defers to the following modules only: pulverized coal, gas combustion, electric arcs.
In addition, specific routines are provided for the definition of some "specific physics" options. These routines are described at the end of this file and will be activated when the corresponding option is selected in the usppmo routine.
Frequency of log output.
Log (listing) verbosity.
Probes output step.
Number of monitoring points (probes) and their positions. Limited to ncaptm=100.
Current variable. As for other variables, if we do not assign the following array values, default values will be used:
User scalar variables.
We may modify here the arrays relative to user scalars, but scalars reserved for specific physics are handled automatically. This explains the tests on 'nscaus', which ensure that the targeted scalars are truly user scalars. By specific physics, we mean only those which are handled in specific modules of the code, such as coal, combustion, electric arcs (see usppmo).
Other variables.
Specific physics variables.
Variables for coal particles.
Variables for droplets.
Variables for carrying gas.
Variables of State; User defined Variables.
State variables for coal particles or fuel droplets.
State variables for carrier gas phase.
Force postprocessing of projection of some variables at boundary with no reconstruction. This is handled automatically if the second bit of a field's 'post_vis' key value is set to 1 (which amounts to adding 2 to that key value).
field_get_id returns -1 if field does not exist
Enforce existence of 'tplus' and 'tstar' fields, so that a boundary temperature or Nusselt number may be computed using the post_boundary_temperature or post_boundary_nusselt subroutines. When postprocessing of these quantities is activated, those fields are present, but if we need to compute them in the cs_user_extra_operations user subroutine without postprocessing them, forcing the definition of these fields to save the values computed for the boundary layer is necessary.