Problem CLM-Output variable EVATRA_SUM – in #9: CCLM
in #9: CCLM
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>
It is really the case that “
<span class="caps">
EVATRA
</span>
_SUM” is defined in the vartab (obviously since the very old
<span class="caps">
COMSO
</span>
version 3.21).
<br/>
But this the only place where you can find this name.
<br/>
Especially, no variable that will be calculated is assigned to this entry.
<br/>
And there is also not an “IF
<span class="caps">
EVATRA
</span>
_SUM …” in src_output where
<span class="caps">
EVATRA
</span>
_SUM is calculated from other variables
<br/>
Thus, to my understanding, it can’t be used as an output variable.
</p>
<p>
Looking into the misc.global_3 file in the
<span class="caps">
DOCS
</span>
folder (looking into this misc.global files is always a good advice to do!!!!)
<br/>
tells you that “
<span class="caps">
EVATRA
</span>
_SUM” belongs to a group of variables, which will be used for the computation of the water budget
<br/>
but that this computation of the water budget is not yet implemented.
<br/>
And this “not yet implemented” seems to be still the case!!!
</p>
<p>
Concerning the list of output variables on the
<span class="caps">
CLM
</span>
-Homepage.
<br/>
This list, in principle, is just a copy of the the src_setup_vartab.f90.
<br/>
Thus, all entries in the vartab, including those that are meaningless, also appear in the list.
<br/>
Whether this can be avoided easily, I don’t know.
</p>
<p>
Furthermore: my explanations for
<span class="caps">
EVATRA
</span>
_SUM are also valid for
<span class="caps">
TRA
</span>
_SUM – defined only in setup-vartab, not used/referenced elsewhere.
<br/>
Thus, I don’t think that your results for
<span class="caps">
TRA
</span>
_SUM are “plausible”.
<br/>
I don’t know exactly what happens in src_output.
<br/>
However, it would make sense to compare the
<span class="caps">
TRA
</span>
_SUM results with the results of those variables that you have defined
<br/>
before
<span class="caps">
TRA
</span>
_SUM in your
<span class="caps">
GRIBOUT
</span>
(
<span class="caps">
HPBL
</span>
or
<span class="caps">
TOP
</span>
_CON or
<span class="caps">
BAS
</span>
_CON).
<br/>
Do the same for
<span class="caps">
EVATRA
</span>
_SUM (compare it with SI, or
<span class="caps">
SLI
</span>
or ….) and, please, report your findings.
</p>
<p>
Conclusion:
<br/>
revision of the code in order to avoid such errors is urgently needed!!!
</p>
<p>
Hans-Juergen
</p>
<p>
It is really the case that “
<span class="caps">
EVATRA
</span>
_SUM” is defined in the vartab (obviously since the very old
<span class="caps">
COMSO
</span>
version 3.21).
<br/>
But this the only place where you can find this name.
<br/>
Especially, no variable that will be calculated is assigned to this entry.
<br/>
And there is also not an “IF
<span class="caps">
EVATRA
</span>
_SUM …” in src_output where
<span class="caps">
EVATRA
</span>
_SUM is calculated from other variables
<br/>
Thus, to my understanding, it can’t be used as an output variable.
</p>
<p>
Looking into the misc.global_3 file in the
<span class="caps">
DOCS
</span>
folder (looking into this misc.global files is always a good advice to do!!!!)
<br/>
tells you that “
<span class="caps">
EVATRA
</span>
_SUM” belongs to a group of variables, which will be used for the computation of the water budget
<br/>
but that this computation of the water budget is not yet implemented.
<br/>
And this “not yet implemented” seems to be still the case!!!
</p>
<p>
Concerning the list of output variables on the
<span class="caps">
CLM
</span>
-Homepage.
<br/>
This list, in principle, is just a copy of the the src_setup_vartab.f90.
<br/>
Thus, all entries in the vartab, including those that are meaningless, also appear in the list.
<br/>
Whether this can be avoided easily, I don’t know.
</p>
<p>
Furthermore: my explanations for
<span class="caps">
EVATRA
</span>
_SUM are also valid for
<span class="caps">
TRA
</span>
_SUM – defined only in setup-vartab, not used/referenced elsewhere.
<br/>
Thus, I don’t think that your results for
<span class="caps">
TRA
</span>
_SUM are “plausible”.
<br/>
I don’t know exactly what happens in src_output.
<br/>
However, it would make sense to compare the
<span class="caps">
TRA
</span>
_SUM results with the results of those variables that you have defined
<br/>
before
<span class="caps">
TRA
</span>
_SUM in your
<span class="caps">
GRIBOUT
</span>
(
<span class="caps">
HPBL
</span>
or
<span class="caps">
TOP
</span>
_CON or
<span class="caps">
BAS
</span>
_CON).
<br/>
Do the same for
<span class="caps">
EVATRA
</span>
_SUM (compare it with SI, or
<span class="caps">
SLI
</span>
or ….) and, please, report your findings.
</p>
<p>
Conclusion:
<br/>
revision of the code in order to avoid such errors is urgently needed!!!
</p>
<p>
Hans-Juergen
</p>
It is really the case that “
EVATRA
_SUM” is defined in the vartab (obviously since the very old
COMSO
version 3.21).
But this the only place where you can find this name.
Especially, no variable that will be calculated is assigned to this entry.
And there is also not an “IF
EVATRA
_SUM …” in src_output where
EVATRA
_SUM is calculated from other variables
Thus, to my understanding, it can’t be used as an output variable.
Looking into the misc.global_3 file in the
DOCS
folder (looking into this misc.global files is always a good advice to do!!!!)
tells you that “
EVATRA
_SUM” belongs to a group of variables, which will be used for the computation of the water budget
but that this computation of the water budget is not yet implemented.
And this “not yet implemented” seems to be still the case!!!
Concerning the list of output variables on the
CLM
-Homepage.
This list, in principle, is just a copy of the the src_setup_vartab.f90.
Thus, all entries in the vartab, including those that are meaningless, also appear in the list.
Whether this can be avoided easily, I don’t know.
Furthermore: my explanations for
EVATRA
_SUM are also valid for
TRA
_SUM – defined only in setup-vartab, not used/referenced elsewhere.
Thus, I don’t think that your results for
TRA
_SUM are “plausible”.
I don’t know exactly what happens in src_output.
However, it would make sense to compare the
TRA
_SUM results with the results of those variables that you have defined
before
TRA
_SUM in your
GRIBOUT
(
HPBL
or
TOP
_CON or
BAS
_CON).
Do the same for
EVATRA
_SUM (compare it with SI, or
SLI
or ….) and, please, report your findings.
Conclusion:
revision of the code in order to avoid such errors is urgently needed!!!
It is really the case that “ EVATRA _SUM” is defined in the vartab (obviously since the very old COMSO version 3.21).
But this the only place where you can find this name.
Especially, no variable that will be calculated is assigned to this entry.
And there is also not an “IF EVATRA _SUM …” in src_output where EVATRA _SUM is calculated from other variables
Thus, to my understanding, it can’t be used as an output variable.
Looking into the misc.global_3 file in the DOCS folder (looking into this misc.global files is always a good advice to do!!!!)
tells you that “ EVATRA _SUM” belongs to a group of variables, which will be used for the computation of the water budget
but that this computation of the water budget is not yet implemented.
And this “not yet implemented” seems to be still the case!!!
Concerning the list of output variables on the CLM -Homepage.
This list, in principle, is just a copy of the the src_setup_vartab.f90.
Thus, all entries in the vartab, including those that are meaningless, also appear in the list.
Whether this can be avoided easily, I don’t know.
Furthermore: my explanations for EVATRA _SUM are also valid for TRA _SUM – defined only in setup-vartab, not used/referenced elsewhere.
Thus, I don’t think that your results for TRA _SUM are “plausible”.
I don’t know exactly what happens in src_output.
However, it would make sense to compare the TRA _SUM results with the results of those variables that you have defined
before TRA _SUM in your GRIBOUT ( HPBL or TOP _CON or BAS _CON).
Do the same for EVATRA _SUM (compare it with SI, or SLI or ….) and, please, report your findings.
Conclusion:
revision of the code in order to avoid such errors is urgently needed!!!
Hans-Juergen