Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Room 1: Infrastructure meets with (in order):

    • 8:40 - 9:00 Water Cycle + HES:

    • 9:10 - 9:30 EAMxx + Omega:

      • What helpful tools/tests/etc has each group created or planned that would be helpful to others?

      • Can you come up with project-wide C++ coding standards?

    • 9:40 - 10:00 Land + v3 Atm:

      • How do we move to an MPAS-land grid?

      • When is a PR for high-res land going to happen?

    • 10:10 - 10:30 Polar + Ice:

      • What are the near-term coupling needs?

  • Room 2: Performance meets with

    • 8:40 - 9:00 EAMxx + Omega

      • What can we do to eek out more performance from our models?

    • 9:10 - 9:30 Land + v3 Atm

    • 9:40 - 10:00 Polar + Ice

    • 10:10 - 10:30 Water Cycle + HES

  • Room 3: Coupled

    • 8:40 - 9:00 Land + v3 Atm

    • 9:10 - 9:30 Polar + Ice

    • 9:40 - 10:00 Water Cycle + HES

    • 10:10 - 10:30 EAMxx + Omega

      • What is the roadmap for coupled runs with EAMxx and Omega? Can we come up with tasks/expectations for each group in this work?

  • Room 4: AI/ML - Peter Caldwell thinks this group (consisting solely of Andy Salinger ) should just take notes on all the AI applications being done within E3SM and discuss how they fit into E3SM’s AI strategic plan.

    • 8:40 - 9:00 Polar + Ice

    • 9:10 - 9:30 Water Cycle + HES

    • 9:40 - 10:00 EAMxx + Omega

    • 10:10 - 10:30 Land + v3 Atm

...

  • Room 1: Infrastructure + Coupled + Performance + AI/ML

    • What do we want in a model experiment tracker?

    • Any progress on identifying AI/ML runtime best practice?

  • Room 2: Water Cycle+HES+Polar+Ice

  • Room 3: EAMxx+Omega+Land+v3 Atm

    • How do we integrate high-res land with EAMxx and Omega?

    • What are Land’s and River’s plans in terms of their own C++ port?

    • How do v3 Atm members get integrated into C++ tasks?