next up previous contents index
Next: 7.1.17 Radiation-transport control (MSrad Up: 7.1 Parameter file: rhd.par Previous: 7.1.15 Dust: dustscheme=dust_bins_01   Contents   Index


7.1.16 Radiation-transport control (general)

In this part of the parameter file the radiation transport module has to be selected. Depending on this selection a couple of additional parameters have to be specified. Table 7.2 gives a list of the parameters and the modules they apply to. The standard routines are now in the MSrad module for local models and the SHORTrad module for global ``star-in-a-box'' models. The LHDrad module is not maintained very much anymore.

Table 7.2: List of radiation transport control parameters and the modules they are relevant for.
Parameter Section LHDrad MSrad SHORTrad
radscheme * * *
opafile * * *
opapath * * *
n_radband   * *
n_radminiter * * *
n_raditer * * *
n_radmaxiter * * *
radraybase * * *
radraystar *   *
c_tminlimit   * *
c_radimplicitmu *   *
c_raditereps *   *
c_raditerstep *   *
n_radtheta   *  
n_radphi   *  
n_radsubray   *  
n_radthickpoint * *  
n_radtaurefine * *  
n_radrsyslevel   *  
n_radoutput   *  
c_radtcool   *  
c_raddcool   *  
c_radscool   *  
c_radtinci   *  
c_raddinci   *  
c_radtvisdtau *    
c_radtvis *    
c_radhtautop   * *
c_radcourant * * *
c_radcourantmax * * *
c_radmaxeichange * * * character radscheme

So far, there exist three different radiation transport modules. The active on can be selected e.g. with
character radscheme f=A80 b=80 n='Radiation transport scheme' &
  c0='LHDrad/MSrad/SHORTrad' &
  c1='None (skip radiation transport step entirely)'
Possible values are integer n_radband

It can be specified whether the grey opacity table or the binned frequency-dependent part of the opacity table is used during the computation. The grey part contains only one bin. The other (possibly non-grey) contains one or more bins depending on the table chosen. The parameter is specified with e.g.
integer n_radband f=I4 b=4 n='Number of frequency bins' &
  c0='1: grey opacities' &
  c1='2: non-grey opacities (if available from table)' &
  c2='3: two bands: 1.grey, 2.CO (density via XCO)' &
  c3='4: two bands: 1.grey, 2.CO (density from chemistry)'
Allowed values are integer n_radminiter

Usually the stability considerations dictate a radiative time step smaller than the hydrodynamics or tensor-viscosity time step. To remedy this situation it is possible to allow several radiation transport steps per global time step. Hitherto, all three radiation transport modules support this iteration. The minimum number of iterations (radiative sub-steps) can be specified e.g. with
integer n_radminiter f=I4 b=4 &
  n='Minimum number of radiation transport iterations' c0=8
If less iterations are needed the time step limit for the next step is increased. This value will in almost any case (for explicit radiation transport) be set to 1. In the implicit case it is set to a higher value (typically 5). integer n_raditer

After each complete radiative time step the recommendation for the next time step will be chosen so that n_raditer iterations will (probably) needed. The parameter can be set e.g. with
integer n_raditer f=I4 b=4 &
    n='Number of radiation transport iterations' c0=10
For a simulation of a solar-type star (with comparatively long radiative time scales) it will typically be set to 1. For stars with shorter radiative time scales values around 10 may be considered. All three radiation transport modules understand this parameter. integer n_radmaxiter

The absolute maximum number of iterations can be specified e.g. with
integer n_radmaxiter f=I4 b=4 &
    n='Maximum number of rad. transport iterations' c0=30
If more iterations are needed the computation for the current time step is stopped and resumed with a smaller one (which means that the hydrodynamics and the tensor-viscosity step have to be done again). Usually, n_radmaxiter will either be set to a value somewhat larger than the recommended number of iterations (n_raditer) or to 0 which disables the check for too many iterations completely. This can be safely allowed in many cases and has the advantage that there is no need to save the initial model before calling the radiation transport module, which saves some memory. To disable the iteration of the radiation transport sub-step set n_radminiter=n_raditer=n_radmaxiter=1. All three radiation transport modules understand this parameter. character radraybase

Using the modules LHDrad or SHORTrad, the orientation of the base axis system can be selected e.g. with
character radraybase f=A80 b=80 n='Base axis system' &
  c0='SHORTrad: unity/random/randomcube/randomgroup/alternate' &
  c1='MSrad: lobatto/dblgaus'
Allowed values for radscheme=SHORTrad are: Because typically only a relatively small number of rays is chosen per time step (with radraystar) it is advisable to vary the directions of the rays (by choosing radraybase=random or randomgroup) to cover the entire sphere at least over a longer time.
Allowed values for radscheme=MSrad are: character radraystar

Using the modules LHDrad or SHORTrad, the list of ray directions (i.e. the number of rays and their coordinates) relative to the base axis system can be specified with e.g.
character radraystar f=A80 b=80 n='List of relative ray directions' &
  c0='x1(1)/x2(1)/x3(1)/oktaeder(3)/tetraeder(4)/cube(4)' &
Examples for allowed values are Several other choices are possible, which are meant for test purposes only. Choosing one of the five Platonic solids (Oops! ``German-Greek'' names only, so far) means that the 3 to 10 rays are equally distributed over the solid angle (from the center to each corner of the respective solid). Check the complete list of options in subroutine rhd_rad3d_RaySystem. real c_tminlimit

A minimum temperature can be set, that is enforced by the radiation transport modules MSrad3D and SHORTrad by adding energy to the too cool cells, e.g. with
real c_tminlimit f=E15.8 b=4 &
  n='Enforced minimum temperature for radiation transport step' u=K &
  c0='<=0.0: off (default); 500.0: reasonable value'
400.0 real c_radimplicitmu

So far, only the LHDrad and the SHORTrad module support implicit radiation transport. It can be activated with the parameter
real c_radimplicitmu f=E15.8 b=4 &
    n='Implicitness parameter for radiation transport'            u=1 &
    c0='0.0: explicit / 0.5: time centered / 1.0: fully implicit'
Allowed values are Values outside this range do not have much meaning. The implicit transport does not work efficiently yet: It does not yield significantly larger time steps than possible with a sequence of purely explicit sub time steps. Additionally, it turns out that the hydrodynamics runs into trouble if a too large time step (still well within the Courant condition) is requested. real c_raditereps

With activated implicit radiation transport (LHDrad and SHORTrad modules only) the requested convergence accuracy of the iteration can be set e.g. with
real c_raditereps f=E15.8 b=4 &
    n='Relative accuracy for radiation iteration'                 u=1 &
    c0='Typical value: 1.0E-03'
2.0E-03 real c_raditerstep

With activated implicit radiation transport (LHDrad and SHORTrad modules only) the step size of the iteration can be restricted with e.g.
real c_raditerstep f=E15.8 b=4 &
    n='Step size of radiation iteration'                          u=1 &
    c0='Typical values: 0.7,0.81'
Allowed values are This value has to be chosen carefully to get optimal performance. Is the step size too small the convergence is safe but too slow. A too large step size inhibits convergence and leads to a decrease in the time step, which results in a bad performance, too.

next up previous contents index
Next: 7.1.17 Radiation-transport control (MSrad Up: 7.1 Parameter file: rhd.par Previous: 7.1.15 Dust: dustscheme=dust_bins_01   Contents   Index