Teleconference 2022-08-03

Attendees:

ECP Updates

• Finalize next P6 Activity
• 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
  • 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

Remove VTKM_CONT? A short discussion had some slight opinions both ways. On one hand, the use of VTKM_CONT is becoming a bit inconsistent with it not being used in some place that it should. On the other hand, VTKM_CONT is a useful comment to those learning the VTK-m source code to tag where something is going to run. There is also a minor concern with running into a device in the future that actually needs VTKM_CONT. Considering this, it was decided to leave the modifiers as they are.

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.