This repository has been archived by the owner on Oct 23, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Agenda Notes Monday December 16th 2013 3:00 PM
Douglas Jacobsen edited this page Nov 17, 2014
·
1 revision
Date: 16 December 2013
Time: 3:00pm MST
Call-in number: 1-866-740-1260
Access Code: 4978161
- Core summaries: Status, Needs and Outlooks
- MPAS infrastructure workplan through 1 January 2014
- Transition to universal mesh type
- Unique namelists for each core, generated at build time
- Transition 'iro' streams in Registry files to new stream definitions
- Any other items
- No updates from the ATM core
- OCN is trying to prepare for OMWG in January
- No updates from LI core
- Multiple Cores / Run-time IO Work plan
- Universal mesh type
- Define mesh type that is required by framework
- Cores can augment mesh type
- Can define a stream attribute that will include fields defined in the mesh type
- Add "computable" tag to mesh specification fields
- Distinct namelists
- Build time generates a default namelist
- Namelists are now named namelist.core_name
- New default stream definitions
- Default streams should be defined through the new "run-time" definition syntax but only be definable at build time.
- Universal mesh type
- Revisit procedure for adding a core to the repository to ensure we're not overloading developers
- Adding a new core shouldn't change framework, if it does it's rejected.
- A new core PR should not require a significant review. Only:
- Developer guidelines
- Framework changes
- "Build-ability"
- Conversion of namelist to XML
- Requirements by external models might determine if we can or cannot do this.
- Could allow more robust error checking
Next Broad MPAS Developer Telecon: Tuesday January 21st 2013