Teleconference 2022-07-06

Attendees: Kenneth Moreland (ORNL), Roxana Bujack (LANL), Ollie Lo (LANL), Mark Bolstad (SNL), Sujin Philip (Kitware), Abhishek Yenpure (Kitware), Nicole Marsaglia (LLNL), Terry Turton (LANL), Silvio Rizzi (ANL), Hank Childs (UO)

ECP Updates

• P6 Activity reporting
  • PI's should update their contributions in google doc
  • https://docs.google.com/document/d/1fUgsTV4HYfbnXdc8xTgBqWPPhUS8spWDLuzBNKTNR7k/edit?usp=sharing
• 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

Discussion on mailing list about moving to C++17. We do not plan to move to C++17. However, there is some worry that if VTK-m libraries are compiled with C++17 (for Kokkos), will that cause issues with using them in applications compiled with C++14? A StackOverflow entry suggests this should be fine.

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.