Agenda Notes Monday May 15th 2017 11:00 AM

MPAS-Developer Telecon:

Date: 15 May 2017
Time: 11:00 MDT / 19:00 CET

Call-in number: 1-866-740-1260
Access Code: 4978161

---

---

Agenda Topics:

1. Framework modifications:
   • Open framework PRs
2. Might -O3 optimizations be too aggressive for use as a default?
   • See Issue #1321
3. MPAS v5.1 was released last Friday
   • There were a couple of conflicts when merging 'master' back to 'develop'
   • Can everyone take a look at develop-v5.1, and if there are no problems we can push develop-v5.1 to develop
4. Some MPAS-Seaice questions:
   • Where to put configurations? See PR #1324
   • Where to add MPAS-Seaice testing system to the repo?
   • If default_inputs contains the default namelist and streams file, what are the namelist and streams file generated in the top level directory? Or does that only happen in MPAS-Seaice?
5. Standing topics:
   • MPAS-Atmosphere has renewed interest in generalized variable attributes
   • Subset I/O capability
   • Periodic meshes
   • https://github.com/MPAS-Dev/MPAS/issues/1307 "reference time" for output_interval in streams

---

---

Notes:

Participants: Matt, Adrian

Framework PRs

• 1318
  • Current approach in PR is fine
  • Another option for handling forcing group restart times might be to write these timestamps to model restart files, though this would be more work for the benefit of removing files from a run directory
• 1309 - Test this for stream within a stream functionality

Default optimization level and floating-point underflow

• Underflows disappear whenever print statements are added to code
• Some combination (TBD) of compiler options may enable FPE trapping just for underflows without the need for explicit print statements

Merge conflicts for hotfix-v5.1

• The two conflicts had reasonably obvious resolutions
• All cores compile in the merged develop-v5.1 branch
• Consensus: Go ahead and just push the merge of master to develop

Sea-Ice questions

• Perhaps if configurations directory is only used by sea-ice, place this directory in testing_and_setup/seaice/configurations
• The Sea-Ice testing system could also reside under testing_and_setup/seaice
  • The Atmosphere core may also do something similar for its testing setup under testing_and_setup/atmosphere
• Namelist and streams files in the default_inputs directory are always updated whenever a core is compiled, but:
  • Copies in the top-level directory are copied from default_inputs directory if they don't already exist
  • and not modified otherwise

Other discussion

• Should we not place any namelist or streams files in the top-level directory?
  • Cores used in ACME tend to not use the main MPAS directory for "ad hoc" model runs
  • On the other hand, atmosphere runs are typically unique and often involve code modifications, which has driven the usage of the top-level directory as a run directory for a particular code setup
  • Atmosphere core is open to exploring the use of the testing_and_setup directory for setting up run directories
• There were about 15 different branches in the main MPAS-Dev/MPAS repository
  • release-v4.0, release-v5.0, and hotfix-v5.1 can be deleted since we have tags v4.0, v5.0, and v5.1
  • Some other branches are being used for long-lived development that isn't easily "owned" by any particular person
    • Having these branches in the main repository is conceptually easier for new developers