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)...") |
|||
| 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 | ||
Revision as of 09:30, 29 June 2022
Attendees:
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.
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.
