Teleconference 2022-03-16

Attendees:

ECP Updates

• ECP Annual Meeting
  • Poster discussion (due April 18)
• ECP management is wanting bi-weekly updates on early access progress
  • Will be biweekly updates on confluence
  • No NDA (limited communication for Arcticus)
  • Plan to summarize progress discussed in this meeting
  • https://confluence.exascaleproject.org/display/1ST/2.3.4+Data+and+Visualization+Exascale+Porting+Status
  • The Frontier Center of Excellence confluence is being shut down and moved to the ECP confluence
    • We will move our collection there when that is complete
• 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://frontier-coe.atlassian.net/wiki/spaces/FCOE/pages/1161625609/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.