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
Currently, certain variables in GFS_Diagnostics.F90 have unclear descriptions/metadata. These variables are being documented in a table in the UFS WM User's Guide (via PR #2277) so that users and developers can easily reference the meaning of the diag_table variables they might like to add. This will help resolve UFS WM Issue #2032.
A few examples, especially related to smoke/aerosols:
GFS_Diagnostics.F90 describes emanoc as 'emission of anoc for thompson mp'. We need to know what "anoc" is or what the abbreviation stands for in order to provide clear documentation in the Weather Model User's Guide.
For emseas, the definition is 'emission of seas for smoke.' Is "seas" short for "seasalt"?
lu_nofire is defined as 'lu nofire pixes.' What does "lu" mean/stand for and what are "pixes"?
Similarly, lu_qfire is defined as 'lu qfire pixes.' What is qfire?
Other definitions seem to be wrong. For example, both xtts and xzts are defined as "NSST d(xt)/d(ts)," but it seems like xzts should be defined as "NSST d(xz)/d(ts)".
Overall, GFS_Diagnostics.F90 could benefit from explicit descriptions throughout. There are many other abbreviations in GFS_Diagnostics.F90 that we have clarified with developers and spelled out in the draft WM PR linked above. It would be helpful to incorporate these changes directly into the fv3atm code directly.
Solution
Spell out abbreviations and correct typos in GFS_Diagnostics.F90.
Alternatives
Open to ideas. Ultimately, it would be great to get this file and others into Doxygen so that documentation can be pulled directly from the code, but that would be a long-term goal.
Testing:
N/A. Issues in code metadata can be seen on examination. No run required.
Dependent PRs:
Directly reference any issues or PRs in this or other repositories that this is related to, and describe how they are related. Example:
@gspetro-NOAA Sure, emanoc is the anthropogenic organic carbon emission; lu is land use; lu_* are arrays to keep track of different fire types, e.g. grass fires.
Description
Currently, certain variables in
GFS_Diagnostics.F90
have unclear descriptions/metadata. These variables are being documented in a table in the UFS WM User's Guide (via PR #2277) so that users and developers can easily reference the meaning of thediag_table
variables they might like to add. This will help resolve UFS WM Issue #2032.A few examples, especially related to smoke/aerosols:
GFS_Diagnostics.F90
describesemanoc
as 'emission of anoc for thompson mp'. We need to know what "anoc" is or what the abbreviation stands for in order to provide clear documentation in the Weather Model User's Guide.emseas,
the definition is 'emission of seas for smoke.' Is "seas" short for "seasalt"?lu_nofire
is defined as 'lu nofire pixes.' What does "lu" mean/stand for and what are "pixes"?lu_qfire
is defined as 'lu qfire pixes.' What is qfire?Other definitions seem to be wrong. For example, both
xtts
andxzts
are defined as "NSST d(xt)/d(ts)," but it seems likexzts
should be defined as "NSST d(xz)/d(ts)".Overall,
GFS_Diagnostics.F90
could benefit from explicit descriptions throughout. There are many other abbreviations inGFS_Diagnostics.F90
that we have clarified with developers and spelled out in the draft WM PR linked above. It would be helpful to incorporate these changes directly into the fv3atm code directly.Solution
Spell out abbreviations and correct typos in
GFS_Diagnostics.F90
.Alternatives
Open to ideas. Ultimately, it would be great to get this file and others into Doxygen so that documentation can be pulled directly from the code, but that would be a long-term goal.
Testing:
N/A. Issues in code metadata can be seen on examination. No run required.
Dependent PRs:
Directly reference any issues or PRs in this or other repositories that this is related to, and describe how they are related. Example:
The text was updated successfully, but these errors were encountered: