Runtime parameters
The behavior of the network and EOS are controlled by many runtime
parameters. These parameters are defined in plain-text files
_parameters located in the different directories that hold the
microphysics code. At compile time, a script in the AMReX build
system, findparams.py, locates all of the _parameters files that
are needed for the given choice of network, integrator, and EOS, and
assembles all of the runtime parameters into a set of header files
(using the write_probin.py script).
Parameter definitions take the form:
# comment describing the parameter
name data-type default-value priority
Here, the priority is simply an integer. When two directories define the same parameter, but with different defaults, the version of the parameter with the highest priority takes precedence. This allows specific implementations to override the general parameter defaults.
The documentation below is automatically generated, using the comments
in the _parameters files.
- BackwardEuler
- ForwardEuler
- QSS
- RKC
- VODE
- ase
- breakout
- burn_cell
- burn_cell_primordial_chem
- burn_cell_sdc
- cj_detonation
- constant
- constant_opacity
- eos_cell
- gamma_law
- helmholtz
- integration
- make_table
- multigamma
- networks
- nse_compatibility
- nse_solver
- nse_table_cell
- nse_tabular
- polytrope
- powerlaw
- primordial_chem
- rad_power_law
- rprox
- screening
- subch_approx
- subch_base
- subch_full
- subch_simple
- test_aprox_rates
- test_ase
- test_conductivity
- test_eos
- test_jac
- test_linear_algebra
- test_neutrino_cooling
- test_nse
- test_nse_interp
- test_part_func
- test_react
- test_rhs
- test_screening
- test_screening_templated
- test_sdc
- test_sdc_vode_rhs
- tillotson
- triple_alpha_plus_cago
- unit_test