Difference between revisions of "Teleconference 2023-01-11"
Jump to navigation
Jump to search
(Created page with "Attendees: == ECP Updates == * KPP-3 * Budget estimations for FY24 ** Our budget estimations will probably be foobar as always ** Unless you tell me otherwise, I am going t...") |
|||
Line 5: | Line 5: | ||
* KPP-3 | * KPP-3 | ||
* Budget estimations for FY24 | * Budget estimations for FY24 | ||
− | ** Our budget estimations | + | ** Our budget estimations are foobar as always |
− | ** Unless you tell me otherwise, I am going to ask to estimate based on spend plan | + | ** Unless you tell me otherwise, I am going to ask to estimate based on spend plan and ask for 1/4 of FY23's budget |
+ | ** BTW, it looks like SNL and LANL are running hot. Make sure you leave enough funds to the end of the year. | ||
* Get key people on AD allocations | * Get key people on AD allocations | ||
** The following AD codes will be running early on Frontier | ** The following AD codes will be running early on Frontier | ||
Line 30: | Line 31: | ||
== Roundtable == | == Roundtable == | ||
+ | |||
+ | No meeting next week. See some of you in Houston. | ||
Decided on doing 4 "early" KPP-3 metrics | Decided on doing 4 "early" KPP-3 metrics |
Revision as of 09:52, 11 January 2023
Attendees:
ECP Updates
- KPP-3
- Budget estimations for FY24
- Our budget estimations are foobar as always
- Unless you tell me otherwise, I am going to ask to estimate based on spend plan and ask for 1/4 of FY23's budget
- BTW, it looks like SNL and LANL are running hot. Make sure you leave enough funds to the end of the year.
- 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
No meeting next week. See some of you in Houston.
Decided on doing 4 "early" KPP-3 metrics
- Flow for WarpX and/or WDMApp
- Springboard off Abhishek's thesis work
- Ascent integration
- ParaView integration
- VisIt integration
R&D100?
- Thinking of submitting for 2023
- Big stumbling block: needs to be "created" between Jan 2022 to March 2023
- 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.