4.3.1 Control environment variables

The environment variables that control the script are listed in the following. It is convenient to put them into the configure resource file .configurerc that is read by the configure script.

4.3.1.1 F90_COLOR

Activate color output of the configure script:

• 0: standard black & white output
• 1: color output

4.3.1.2 F90_COMPILER

Fortran compiler, e.g.:

• '': a machine-dependent default is chosen individually for each architecture
• f90: general default
• gfortran: GNU compiler
• ifort: Intel compiler

See Sect.4.6 for a more complete list and further details.

4.3.1.3 F90_PREFLAGS

Compiler flags to be put at the beginning of the list. Usually, the list of compiler flags produced by the configure script should be pretty complete. But you might want to add special switches like '-Bstatic' to enforce static linking of libraries.

• '': no extra flags

4.3.1.4 F90_POSTFLAGS

Compiler flags to be put at the end of the list. Usually, the list of compiler flags produced by the configure script should be pretty complete. However, you might want to overwrite some settings. This can be done by setting this variable to a none-empty value because typically a compiler should interpret the flags from left to right.

• '': no extra flags

4.3.1.5 F90_PARALLEL

Parallelization scheme:

• scalar: no parallelization (default)
• openmp: OpenMP (appropriate for CO5BOLD)
• auto: auto-parallelization (not implemented for all machines)

4.3.1.6 F90_DEBUG

Debugging level:

• 0: no extra debugging information produced, full optimization is chosen (default)
• 1: standard debugging mode (typically switch '-g' instead of '-fast')
• 2: other debugging (or array checking) modes possible if implemented for the requested machine

4.3.1.7 F90_OPTIMIZE

Optimization:

• 0: no explicit optimization (default if F90_DEBUG=1)
• 1: try to find automatically sensible optimization flags. That's the default if F90_DEBUG=0. However, often it is better to specify the optimization flags explicitly
• -ipo -O3 -xHost (example): set the optimization flags by hand. This is a better way to specify the optimization than using F90_POSTFLAGS

4.3.1.8 F90_LHDRAD

LHDrad radiation transport:

• 0: do not activate (compile and link) this module (default)
• 1: activate this radiation transport module

4.3.1.9 F90_MSRAD

MSrad radiation transport:

• 0: do not activate (compile and link) this module (default)
• 1: activate this radiation transport module

4.3.1.10 F90_SHORTRAD

SHORTrad radiation transport:

• 0: do not activate (compile and link) this module (default)
• 1: activate this radiation transport module

4.3.1.11 F90_CHEM

CHEM module (chemical reaction networks):

• 0: do not activate (compile and link) this module (default)
• 1: activate this source step module

Setting this variable to 1 will set F90_DUST=1. The compiler is then called with -Drhd_chem01.

4.3.1.12 F90_HION

HION module (time-dependent hydrogen ionization):

• 0: do not activate (compile and link) this module (default)
• 1: activate this source step module

Setting this variable to 1 will set F90_DUST=1. The compiler is then called with -Drhd_hion01.

4.3.1.13 F90_DUST

DUST module:

• 0: do not activate (compile and link) this module (default)
• 1: activate this source step module

If this variable is set to 1 the compiler is called with -Drhd_box_quc01=1, see Sect.4.4.1.6.

4.3.1.14 F90_MHD

MHD module:

• 0: do not activate (compile and link) this module (default)
• 1: activate this magnetohydrodynamics module (MHD HLL solver)

If CO5BOLD is compiled with the MHD module, your start model should include magnetic fields, otherwise zero magnetic fields are created and used. In the latter case, the magnetic field arrays are not written into the output files.

4.3.1.15 F90_TWEAK

TWEAK module:

• 0: do not activate (compile and link) this module (default)
• 1: activate the TWEAK module rhd_tweak_module.F90
• rhd_tweak_name_module: activate the TWEAK module with this name

A TWEAK module is a user-provided set of routines performing some simple but non-standard task.

4.3.1.16 F90_MACHINE

Explicit machine specification. This is usually not necessary, use 'local' or '' instead.

• '': local machine
• sun4u: Sun
• ...: See the header of the configure script for an up-to-date list
• local: local machine (default)
• dummy: do not use any machine-dependent flags but use module selections
• empty: compiler flags are composed from F90_PREFLAGS and F90_POSTFLAGS only

4.3.1.17 F90_BASEPATH

Path for the CO5BOLD base directory.

• '': the configure script tries to determine the base-directory name automatically (default). This should work if the local directory is located somewhere below .../hd/rhd/
• otherwise: this string is used as base directory name (e.g.tex2html_verb_mark>214)

Some examples can be found in Sect.4.2.