Teleconference 2022-02-02

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

ECP Updates

• ECP Annual Meeting
  • 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 weekly updates on early access progress
  • Not sure how that communication is going to happen
• 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

VTK-m 1.7.1 released.

Mark noticed some compile failures with GCC 11.1. It looks like the error is happening with brigand.

Mark needs to be added to the VTK-m GitLab.

When updating the tests, Ken noticed some discrepancies in the rendering for some types of components. Who is now responsible for rendering and can take a look at this:

• MapperQuad colors are wrong
• MapperConnectivity is buggy
• MapperCylinder just does not work

They are probably not used. Maybe they should be deprecated.

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.