You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current standard name entries include a "type" element that has information about the variable units, type and kind. As an example:
<standard_name name="exner_function"
long_name="exner function, (p/p0)^(Rd/cp), where p0 is 1000 hPa">
<type kind="kind_phys" units="1">real</type>
</standard_name>
While units and type are both important to distinguishing the use of a variable, the "kind" entry is a vestige of this dictionary's origin in a UFS context for CCPP, and is not generalizable to other contexts. My opinion is that this information should be removed, but I am hoping to hear others' opinions.
The text was updated successfully, but these errors were encountered:
mkavulich
changed the title
Remove "kind" from standard name entries
[release/v1] Remove "kind" from standard name entries
Mar 21, 2025
While I'm not sure "... vestige of this dictionary's origin in a UFS context ..." is accurate (I created it in 2020 without any UFS-specific variables), I agree that kind is a variable property, not a physical one.
On the other hand, it is a useful entry for CCPP users in that it indicates the 'normal' usage of the standard name. Use of standard kind and units properties lowers the cost of calling a scheme by avoiding unnecessary kind and unit conversions. Is there a way to generalize the dictionary beyond the CCPP without making it less useful to the CCPP community?
The current standard name entries include a "type" element that has information about the variable units, type and kind. As an example:
While units and type are both important to distinguishing the use of a variable, the "kind" entry is a vestige of this dictionary's origin in a UFS context for CCPP, and is not generalizable to other contexts. My opinion is that this information should be removed, but I am hoping to hear others' opinions.
The text was updated successfully, but these errors were encountered: