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.
| Priority | Candidate Discussion Topic | Requestor | More Details; Others can chime in here to modify scope, show support or not, etc. | Notes: |
|---|---|---|---|---|
| 8 | Test Suite Revamp : What do we need to do finish this off? | 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.
| Can SCM replace some global configs for tests? | |
| 1 | How to best support Critical Path Team and Coupled Sim Group? | Michael Deakin (Unlicensed), Jon Wolfe: What should the rest of the SE/CPL + Perf groups know to better support ACME scientists? | run_acme script is being tested. But maybe not full combinatorial options. Need more runs with options. Formation of Critical Path team has helped communication problems. build_namelist is the expensive part, run a lot of places due to legacy reasons A lot of the infrastructure has to have an understanding of how the tools are used | |
| 2 | Is 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. | Need more tests. That prevents things from being dropped. Its always inadvertent. Going back: can always check out old version of master. Hard to mix new master with old features. Whole body of people doing model runs; tap into them to find out what model runs entail, then we can catch a lot more |
| 4 | How 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. | |
| 5 | Upcoming Issues to be ready for: | Andy Salinger | Things we need to be ready for:
| |
| 6 | Open discussion on ACME and SE/CPL Group Management and Cross-Group relations. | Andy Salinger | Any suggestions on improved management? Inter-group management | |
| 7 | Coupler Documentation | Noel Keen | How to modify for performance? | |
| 3 | Performance plans in advance of release. | Peter Caldwell | ||
| 9 | Test Process | Wade Burgess |