Difference between revisions of "Teleconference 2022-03-30"
Jump to navigation
Jump to search
Line 25: | Line 25: | ||
* https://wiki.jlse.anl.gov/display/inteldga/ECP+2.3.4.13+VTK-m | * https://wiki.jlse.anl.gov/display/inteldga/ECP+2.3.4.13+VTK-m | ||
− | * https:// | + | * https://confluence.exascaleproject.org/display/STDA05/Porting+Activities+O21 |
== ECP task updates == | == ECP task updates == |
Latest revision as of 12:21, 30 March 2022
Attendees: Ken Moreland (ORNL), Mark Bolstad (SNL), Terry Turton (LANL), Hank Childs (UO), Nichole Marsaglia (UO), Vicente Bolea (Kitware), Berk Geveci (Kitware), Dave Pugmire (ORNL), Manish Mathi (UO), Tushar Athawale (ORNL), Sujin Philip (Kitware)
ECP Updates
- ECP funds approved for travel
- Still have to follow your local institutions rules
- Pre-COVID rules still apply
- 3-5% of overall budget
- Foreign travel requires ECP pre-approval (+ other DOE approvals)
- 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
- 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.