Allow obgc tracers have different reservoir length scales
This update along with an update to MOM6 brings
in the capability to set tracer reservoir (inverse) length scales for
individual obgc tracers via ocean_bgc field_table mechanism.
Tracer resevoir inverse length scales are set as before to 1.0/Lscale_in and
1.0/Lscale_out
Users should be able to specify a multiplicative factor for each obgc
tracer for each IN or OUT direction in the field_table, e.g.,
alk_obc_lfac_in = 0.5
alk_obc_lfac_out = 0.75
The factors are multiplied by the inverse length scales before
reservoir calculations.
The default factors for all tracers are 1.
No answer changes unless non-one factors are specified in field_table
There is also a bugfix to COBALT to allow running in debug mode, log10
must be epsiloned to avoid log(0)
There is a bugfix to generic_tracer_utils to allow running in debug
mode, intent(out) strings must have len=* otherwise we get a crash in
debug mode like:
forrtl: severe (408): fort: (18): Dummy character variable 'STRING' has length 1024 which is greater than actual variable length 200
Allow obgc tracers have different reservoir length scales
Users should be able to specify a multiplicative factor for each obgc tracer for each IN or OUT direction in the field_table, e.g., alk_obc_lfac_in = 0.5 alk_obc_lfac_out = 0.75
The factors are multiplied by the inverse length scales before reservoir calculations.
The default factors for all tracers are 1.
No answer changes unless non-one factors are specified in field_table
There is also a bugfix to COBALT to allow running in debug mode, log10 must be epsiloned to avoid log(0)
There is a bugfix to generic_tracer_utils to allow running in debug mode, intent(out) strings must have len=* otherwise we get a crash in debug mode like: forrtl: severe (408): fort: (18): Dummy character variable 'STRING' has length 1024 which is greater than actual variable length 200