Difference between revisions of "Teleconference 2020-10-07"
Jump to navigation
Jump to search
Line 5: | Line 5: | ||
* E4S document is up | * E4S document is up | ||
** If anyone cares, comments due by October 13 | ** If anyone cares, comments due by October 13 | ||
+ | * ECP Annual Meeting: April 12-15 | ||
+ | ** Submissions for tutorials, breakouts, and other things open (deadline December 15) | ||
+ | ** Do we want to organize VTK-m tutorial or breakout? (Usually couple with Alpine.) | ||
* ECP Independent Project Review pushed from October to February | * ECP Independent Project Review pushed from October to February | ||
** Means several of our deadlines have been pushed back | ** Means several of our deadlines have been pushed back |
Revision as of 12:55, 7 October 2020
Attendees:
ECP Updates
- E4S document is up
- If anyone cares, comments due by October 13
- ECP Annual Meeting: April 12-15
- Submissions for tutorials, breakouts, and other things open (deadline December 15)
- Do we want to organize VTK-m tutorial or breakout? (Usually couple with Alpine.)
- ECP Independent Project Review pushed from October to February
- Means several of our deadlines have been pushed back
- ECP ST Annual Reviews: Delayed to Dec 7-11
- Still "keen" on collecting information about early access systems by end of August
- 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
- Submitted highlight on integration with EFFIS
- Expect to submit another highlight when used in a big run
Porting Activities
- https://confluence.exascaleproject.org/display/STDA05/Porting+Activities+A21
- https://confluence.exascaleproject.org/display/STDA05/Porting+Activities+O21
ECP task updates
Roundtable
Matt Larsen has run into an issue with CUDA 11 where it is complaining while compiling DIY that the std:: namespace does not seem to exist. The issue might be related to new CUDA features that support more std objects on devices. As of now, no one has a good solution.
Follow up for benchmarking of Kokkos. Do we have profiling of what is being run during the "slow" filter benchmarks?
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.