Difference between revisions of "Teleconference 2020-03-11"
Jump to navigation
Jump to search
| Line 16: | Line 16: | ||
[https://gitlab.kitware.com/kmorel/ecp-vtk-m-project-management ECP/VTK-m Project Management] | [https://gitlab.kitware.com/kmorel/ecp-vtk-m-project-management ECP/VTK-m Project Management] | ||
| + | |||
| + | == Roundtable == | ||
| + | |||
| + | Matt has been feeling some pain with the fact that control portals can lock access to their ArrayHandle. Suggesting backing out of this behavior (or be able to disable it). We have 3 possible behaviors | ||
| + | * Control portals block invalid access to ArrayHandle while still in scope (current behavior) | ||
| + | * Control portals check with the ArrayHandle to ensure the memory is still available, report error if not | ||
| + | ** Error could be assert | ||
| + | ** Error could be exception | ||
| + | ** Error could go to log | ||
| + | * Control portals ignore access and just assume data are still valid (old behavior) | ||
Revision as of 10:17, 11 March 2020
Attendees:
ECP Updates
- FY21 P6 Activities draft complete
- FY20 Q2 is nearing completion
- We should be starting to complete our tasks for this quarter
- Are there any budget issues?
- 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)
ECP task updates
Roundtable
Matt has been feeling some pain with the fact that control portals can lock access to their ArrayHandle. Suggesting backing out of this behavior (or be able to disable it). We have 3 possible behaviors
- Control portals block invalid access to ArrayHandle while still in scope (current behavior)
- Control portals check with the ArrayHandle to ensure the memory is still available, report error if not
- Error could be assert
- Error could be exception
- Error could go to log
- Control portals ignore access and just assume data are still valid (old behavior)
