Teleconference 2021-09-01

Attendees:

ECP Updates

• Any computer allocation needed for next quarter (deadline today)
• Review Product Readiness
  • https://confluence.exascaleproject.org/display/1ST/ECP+ST+Product+Readiness
• 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
    • Submitted highlight on integration with EFFIS
    • Expect to submit another highlight when used in a big run
  • Possible highlight slide on particle advection with WarpX (Matt)

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

No meeting next week.

Update on Kokkos "separable compile"? Seems to be working and making the Kokkos compile time managamble.

Ken would like to look at removing the template from CellSetExplicit. This would mean that the array types would be fixed for unstructured cell sets. Currently, apart from the default basic array types, the only specializations are for CellSetSingleType and for adapting to VTK meshes using 32-bit indices. What would happen if these went away (and we just copied arrays as necessary)? -- This is a problem. Single type cell sets are very common.

Has anyone been looking at compiling both VTK-m and Ascent over Kokkos? We have had to do some special things under CUDA, and we might expect there to be some integration issues under Kokkos and its various backends as well.

Filter redesign requirements: https://gitlab.kitware.com/vtk/vtk-m/-/issues/601

Matt working on WarpX highlight.

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.