Difference between revisions of "Teleconference 2022-06-29"
Jump to navigation
Jump to search
(Created page with "Attendees: == ECP Updates == * ECP FY23 planning ** Further updates? * Let's think about possible highlights ** App engagement ** Success with porting (e.g. run on Aurora)...") |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | Attendees: | + | Attendees: Ken Moreland (ORNL), Ollie Lo (LANL), Elyce Bayat (LANL), Mark Bolstad (SNL), Nicole Marsaglia (LLNL), Dave Pugmire (ORNL), Abhishek Yenpure (Kitware), Sujin Philip (Kitware), Hank Childs (UO), Vicente Bolea (Kitware), Tushar Athawale (ORNL) |
== ECP Updates == | == ECP Updates == | ||
| Line 5: | Line 5: | ||
* ECP FY23 planning | * ECP FY23 planning | ||
** Further updates? | ** Further updates? | ||
| + | * In-person Frontier hackathon September 12-14 | ||
| + | ** Any interest? | ||
| + | ** Deadline July 1 | ||
* Let's think about possible highlights | * Let's think about possible highlights | ||
** App engagement | ** App engagement | ||
| Line 24: | Line 27: | ||
== Roundtable == | == Roundtable == | ||
| − | Discussion on mailing list about moving to C++17. | + | Discussion on mailing list about moving to C++17. We do not plan to move to C++17. However, there is some worry that if VTK-m libraries are compiled with C++17 (for Kokkos), will that cause issues with using them in applications compiled with C++14? A [https://stackoverflow.com/questions/46746878/is-it-safe-to-link-c17-c14-and-c11-objects StackOverflow entry] suggests this should be fine. |
R&D100? | R&D100? | ||
Latest revision as of 12:00, 29 June 2022
Attendees: Ken Moreland (ORNL), Ollie Lo (LANL), Elyce Bayat (LANL), Mark Bolstad (SNL), Nicole Marsaglia (LLNL), Dave Pugmire (ORNL), Abhishek Yenpure (Kitware), Sujin Philip (Kitware), Hank Childs (UO), Vicente Bolea (Kitware), Tushar Athawale (ORNL)
ECP Updates
- ECP FY23 planning
- Further updates?
- In-person Frontier hackathon September 12-14
- Any interest?
- Deadline July 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
- 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
Discussion on mailing list about moving to C++17. We do not plan to move to C++17. However, there is some worry that if VTK-m libraries are compiled with C++17 (for Kokkos), will that cause issues with using them in applications compiled with C++14? A StackOverflow entry suggests this should be fine.
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.
