Skip to content
This repository has been archived by the owner on Oct 23, 2020. It is now read-only.

Agenda Notes Monday February 6th 2017 11:00 AM

Jump to bottom
Michael Duda edited this page Feb 6, 2017 · 4 revisions

MPAS-Developer Telecon:

Date: 6 February 2017
Time: 11:00 MST / 19:00 CET

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

Agenda Topics:

  1. Report from extreme scaling experiment with MPAS-Atmosphere
  2. Framework modifications:
  3. Design Document Discussions
  4. News and updates:
    • A new label, High-priority has been created for use with PRs that require attention in the next few days

Notes:

Participants: Dom, Xylar, Mark, Jon, Matt

Extreme-scaling report: Postpone discussion until a later week

Framework PRs:

  • #1215: Mark will test in the normal way in the ocean, but how do we want to test this in ACME?
    • Matt: this may solve the 1850 issue, but may need the corresponding fix in ACME
    • This commit only brings us up to date with ESMF in CIME; a later PR will address the 1850 issue (and will be labeled "Don't Merge" until the time manager code in ACME has been updated with current CIME)
  • #1211: Michael will merge this - similar fixes were needed when testing with PIO2 before the v5.0 release
  • #1207: no objections - we'll merge this PR this week
  • Dom will create another PR to 'hotfix-v5.1' to fix angle brackets in #include lines; Michael will ensure changes are mirrored in CIME
  • #453: Enough value to see this through to completion; Dom interested to take this up; can we come up with an example of nested structs in the Registry?
  • #522 homework item: each core maintainer should take a look at design document and return next week with thoughts Matt will check with Doug on filter infrastructure

Arbitrary attributes: keep on to-do list, because it may be something helpful in future

Logging module: provide input by the end of this week, Matt has started working on a design Highlights on areas where input is needed:

  • naming of output/warning/error/critical
  • how to handle transition from redirect to new logging module - perhaps overlap period of month or two
    • what about sw core? Michael volunteers to convert this
  • looked at basic design
  • provide feedback to questions in red
Clone this wiki locally