Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

All: We have 1.5 hours for this Bi-Group breakout.

The goal is to have the necessary discussions to give everyone as much clarity on their path forward and responsibilities in the months ahead.

To use this time optimally, we will gather candidate discussion topics before and at the start of the meeting, then do a prioritization, and then have time-boxed discussions on the high-priority topics.

PriorityCandidate Discussion TopicRequestorMore Details; Others can chime in here to modify scope, show support or not, etc.Notes:
1Test Suite Revamp : What do we need to do finish this off.
Andy Salinger

Balwinder Singh (thank you, thank you) is leading this critical Epic to define a test suite with mostly ultra-low-res grids to get both improved code coverage and faster test throughput. What can the team do to finish this off?

We also need a high-res, large-case test suite to test basic functionality at scale and prevent performance regression.

  • the production low-res model at production processor counts
  • the high-res model at whatever count works.

2How to best support Critical Path Team and Coupled Sim Group?
Andy Salinger
Michael Deakin (Unlicensed), Jon Wolfe: What should the rest of the SE/CPL + Perf groups know to better support ACME scientists?

3Is there a better way to solicit/determine requirements for CIME and associated infrastructure?Philip Jones, Patrick Worley (Unlicensed) (in absentia)In the recent past, some capabilities have been (inadvertently?) dropped. Related to testing too.
4How can we provide a mechanism for work to move forward without requiring a CIME mod to propagate into the repo?Philip Jones, Patrick Worley (Unlicensed) (in absentia)As CIME has become more opaque, it is more difficult to make quick/simple workarounds to keep simulations going while the final fix propagates through the system. Makes James Foucar a single point of failure.
5Upcoming Issues to be ready for:Andy Salinger

Things we need to be ready for:

  1. Multi-Repo Discussion Wednesday
  2. Infrastructure Review – Summer
  3. v1 Support – next year

6Open discussion on ACME and SE/CPL Group ManagementAndy Salinger

Any suggestions on improved management?







  • No labels