-
Notifications
You must be signed in to change notification settings - Fork 17
Standard Names Meeting Minutes 2024 11 14
- Standard Names governance
- Standard Names rules
- GitHub issues/PRs
- New items
- Other issues needing discussion
- notes
Attendees: Jordan Powers, Michael Kavulich, Jesse Nusbaumer, Dom Heinzeller, RhaeSung Kim, Soren Rasmussen, Dustin Swales, Courtney Peverley, Michael Waxmonsky
We should stand up a group containing at least one member from each group using (or considering using) Standard Names
- NCAR/CGD
- NOAA/DTC
- JCSDA
- NRL
- ???
These members can meet bi-weekly as needed to discuss updates to the standard names, rules, and other Standard Names topics.
Do we need official guidelines on governance aside from the understanding that everyone gets a seat at the table if they wish? At the very least we need rules on PR reviews and merging
-
Latest rules updates:
- Created a branch
release/v1
for this work to occur on - PR with last meeting's changes plus more open: https://github.com/ESCOMP/CCPPStandardNames/pull/85
- Next round of changes for discussion started in a new google doc
- Created a branch
-
We should rename the repository to remove CCPP from the name
- Seems like something more descriptive than "Standard Names" should be used
- "Earth System Standard Names"?
- What is "air"?
- I promise this is an important question
- Does it include CO2? Does it include trace gases? Does it include all trace gases, or just well-mixed gases?
- Is it an assumed composition? Can we use the same "air" variables in the troposphere as the ionosphere?
- Questions about mixing ratios
- Here there seems to be a conflict between meteorology and atmospheric chemistry
- In meteorology, it is assumed "with respect to dry air" (typically water vapor)
- In atmospheric chemistry, it is assumed "with respect to all other constituents"
- Our current rules don't even explicitly say that a mixing ratio is wrt to air, or dry air, or anything by default.
- "Longwave" and "shortwave"
- Currently not defined, and could lead to disagreements based on different definitions
- Longwave
- Synonym for infrared?
- Specifically the thermal emission spectrum?
- Some other wavelength range? >400nm?
- Shortwave
- Synonym for UV?
- UV + Visible?
- Specifically the solar emission spectrum?
- Some other wavelength range? <400nm?
- Longwave
- Define or disallow? Or allow only in reference to a particular type of radiation scheme?
- I lean towards the last option.
- Continuing down the rabbit hole, what about existing "allowed" terms...none of these are strictly defined
- infrared
- near-infrared
- visible
- ultraviolet
- Decide what units to support
- https://github.com/ESCOMP/CCPPStandardNames/issues/63
- This is different from any restrictions that CCPP framework wants to make on the acceptable units
- Should we try to list supported units, or just say "SI units and geometric combinations thereof are permitted" at the top of the units table?
- Decide what variables should and should not be standard names
- "flag" and "index" variables (some boolean, some integer)?
- Currently (with "index" variables) represent approximately half (!!) of all standard names, and many have questionable value for inter-component functionality
- If flags are included, how to name them? We currently have "flag_for_", "control_for_", "identifier_for_", "do_", and some have no qualifier at all!
- scheme-specific tuning coefficients/weights
- scheme-specific bins (e.g. GOCART aerosols)
- Should Standard Names include constants, or should this be a separate standard?
- Should we include definitions, or just the names? Should the names be base names? (probably)
Standard names (issues, PRs, discussions)
-
Continue iterating on rules document, open PRs to v1 branch as needed
-
Develop an automated script that generates the entire possible list based on specified rules and base names
-
Make "announcement" discussion about rename and overhaul
Standard Names
- Michael K opened PR #85 with updates (rule changes, clarification) from last time
- People should look at it/iterate
- Michael K created a branch (release/v1) for further work to occur on
- Change repo name to remove “CCPP”
- Michael K proposed Earth System Standard Names
- Dom & Jesse - ESM (Earth System Modeling) Standard Names
- Jordan proposes listing out the candidates somewhere
- Michael K to put them here (new rules document) - https://docs.google.com/document/d/19ysUCWDhv53W8fQbElW7opr_1Pm7ck95QRUyKM_qy4E/edit?tab=t.0#heading=h.vf7w5h6fu1hm
- Jesse - should still document what the names are used for (e.g. new standard names can’t break these) - JEDI, CCPP
- Michael K to include in introductory paragraph
- Dom - should announce it widely & document clearly
- Michael K working on list of base standard names
- https://docs.google.com/document/d/1h5PeHk_efVrZvqfBO2ZexY-UREwwdlbfcvrvz_s3f2A/edit?tab=t.0
- PLEASE TAKE A LOOK & OFFER COMMENTS, especially base names section
- Only included names that appeared more than once (will also probably contain one-off names in the future)
- Few cases where we need to pick a version
- Or do we allow synonyms?
- Courtney: synonyms seem non-ideal to code up
- Jesse: also, synonyms also end up being not actually synonymous scientifically
- Decision: no synonyms!
- Or do we allow synonyms?
- Dom - is it “air_” or “of_air”
- Michael - would kind of include both. Base names that include “air_” are OK, but other ones would be “of_air”
- What about “surface_” vs “of_surface”?
- Dom & Jesse - recall it should be “at_surface”
- Dimensions - will likely end up being a separate section because capgen is picky about dimension variables!
- Jesse - we should explain where/when to use horizontal_loop_extent vs horizontal_dimension
- Michael K - should these variables have “ccpp_”?
- Jesse - probably, but would be a bit of a lift
- How do we document these in a “general” way? Should these reserved variables have a prefix option? ccpp_ ? esmf_ ?
- Will discuss at a future meeting
- Constants - include as base names?
- Re-organize! GFS-specific sections not useful for other components
- Dom & Dustin have been discussing organization of typedefs for MPAS
- Don’t need to have all the data containers now that they’re using contiguous data in UFS
- Can remove data container references from GFS variables
- Dom & Dustin have been discussing organization of typedefs for MPAS
- What is air?
- Michael K - Can we just use “air” or does there always need to be a qualifier?
- Jesse - just specifying dry air or not is sufficient
- Up to model to adjust quantities relative to that
- Would get complicated for exoplanets
- Jesse: “The mixture of gases that make up the fluid medium of the atmosphere”
- Dustin: “air = well mixed major contributors”
- Major constituents + CO2 + methane
- Up to host model to determine what “air” is composed of
- Jesse - from dycore’s perspective, what matters are those that can meaningfully impact the gas constant
- Mixing ratios - current rules are ambiguous?
- Meteorology: wrt dry air
- Atmospheric chemistry: wrt all other constituents
- Jesse - leans towards no default; have to specify
- Do we need another suffix option - “wrt_all_other_constituents”?
- Michael K to add example in the documentation
- Longwave and shortwave - definition?
- Dustin: longwave covers spectrum emissions of the earth (infrared/near-ir); shortwave covers spectrum from sun (visible, uv)
- The specific bands are dependent on the composition of the atmosphere (could differ on other planets)
** gchat **
You 9:29 AM https://github.com/ESCOMP/CCPPStandardNames/wiki/Standard-Names-Meeting-Minutes-2024-11-14 keep Pinned Dom Heinzeller 9:36 AM ESM Standard Names (Earth System Modeling) Jesse Nusbaumer 9:36 AM I think "EarthSystemStandardNames" is fine, or "EarthSystemModelStanrdNames" ESM Standard Names works for me to. Dom Heinzeller 9:40 AM https://github.com/JCSDA/spack-stack/blob/develop/project_charter.md Dom Heinzeller 9:42 AM brb You 9:42 AM https://docs.google.com/document/d/1h5PeHk_efVrZvqfBO2ZexY-UREwwdlbfcvrvz_s3f2A/edit?tab=t.0 Jesse Nusbaumer 9:45 AM This is a great start, thanks Michael! Dustin Swales - NOAA Federal 9:51 AM I agree with Courtney here, but see the value of having them Dustin Swales - NOAA Federal 9:55 AM https://github.com/NCAR/ccpp-framework/blob/main/scripts/metavar.py#L34 ^These are no touchy by the dictionary. Correct? Dom Heinzeller 10:00 AM I like it, just a lot of changes and even longer names Dom Heinzeller 10:04 AM Dustin, do you want to talk about what we discussed the other day? Jesse Nusbaumer 10:09 AM The mixture of gases that make up the fluid medium of the atmosphere? Dustin Swales - NOAA Federal 10:11 AM air = well mixed major contributors What is temperature in the ionosphere? Jesse Nusbaumer 10:12 AM high ba-dum-ts but also true because the thermosphere You 10:16 AM No love for Argon Jesse Nusbaumer 10:18 AM From a dycore point-of-view the things that matter are those that can meaningfully impact the gas constant (basically) Dustin Swales - NOAA Federal 10:20 AM shared misery Dom Heinzeller 10:20 AM By default, mixing_ratio refers to mass mixing ratios. The long name should explicitly specify that it refers to the mass mixing ratio. Mass mixing ratios should contain information regarding with respect to what quantity they are defined, and options are wrt_dry_air, wrt_moist_air, or wrt_moist_air_and_condensed_water, where moist_air refers to dry air plus vapor and moist_air_and_condensed_water refers to dry air plus vapor and hydrometeors. Use of specific_humidity should be avoided as there is no consensus on whether it refers to mixing_ratio_of_water_vapor_wrt_moist_air or mixing_ratio_of_water_vapor_wrt_moist_air_and_condensed_water. total_water can be used to designate water in every form, i.e. water vapor plus condensed water. Jesse Nusbaumer 10:33 AM could we give official wavenumber bandwidths for the more specific sectiosn below? E.g. Visible versus UV? sectiosn = section*