Teleconference 2021-02-24

From VTKM
Revision as of 13:53, 24 February 2021 by Kmorel (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Attendees: Ken Moreland (SNL), Berk Geveci (Kitware), Terry Turton (LANL), Matt Larsen (LLNL), James Kress (ORNL), Silvio Rizzi (ANL), Dave Pugmire (ORNL), Ollie Lo (LANL), Hank Childs (UO), Nick Davis (SNL), Sujin Philip (Kitware), Nick Thompson (ORNL), Vicente Bolea (Kitware)

ECP Updates

  • ECP Annual Meeting
    • Registration is open
      • Will be virtual, registration is free
      • Everyone funded by ECP/VTK-m should register and plan to attend at least part of the meeting
    • Our project will need to create a poster
      • Looks like the design will be a traditional poster
      • Not totally clear how the poster session will work
      • Looks like they are planning on using a virtual meet space.
  • Computer allocation requests due March 1
  • 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

ECP task updates

ECP/VTK-m Project Management

Roundtable

Wiki might go down real soon. Might need to capture.

We need some redesign design workflow for branchy release process

  • When we create a VTK-m release, we have a branch for that release (at least until the subsequent release).
  • New feature development continues on the main branch
  • _Bug fixes_ happen off the release branch
    • Get merged to both the release branch and the master branch
  • This in principal should already be supported by GitLab
    • Just create a merge request on a different branch
    • Will need to add support to gitlab-push
      • Ask VTK folks. They might just have a select few to do a special process.
    • Need to check that bot stuff works (CI builds, Do: merge, etc.)

Should think about releasing VTK-m 1.6, 2.0.

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.