-
Notifications
You must be signed in to change notification settings - Fork 64
CCPP Framework Meeting Minutes 2020 11 24
Dom Heinzeller edited this page Nov 24, 2020
·
13 revisions
-
capgen.py
progress - Transition to
capgen.py
- NOAA / NCAR-ACOM model development
- Other business
- Build updates for unification: https://github.com/NCAR/ccpp-framework/pull/339
- This fixed #278 and #293
- Now working on #259 and #306, another PR will be #314, #328, #329 and #337
- We don't have a plan yet how to handle optional arguments
- Also looking at "advective species feature" requested by NRL (#282)
- We should touch base with them in one of the following ccpp-framework meetings; want Cheryl, Dave, Francis, Steve, Grant, Dom as well
- DTC needs to develop a mechanism to avoid using the
field_table
- use an internal field table approach, similar to the internal input file?
- Updated DTC timeline and resource chart (https://docs.google.com/spreadsheets/d/1XbSF1ejYcPMrVtZtk1OSiMX-vI5srLkwEUhyAirGr8k/edit?usp=sharing)
- Things that need to happen for transitioning UFS to
capgen.py
(https://docs.google.com/document/d/1M3mCO3ESR9OJqLyUbQf-ahJtmfmGKilZlWaBTxsfMRk/edit?usp=sharing) - Follow up on discussion of last week on removal of optional arguments (or not)
- From two weeks ago: Do we need consent from developers to not support optional arguments? Do we tell developers to not use them right away? Do they need alternatives? Whom to contact? EMC, GSL, Robert & Dustin
- Dom will do - after Thanksgiving
-
timestep_init
,timestep_finalize
- Dom is working on this - assumed sizes: Dom needs to take up this PR, update it with the latest code and fix the issues
- cleanup of grandfathered stuff (Xia): See https://docs.google.com/spreadsheets/d/1rUMEG0yhZaJvbsl3OawlBzYwLYzo1XBPQfsBZZto63I/edit?usp=sharing
- Consolidation of standard names (Ligia and Grant) - https://docs.google.com/spreadsheets/d/1kWDC7_2sagm-PTP_tXaGyI3O3sJFK8FY9FElQbb6V3o/edit#gid=613941307
- No progress since last week
- Ligia and Dom met with Georg and Jordan (Schnell); Georg and Jordan are under the impression that ACOM will still use CCPP?
- Steve met with SIMA co-leads to seek clarification. Need to distinguish between two different things: (1) Connecting a chemistry suite with a host model will still be done using CCPP (2) How to connect chemistry internally - could use CCPP (we believe that it would be possible to do this) or something else (this seems like what they want to do)
- If chemistry connections are done outside of CCPP, this will be a major drawback for collaboration - other efforts at GSL aim at breaking the chemistry up into CCPP components
- Complication: chemistry may use complex derived data types, this will require good documentation in metadata for CCPP to work
- CCPP-ized runtime data structures for chemistry arrays - this needs to be worked on
- Should we ask the MUSICA working group to give an update in this meeting?
- possibly after MUSICA meeting in early December
- Progress on CCPP physics governance?