.. meta:: :description: The current Flow360 CFD simulation Mesh Processor and Solver input configuration parameters. Boundaries & Sliding Interfaces mesh types, nondimensionalization. Solver Configuration ******************** The Flow360.json file defines the solver settings used during the CFD solution. Most input quantities in the case configuration file (Flow360.json) are dimensionless. The conventions of nondimensional inputs in Flow360 are explained in detail at the :ref:`nondimensional inputs knowledge base ` and the :ref:`non-dimensionalization in Flow360 tutorial `. .. _geometryConfiguration: :code:`geometry` ---------------- **OPTIONAL** The :code:`geometry` section defines the geometric reference values. These parameters are used in the calculation of nondimensional loads reported (e.g., :math:`CL`, :math:`CMy`, etc.). Please refer to :ref:`nondimensional inputs knowledge base ` and the :ref:`non-dimensionalization in Flow360 tutorial ` for further information on how to define these. .. csv-table:: :file: Tables/geometryTable.csv :widths: 25, 25, 50 :header-rows: 1 :delim: @ **Example** .. literalinclude:: Files/geometryExample.json :linenos: .. _solverConfiguration-freestream: :code:`freestream` ------------------ **REQUIRED** The :code:`freestream` section defines the flow conditions at the freestream. Please refer to :ref:`nondimensional inputs knowledge base ` and the :ref:`non-dimensionalization in Flow360 tutorial ` for further information on how to define these. .. csv-table:: :file: Tables/freestreamTable.csv :widths: 20, 20, 70 :header-rows: 1 :delim: @ **Example** .. literalinclude:: Files/freestreamExample.json :linenos: .. _boundariesParameters: :code:`boundaries` ------------------ **REQUIRED** The :code:`boundaries` section defines the boundary conditions. Each boundary condition is specified by associating the boundary type for each boundary name in the mesh file, as follows: .. literalinclude:: Files/boundaryBase.json :linenos: The "boundary_name" is the name of each individual patch of the grid and is typically of the form "1" for .ugrid files and "vol-1/wall" for .cgns files. Additionally, for .ugrid meshes an optional parameter "name" can be specified within each boundary dictionary to overwrite the numeric "boundary_name" in results. The "name" option takes a string entry. Numerous boundary conditions require the specification of additional options, which are outlined in the table below. For a number of boundaries such as :code:`NoSlipWall`, :code:`IsothermalWall` and :code:`Freestream`, mathematical expressions can be used to define the inputs. Please refer to the :ref:`boundary conditions knowledge base ` for more information. .. csv-table:: :file: Tables/boundariesTable.csv :widths: 15, 25, 70 :header-rows: 1 :delim: @ **Example** .. literalinclude:: Files/boundariesExample.json :linenos: .. _navierStokesSolverParameters: :code:`navierStokesSolver` -------------------------- **OPTIONAL** This section of the configuration file defines the numerical parameters for the Navier-Stokes solver. For more information on setting up these parameters refer to :ref:`Navier-Stokes solver knowledge base `. .. csv-table:: :file: Tables/navierStokesTable.csv :widths: 25 10 65 :header-rows: 1 :delim: @ **Example** .. literalinclude:: Files/navierStokesExample.json :linenos: .. _turbulenceModelSolverParameters: :code:`turbulenceModelSolver` ----------------------------- **OPTIONAL** This section of the configuration file defines the numerical parameters for the turbulence model solver. For more information on setting up these parameters refer to :ref:`the turbulence model solver knowledge base `. .. csv-table:: :file: Tables/turbulenceTable.csv :widths: 25 10 65 :header-rows: 1 :delim: @ **Example** .. literalinclude:: Files/turbulenceModelExample.json :linenos: .. _transitionModelSolverParameters: :code:`transitionModelSolver` ----------------------------- **OPTIONAL** This section of the configuration file defines the numerical parameters for the transition model solver. For more information on setting up these parameters refer to :ref:`the transition model solver knowledge base `. .. csv-table:: :file: Tables/transitionTable.csv :widths: 25 10 60 :header-rows: 1 :delim: @ **Example** .. literalinclude:: Files/transitionModelExample.json :linenos: :code:`initialCondition` ------------------------ **OPTIONAL** This section of the configuration file specifies the initial condition for the simulation. .. csv-table:: :file: Tables/initialTable.csv :widths: 25 15 60 :header-rows: 1 :delim: @ **Example** .. literalinclude:: Files/initialConditionExample.json :linenos: .. _timeSteppingParameters: :code:`timeStepping` -------------------- **OPTIONAL** This section of the configuration file defines the numerical parameters for time stepping. Please refer to the :ref:`time stepping knowledge base ` for further guidance regarding these parameters. .. _table_timeStepping: .. csv-table:: :file: Tables/timeSteppingTable.csv :widths: 25 25 10 65 :header-rows: 1 :delim: @ .. note:: The :code:`timeStepSize` is in solver units (nondimensional), where time-scale is mesh unit divided by freestream speed of sound. So a time of :code:`timeStepSize=1` means the time it takes for sound to travel 1 mesh unit at freestream. **Example** .. literalinclude:: Files/timeSteppingExample.json :linenos: .. _slidingInterfacesParameters: :code:`slidingInterfaces` (list) -------------------------------- **OPTIONAL** This section of the configuration file defines the simulation parameters of a sliding interface. Please refer to the :ref:`knowledge base on sliding interfaces ` for further information. .. csv-table:: :file: Tables/slidingInterfacesTable.csv :widths: 25 10 65 :header-rows: 1 :delim: @ **Example** .. literalinclude:: Files/slidingInterfacesExample.json :linenos: .. _actuatorDisksParameters: :code:`actuatorDisks` (list) ---------------------------- **OPTIONAL** The actuator disk inputs are defined in this section. Please refer to the :ref:`actuator disk knowledge base ` for further information. .. csv-table:: :file: Tables/actuatorDiskTable.csv :widths: 20, 10, 70 :header-rows: 1 :delim: @ **Example** .. literalinclude:: Files/actuatorDiskExample.json :linenos: .. _betDisksInputParameters: :code:`BETDisks` (list) ------------------------ **OPTIONAL** In this section, the Blade Element Theory (BET) model inputs are defined. For detailed information on the parameters, please refer to the :ref:`BET knowledge Base `. To generate the sectional polars the BET translators can be used which are outlined :ref:`here ` with best-practices for the sectional polars inputs available :ref:`here `. A case study of the XV-15 rotor using the steady BET Disk method is available in :ref:`Case Studies `. Because a transient BET Line simulation is simply a time-accurate version of a steady-state BET Disk simulation, most of the parameters below are applicable to both methods. .. csv-table:: :file: Tables/betTable.csv :widths: 20, 10, 70 :header-rows: 1 :delim: @ **Example** .. literalinclude:: Files/BETExample.json :linenos: .. _porousMediaParameters: :code:`porousMedia` (list) -------------------------- **OPTIONAL** This section defines the inputs for the porous media model. For further information please refer to the :ref:`porous media knowledge base `. .. csv-table:: :file: Tables/porousTable.csv :widths: 30, 30, 15, 70 :header-rows: 1 :delim: @ **Example** .. literalinclude:: Files/porousMediaExample.json :linenos: .. _userDefinedDynamicsParameters: :code:`userDefinedDynamics` --------------------------- **OPTIONAL** This section defines the user defined dynamics inputs. An example of how to use the userDefinedDynamics is available :ref:`here `. .. csv-table:: :file: Tables/userDefinedDynamicsTable.csv :widths: 20, 10, 70 :header-rows: 1 :delim: @ **Example** .. literalinclude:: Files/userDefinedDynamicsExample.json :linenos: .. _postProcessingParameters: Output -------------- This section presents all the configuration file inputs regarding solution output. This includes, the surface and volume solutions, as well as slices, isosurfaces and point monitors. Universal nondimensional variables supported by all types of output are presented below: [note]_ .. _universalvariables: .. csv-table:: :file: Tables/UniversalVariablesTable.csv :widths: 25,50 :header-rows: 1 :delim: @ Additional nondimensional variables supported by :ref:`volumeOutput` and :ref:`sliceOutput`: .. _VolumeAndSliceSpecificVariables: .. csv-table:: :file: Tables/VolumeAndSliceSpecific.csv :widths: 25,50 :header-rows: 1 :delim: @ Additional nondimensional variables supported by :ref:`surfaceOutput`: .. _SurfaceSpecificVariables: .. csv-table:: :file: Tables/SurfaceSpecific.csv :widths: 25,50 :header-rows: 1 :delim: @ .. _volumeOutputInputParameters: :code:`volumeOutput` ^^^^^^^^^^^^^^^^^^^^ **OPTIONAL** .. csv-table:: :file: Tables/volumeOutputTable.csv :widths: 25 10 65 :header-rows: 1 :delim: @ **Example** .. literalinclude:: Files/volumeExample.json :linenos: .. _surfaceOutputInputParameters: :code:`surfaceOutput` ^^^^^^^^^^^^^^^^^^^^^ **OPTIONAL** .. csv-table:: :file: Tables/surfaceOutputTable.csv :widths: 25 10 65 :header-rows: 1 :delim: @ **Example** .. literalinclude:: Files/surfaceExample.json :linenos: .. _sliceOutputInputParameters: :code:`sliceOutput` ^^^^^^^^^^^^^^^^^^^ **OPTIONAL** .. csv-table:: :file: Tables/sliceOutputTable.csv :widths: 25 10 65 :header-rows: 1 :delim: @ **Example** .. literalinclude:: Files/sliceExample.json :linenos: .. _isoSurfaceOutputInputParameters: :code:`isoSurfaceOutput` ^^^^^^^^^^^^^^^^^^^^^^^^ **OPTIONAL** .. csv-table:: :file: Tables/isoSurfaceOutputTable.csv :widths: 25 25 10 65 :header-rows: 1 :delim: @ **Example** .. literalinclude:: Files/isoSurfaceConfigExample.json :linenos: .. _monitorOutputInputParameters: :code:`monitorOutput` ^^^^^^^^^^^^^^^^^^^^^ **OPTIONAL** .. csv-table:: :file: Tables/monitorOutputTable.csv :widths: 25 25 10 65 :header-rows: 1 :delim: @ .. note:: Please increase the precision of the input coordinates when probing near the grid boundaries to ensure that the probing location is within the mesh. **Example** .. literalinclude:: Files/monitorExample.json :linenos: .. [note] Since release-23.1.1.0, `previous syntax `_ to specify output variables is being deprecated and not all variables are supported. Users are encouraged to use the new syntax as described in :ref:`this documentation `.