Difference between revisions of "Teleconference 2022-01-12"
Jump to navigation
Jump to search
(Created page with "Attendees: Ken Moreland (ORNL), Ollie Lo (LANL), Roxana Bujack (LANL), Terry Turton (LANL), Tushar Athawale (ORNL), Abhishek Yenpure (UO), Dave Pugmire (ORNL), Nick Davis (SNL...") |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | Attendees: Ken Moreland (ORNL), Ollie Lo (LANL), | + | Attendees: Ken Moreland (ORNL), Ollie Lo (LANL), Abishek Yenpure (UO), Bark Bolstad (SNL), David Pugmire (ORNL), Terry Turton (LANL), Tushar Athawale (ORNL), Nick Davis (SNL), Manish Mathi (UO), Hank Childs (UO), Berk Geveci (Kitware), James Kress (ORNL), Sujin Philip (Kitware), Vicente Bolea (Kitware) |
== ECP Updates == | == ECP Updates == | ||
| + | * Will break early for ECP project review feedback | ||
* ECP Annual Meeting | * ECP Annual Meeting | ||
** Call for BoF, Breakout, Panel, Tutorials: Due Feb 16 | ** Call for BoF, Breakout, Panel, Tutorials: Due Feb 16 | ||
** Usually participate with Alpine | ** Usually participate with Alpine | ||
* Crusher test and development system for Frontier | * Crusher test and development system for Frontier | ||
| − | ** | + | ** Our CSC331 project now has access |
| − | ** | + | *** Apparently Kitware does not have access (even though I was told they would have it) |
| + | ** If you are waiting on my approval for something, send me an email | ||
| + | *** System is still not alerting me when I have approvals waiting | ||
* Software sustainability town halls | * Software sustainability town halls | ||
** https://lssw.io/ | ** https://lssw.io/ | ||
| Line 31: | Line 34: | ||
== Roundtable == | == Roundtable == | ||
| + | |||
| + | Break at 10:30 for ECP project review feedback. | ||
| + | |||
| + | VTK-m release 1.7.1 immenent. | ||
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. | 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. | ||
Latest revision as of 12:29, 12 January 2022
Attendees: Ken Moreland (ORNL), Ollie Lo (LANL), Abishek Yenpure (UO), Bark Bolstad (SNL), David Pugmire (ORNL), Terry Turton (LANL), Tushar Athawale (ORNL), Nick Davis (SNL), Manish Mathi (UO), Hank Childs (UO), Berk Geveci (Kitware), James Kress (ORNL), Sujin Philip (Kitware), Vicente Bolea (Kitware)
ECP Updates
- Will break early for ECP project review feedback
- ECP Annual Meeting
- Call for BoF, Breakout, Panel, Tutorials: Due Feb 16
- Usually participate with Alpine
- Crusher test and development system for Frontier
- Our CSC331 project now has access
- Apparently Kitware does not have access (even though I was told they would have it)
- If you are waiting on my approval for something, send me an email
- System is still not alerting me when I have approvals waiting
- Our CSC331 project now has access
- Software sustainability town halls
- 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)
- Improvement with Kokkos on Spock
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
Roundtable
Break at 10:30 for ECP project review feedback.
VTK-m release 1.7.1 immenent.
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.
Gunther brings up an issue where he tried contour trees with large data sets that ran slowly on CUDA but crashed with HIP/Kokkos. This might be an issue of lack of proper unified memory on the HIP/Kokkos end. We are not sure.
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.
