Teleconference 2022-12-07

Attendees: Ken Moreland (ORNL), Eric Bruger (LLNL), Silvio Rizzi (ANL), Roxana Bujack (LANL), Hank Childs (UO), Sujin Philip (Kitware), Mark Bolstad (SNL), Abhishek Yenpure (Kitware), Dave Pugmire (ORNL), Nicole Marsaglia (LLNL), Jeff Amstutz (Nvidia), Jay Wang (ORNL), Tushar Athawale (ORNL), Manish Mathai (UO)

ECP Updates

• Need to work on early KPP-3
• ECP All Hands Meeting
  • Registration information available at https://www.ecpannualmeeting.com/
    • Deadline is December 16 for US citizens
    • Registration is not free. Prepare for permissions before deadline.
  • Poster
    • A poster for every project (including VTK-m) expected
    • Theme: then and now. Highlight new capabilities of the VTK-m since beginning of ECP
• Get key people on AD allocations
  • The following AD codes will be running early on Frontier
    • LatticeQCD, ExaSMR, ExaSky (HACC), CANDLE, EQSIM, Subsurface, WDMApp, WarpX
    • For WarpX: they have already run their KPP-1. Further KPP-3 will likely be in ALPINE's project (CSC340).
  • If we are providing software assistance for any of these, or we are planning a KPP-3, we should have a member as part of their allocation.
• 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
  • 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

Last meeting of the year.

Decided on doing 4 "early" KPP-3 metrics

• Flow for WarpX and/or WDMApp
  • Springboard off Abhishek's thesis work
• Ascent integration
• ParaView integration
• VisIt integration

R&D100?

• Thinking of submitting for 2023
• Big stumbling block: needs to be "created" between Jan 2022 to March 2023
• 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.