Difference between revisions of "Teleconference 2022-07-27"
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | Attendees: | + | Attendees: Ken Moreland (ORNL), Ollie Lo (LANL), Mark Bolstad (SNL), Dave Pugmire (ORNL), Tushar Athawale (ORNL), Nicole Marsaglia (LLNL), Silvio Rizzi (ANL), Sujin Philip (Kitware), Terry Turton (LANL), Hank Childs (UO), Vicente Bolea (Kitware) |
== ECP Updates == | == ECP Updates == | ||
| Line 7: | Line 7: | ||
** https://docs.google.com/document/d/1fUgsTV4HYfbnXdc8xTgBqWPPhUS8spWDLuzBNKTNR7k/edit?usp=sharing | ** https://docs.google.com/document/d/1fUgsTV4HYfbnXdc8xTgBqWPPhUS8spWDLuzBNKTNR7k/edit?usp=sharing | ||
* Tulip to be decommissioned August 31 | * Tulip to be decommissioned August 31 | ||
| + | * Polaris early access available | ||
| + | ** https://argonne-lcf.github.io/polaris-userdocs/polaris/getting-started/ | ||
* Let's think about possible highlights | * Let's think about possible highlights | ||
** App engagement | ** App engagement | ||
| Line 25: | Line 27: | ||
== Roundtable == | == Roundtable == | ||
| + | |||
| + | Remove VTKM_CONT? A short discussion had some slight opinions both ways. On one hand, the use of VTKM_CONT is becoming a bit inconsistent with it not being used in some place that it should. On the other hand, VTKM_CONT is a useful comment to those learning the VTK-m source code to tag where something is going to run. There is also a minor concern with running into a device in the future that actually needs VTKM_CONT. Considering this, it was decided to leave the modifiers as they are. | ||
R&D100? | R&D100? | ||
Latest revision as of 11:53, 27 July 2022
Attendees: Ken Moreland (ORNL), Ollie Lo (LANL), Mark Bolstad (SNL), Dave Pugmire (ORNL), Tushar Athawale (ORNL), Nicole Marsaglia (LLNL), Silvio Rizzi (ANL), Sujin Philip (Kitware), Terry Turton (LANL), Hank Childs (UO), Vicente Bolea (Kitware)
ECP Updates
- P6 Activity reporting
- PI's should update their contributions in google doc
- https://docs.google.com/document/d/1fUgsTV4HYfbnXdc8xTgBqWPPhUS8spWDLuzBNKTNR7k/edit?usp=sharing
- Tulip to be decommissioned August 31
- Polaris early access available
- 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
Roundtable
Remove VTKM_CONT? A short discussion had some slight opinions both ways. On one hand, the use of VTKM_CONT is becoming a bit inconsistent with it not being used in some place that it should. On the other hand, VTKM_CONT is a useful comment to those learning the VTK-m source code to tag where something is going to run. There is also a minor concern with running into a device in the future that actually needs VTKM_CONT. Considering this, it was decided to leave the modifiers as they are.
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.
