Teleconference 2022-02-09

Attendees: Ken Moreland (ORNL), Terry Turton (LANL), Mark Bolstad (SNL), Ollie Lo (LANL), Hank Childs (UO), Berk Geveci (Kitware), Silvio Rizzi (ANL), Sujin Philip (Kitware), James Kress (ORNL), Roxana Bujack (LANL), Tushar Athawale (ORNL), Vicente Bolea (Kitware)

ECP Updates

• Funding for FY23/Q4 is officially coming
• ECP Annual Meeting
  • Officially now virtual, week of May 2
  • Call for BoF, Breakout, Panel, Tutorials: Due Feb 16
  • Usually participate with Alpine
• Crusher test and development system for Frontier
  • Kitware now has access
• 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
• 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

What do we do with the tutorial slides. Sounds like consensus is to go ahead and put it in the repo as an LFS file.

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.