Teleconference 2022-05-18

Attendees: Ken Moreland (ORNL), Dave Pugmire (ORNL), Abhishek Yenpure (Kitware), Terry Turton (LANL), Mark Bolstad (SNL), Nicole Marsaglia (LLNL), Sujin Philip (Kitware), Ollie Lo (LANL), Hank Childs (UO), Tushar Athawale (ORNL)

ECP Updates

• ECP FY23 planning
  • https://confluence.exascaleproject.org/display/1ST/FY23+Planning+Instructions
  • Preliminary content due June 10: https://confluence.exascaleproject.org/pages/viewpage.action?pageId=145561537
  • Milestones in JIRA due June 24
  • What compute resources will we need to verify our KPP-3 scores?
    • What will be done if applications don't come through themselves?
• Software sustainability town halls
  • https://lssw.io/
• Let's think about possible highlights
  • App engagement
  • Success with porting (e.g. run on Aurora)
  • Engagement with other ST teams (e.g. using Kokkos)
  • WDM
  • Possible highlight slide on particle advection with WarpX (Matt)
  • Some work with MFIX. Going to execute on Summit. Might wait for run on early access machine before highlight.

Porting Activities

• https://wiki.jlse.anl.gov/display/inteldga/ECP+2.3.4.13+VTK-m
• https://confluence.exascaleproject.org/display/STDA05/Porting+Activities+O21

ECP task updates

ECP/VTK-m Project Management

Roundtable

LSSw whitepaper: a big part of Jim's response is a question of whether everything should be in VTK-m or if there is still stuff that should be otherwise. We should give some thought on what should or shouldn't be in VTK-m and have a reasonable argument for it.

R&D100?

• Thinking of submitting for 2022
• Big stumbling block: needs to be "created" between Jan 2021 to March 2022
• Plan: Release VTK-m 2.0, do a copyright assertion

Rename master branch?

• Need to wait for some changes to git before the transition (for some automated features of repo).
• Can we for a time have a master that mirrors the new default?
  • Don't know, but seems possible. Will have to look into that.