Push notifications in your browser are not yet configured.

You are not logged in, you may not see all content and functionalities. If you have an account, please login .

Push notifications in your browser are not yet configured.

## External parameters LAI, PLCOV and ROOTDP

Earlier these parameters were adjusted daily with a seasonal sine

(for LAI and PLCOV with min/max values in the extPar data).

Now, for LAI and PLCOV there are 12 monthly values in the extpar data,

from which the fair value is determined (linear interpolation).

For ROOTDP there is nothing like that: – Why is this not adapted consistently? – How is ROOTDP adapted to the day of the year? With a sine or something else (e.g., depending on LAI ?

Thanks for your help,

Steffen

Steffen wrote:

“Earlier these parameters were adjusted daily with a seasonal sine

(for LAI and PLCOV with min/max values in the extPar data)”

Correct, but also for ROOTDP . There are 5 different options for the treatment of ROOTDP (0 .le. itype_rootdp .le. 4), see src_2s_fields.f90

in any INT2LM version since Version 1.9, for example.

“Now, for LAI and PLCOV there are 12 monthly values in the extpar data,

from which the fair value is determined (linear interpolation).”

Correct, if you have chosen the corresponding dataset option in EXTPAR in order to get these data,

and the corresponding option (itype_ndvi) in INT2LM.

“For ROOTDP there is nothing like that:

- Why is this not adapted consistently?

- How is ROOTDP adapted to the day of the year? With a sine or something else (e.g., depending on LAI ?”

That’s not true!

The 5 options for ROOTDP still exist, also in the most recent INT2LM version 2.0.

Three of them (itype_rootdp=0,2,3) calculate an annual cycle for ROOTDP , using the same sin-function as for LAI and PLCOV .

Consistent adaptation to 12-monthly values: do you have appropriate data for ROOTDP ? Or do you know sources for such data?

Hans-Jürgen