Question about int2lm_org using EXTPAR for external boundaries – in #10: INT2LM

in #10: INT2LM

The problem is the parameter itype_albedo in CONTRL .
This parameter does not yet exist in IN2LM version 1.10.

If you want to you INT2LM_1.10 you have to
- run INT2LM without the itype_albedo parameter
- extract ALB _RAD and ALB _SAT from your ext. dataset and adapt them to you model domain
- include them by hand into the laf-file (only there) using NCO command ncks -C -A -v …..

Or use a more recent INT2LM version which is able to treat this kind of albedo

Hans-Jürgen

  @hans-jürgenpanitz in #1f27c7e

The problem is the parameter itype_albedo in CONTRL .
This parameter does not yet exist in IN2LM version 1.10.

If you want to you INT2LM_1.10 you have to
- run INT2LM without the itype_albedo parameter
- extract ALB _RAD and ALB _SAT from your ext. dataset and adapt them to you model domain
- include them by hand into the laf-file (only there) using NCO command ncks -C -A -v …..

Or use a more recent INT2LM version which is able to treat this kind of albedo

Hans-Jürgen

The problem is the parameter itype_albedo in CONTRL .
This parameter does not yet exist in IN2LM version 1.10.

If you want to you INT2LM_1.10 you have to
- run INT2LM without the itype_albedo parameter
- extract ALB _RAD and ALB _SAT from your ext. dataset and adapt them to you model domain
- include them by hand into the laf-file (only there) using NCO command ncks -C -A -v …..

Or use a more recent INT2LM version which is able to treat this kind of albedo

Hans-Jürgen