Difference between revisions of "Teleconference 2022-10-26"
Jump to navigation
Jump to search
(Created page with "Attendees: == ECP Updates == * ECP All Hands Meeting submissions ** Due by October 28 (this Friday) ** An DAV overview BOF will not be done this year * P6 Activity reportin...") |
|||
Line 31: | Line 31: | ||
== Roundtable == | == Roundtable == | ||
− | |||
− | |||
R&D100? | R&D100? |
Revision as of 08:17, 24 October 2022
Attendees:
ECP Updates
- ECP All Hands Meeting submissions
- Due by October 28 (this Friday)
- An DAV overview BOF will not be done this year
- P6 Activity reporting
- Get key people on AD allocations
- The following AD codes will be running early on Frontier
- LatticeQCD, ExaSMR, ExaSky (HACC), CANDLE, EQSIM, Subsurface, WDMApp, WarpX
- For WarpX: they have already run their KPP-1. Further KPP-3 will likely be in ALPINE's project (CSC340).
- If we are providing software assistance for any of these, or we are planning a KPP-3, we should have a member as part of their allocation.
- The following AD codes will be running early on Frontier
- 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
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.