Difference between revisions of "Teleconference 2021-05-12"
(Created page with "Attendees: Ken Moreland (ORNL) == ECP Updates == * Let's think about possible highlights ** App engagement ** Success with porting (e.g. run on Aurora) ** Engagement with ot...") |
|||
| Line 1: | Line 1: | ||
| − | Attendees: Ken Moreland (ORNL) | + | Attendees: Ken Moreland (ORNL), Ollie Lo (LANL), Terry Turton (LANL), Silvio Rizzi (ANL), Dave Pugmire (ORNL), Hank Childs (UO), Matt Larsen (LLNL), Sujin Philip (Kitware) |
== ECP Updates == | == ECP Updates == | ||
| + | * Submitted new PCRs for work at SNL and LANL | ||
* Let's think about possible highlights | * Let's think about possible highlights | ||
** App engagement | ** App engagement | ||
| Line 10: | Line 11: | ||
*** Submitted highlight on integration with EFFIS | *** Submitted highlight on integration with EFFIS | ||
*** Expect to submit another highlight when used in a big run | *** Expect to submit another highlight when used in a big run | ||
| − | ** Possible highlight slide on particle advection with WarpX (Matt) | + | ** Possible highlight slide on particle advection with WarpX (Matt) |
== Porting Activities == | == Porting Activities == | ||
| Line 22: | Line 23: | ||
== Roundtable == | == Roundtable == | ||
| + | |||
| + | Update P6 Activites. No links. Generic statements across integrations (e.g. work with ECP partners to identify specific needs of the group, address specific needs, etc.) Perhaps "maintain and harden VTK-m software for key stakeholders such as Ascent and apps such as..." | ||
| + | |||
| + | Clean up P6 Activities so that it doesn't just list detailed stuff. | ||
Version 1.6.0-rc1 is released. What do we need to do before the official release? Update Ascent? Update VTK? Others? | Version 1.6.0-rc1 is released. What do we need to do before the official release? Update Ascent? Update VTK? Others? | ||
Latest revision as of 12:02, 12 May 2021
Attendees: Ken Moreland (ORNL), Ollie Lo (LANL), Terry Turton (LANL), Silvio Rizzi (ANL), Dave Pugmire (ORNL), Hank Childs (UO), Matt Larsen (LLNL), Sujin Philip (Kitware)
ECP Updates
- Submitted new PCRs for work at SNL and LANL
- 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
Roundtable
Update P6 Activites. No links. Generic statements across integrations (e.g. work with ECP partners to identify specific needs of the group, address specific needs, etc.) Perhaps "maintain and harden VTK-m software for key stakeholders such as Ascent and apps such as..."
Clean up P6 Activities so that it doesn't just list detailed stuff.
Version 1.6.0-rc1 is released. What do we need to do before the official release? Update Ascent? Update VTK? Others?
A new machine will be deploying a new machine: Polaris. Intended to help science teams be ready for exascale machines.
Wiki will go away at some point (and will definitely move soon). We should avoid using it for anything other than these notes.
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.
