Before starting the run you need to select the type and value of the boundary
conditions for all equations. Please note that the value should correspond to
the type. All equations allow for following types of boundary conditions:
The particular equation will be activated if the boundary condition type for
it is other than OFF
To set up boundary conditions:
The workflow will not allow the user all particle components (ions[1:NION]+electrons) to be run predictively. At least one of them shall be set to OFF (this component will be computed from quasi-neutrality condition).
!!! If electron density is solved, all ions with ni_bnd_type=OFF will be computed from the quasineutrality condition and scaled proportional to specified ni_bnd_value or inversely proportional to their charge, charge_proportional. This is defined by option: ni_from_quasineutrality.
You can set up the boundary conditions for impurity ions in a similar way as
for main ions.
!!! Note, that at the moment only types: OFF; value and value_from_input_CPO are accepter by impurity
solver.
To set up boundary conditions:
Interface for impurity boundary condition has additional option, coronal_distribution, that allow to preset the edge
values or entire profiles of individual ionization states from coronal distribution. In tis case only single value is required to be specified for
each impurity boundary value.
The options are:
!!! AT THE MOMENT BOUNDARY CONDITIONS FOR NEUTRAL VELOCITIES ARE DISABLED, MIGHT BE ADDED ON REQUEST
Note, that ALL values should be specified in the order: {1, 2, 3 ...NION, 1, 2, 3, ...NIMP}
To set up boundary conditions:
You are going to start the ETS run from some input shot, which might contain
some conflicting rho grids saved to different CPOs.
Thus there is a choice for the user to decide on the grid on which the
starting profiles should be load by the
worflow, Interpolation_of_input_profiles.
To define the interpolation grid select: