Difference between revisions of "Teleconference 2022-04-13"
Jump to navigation
Jump to search
(Created page with "Attendees: == ECP Updates == * ECP Annual Meeting ** If you want to attend NDA sessions on Aurora, you need an account on Articus *** Get an account now before it is too la...") |
|||
Line 1: | Line 1: | ||
− | Attendees: | + | Attendees: Ken Moreland (ORNL), Nicole Marsaglia (LLNL), Mark Bolstad (SNL), Terry Turton (LANL), Silvio Rizzi (ANL), Sujin Philip (Kitware), Abhishek Yenpure (Kitware), Hank Childs (UO), Manish Mathi (UO) |
== ECP Updates == | == ECP Updates == |
Latest revision as of 11:41, 13 April 2022
Attendees: Ken Moreland (ORNL), Nicole Marsaglia (LLNL), Mark Bolstad (SNL), Terry Turton (LANL), Silvio Rizzi (ANL), Sujin Philip (Kitware), Abhishek Yenpure (Kitware), Hank Childs (UO), Manish Mathi (UO)
ECP Updates
- ECP Annual Meeting
- If you want to attend NDA sessions on Aurora, you need an account on Articus
- Get an account now before it is too late
- Poster discussion (due April 18)
- If you want to attend NDA sessions on Aurora, you need an account on Articus
- ECP FY23 planning
- Consider if you have the funding for our scope. Raise concerns early
- Start thinking about your FY23 P6 Activities
- What compute resources will we need to verify our KPP-3 scores?
- What will be done if applications don't come through themselves?
- 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
- Possible highlight slide on particle advection with WarpX (Matt)
- 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
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.
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.