External parameters LAI, PLCOV and ROOTDP – in #11: EXTPAR / WebPEP
in #11: EXTPAR / WebPEP
Cookies disclaimer
Our site saves small pieces of text information (cookies) on your
device in order to verify your login. These cookies are essential
to provide access to resources on this website and it will not
work properly without.
Learn more
<p>
Earlier these parameters were adjusted daily with a seasonal sine
<br/>
(for
<span class="caps">
LAI
</span>
and
<span class="caps">
PLCOV
</span>
with min/max values in the extPar data).
<br/>
Now, for
<span class="caps">
LAI
</span>
and
<span class="caps">
PLCOV
</span>
there are 12 monthly values in the extpar data,
<br/>
from which the fair value is determined (linear interpolation).
</p>
<p>
For
<span class="caps">
ROOTDP
</span>
there is nothing like that:
– Why is this not adapted consistently?
– How is
<span class="caps">
ROOTDP
</span>
adapted to the day of the year? With a sine or something else (e.g., depending on
<span class="caps">
LAI
</span>
?
</p>
<p>
Thanks for your help,
<br/>
Steffen
</p>
<p>
Earlier these parameters were adjusted daily with a seasonal sine
<br/>
(for
<span class="caps">
LAI
</span>
and
<span class="caps">
PLCOV
</span>
with min/max values in the extPar data).
<br/>
Now, for
<span class="caps">
LAI
</span>
and
<span class="caps">
PLCOV
</span>
there are 12 monthly values in the extpar data,
<br/>
from which the fair value is determined (linear interpolation).
</p>
<p>
For
<span class="caps">
ROOTDP
</span>
there is nothing like that:
– Why is this not adapted consistently?
– How is
<span class="caps">
ROOTDP
</span>
adapted to the day of the year? With a sine or something else (e.g., depending on
<span class="caps">
LAI
</span>
?
</p>
<p>
Thanks for your help,
<br/>
Steffen
</p>
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
?
<p>
Steffen wrote:
</p>
<p>
“Earlier these parameters were adjusted daily with a seasonal sine
<br/>
(for
<span class="caps">
LAI
</span>
and
<span class="caps">
PLCOV
</span>
with min/max values in the extPar data)”
</p>
<p>
Correct, but also for
<span class="caps">
ROOTDP
</span>
. There are 5 different options for the treatment of
<span class="caps">
ROOTDP
</span>
(0 .le. itype_rootdp .le. 4), see src_2s_fields.f90
<br/>
in any INT2LM version since Version 1.9, for example.
</p>
<p>
“Now, for
<span class="caps">
LAI
</span>
and
<span class="caps">
PLCOV
</span>
there are 12 monthly values in the extpar data,
<br/>
from which the fair value is determined (linear interpolation).”
</p>
<p>
Correct, if you have chosen the corresponding dataset option in
<span class="caps">
EXTPAR
</span>
in order to get these data,
<br/>
and the corresponding option (itype_ndvi) in INT2LM.
</p>
<p>
“For
<span class="caps">
ROOTDP
</span>
there is nothing like that:
<br/>
- Why is this not adapted consistently?
<br/>
- How is
<span class="caps">
ROOTDP
</span>
adapted to the day of the year? With a sine or something else (e.g., depending on
<span class="caps">
LAI
</span>
?”
</p>
<p>
That’s not true!
<br/>
The 5 options for
<span class="caps">
ROOTDP
</span>
still exist, also in the most recent INT2LM version 2.0.
<br/>
Three of them (itype_rootdp=0,2,3) calculate an annual cycle for
<span class="caps">
ROOTDP
</span>
, using the same sin-function as for
<span class="caps">
LAI
</span>
and
<span class="caps">
PLCOV
</span>
.
<br/>
Consistent adaptation to 12-monthly values: do you have appropriate data for
<span class="caps">
ROOTDP
</span>
? Or do you know sources for such data?
</p>
<p>
Hans-Jürgen
</p>
<p>
Steffen wrote:
</p>
<p>
“Earlier these parameters were adjusted daily with a seasonal sine
<br/>
(for
<span class="caps">
LAI
</span>
and
<span class="caps">
PLCOV
</span>
with min/max values in the extPar data)”
</p>
<p>
Correct, but also for
<span class="caps">
ROOTDP
</span>
. There are 5 different options for the treatment of
<span class="caps">
ROOTDP
</span>
(0 .le. itype_rootdp .le. 4), see src_2s_fields.f90
<br/>
in any INT2LM version since Version 1.9, for example.
</p>
<p>
“Now, for
<span class="caps">
LAI
</span>
and
<span class="caps">
PLCOV
</span>
there are 12 monthly values in the extpar data,
<br/>
from which the fair value is determined (linear interpolation).”
</p>
<p>
Correct, if you have chosen the corresponding dataset option in
<span class="caps">
EXTPAR
</span>
in order to get these data,
<br/>
and the corresponding option (itype_ndvi) in INT2LM.
</p>
<p>
“For
<span class="caps">
ROOTDP
</span>
there is nothing like that:
<br/>
- Why is this not adapted consistently?
<br/>
- How is
<span class="caps">
ROOTDP
</span>
adapted to the day of the year? With a sine or something else (e.g., depending on
<span class="caps">
LAI
</span>
?”
</p>
<p>
That’s not true!
<br/>
The 5 options for
<span class="caps">
ROOTDP
</span>
still exist, also in the most recent INT2LM version 2.0.
<br/>
Three of them (itype_rootdp=0,2,3) calculate an annual cycle for
<span class="caps">
ROOTDP
</span>
, using the same sin-function as for
<span class="caps">
LAI
</span>
and
<span class="caps">
PLCOV
</span>
.
<br/>
Consistent adaptation to 12-monthly values: do you have appropriate data for
<span class="caps">
ROOTDP
</span>
? Or do you know sources for such data?
</p>
<p>
Hans-Jürgen
</p>
“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?
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