Difference between revisions of "Teleconference 2020-03-18"

From VTKM
Jump to navigation Jump to search
(Created page with "== ECP Updates == * FY21 P6 Activities draft complete ** https://confluence.exascaleproject.org/pages/viewpage.action?pageId=85690510 * FY20 Q2 is nearing completion ** We sh...")
 
Line 22: Line 22:
  
 
Changed control-side portals to no longer lock ArrayHandles. Instead, you get an error logged if the portal is changed while you are still using it. Deadlocks should now be much harder to make.
 
Changed control-side portals to no longer lock ArrayHandles. Instead, you get an error logged if the portal is changed while you are still using it. Deadlocks should now be much harder to make.
 +
 +
Changing to GitLab continuous integration coming.
  
 
Can we get rid of streaming array handles and dispatching? This only works in very limited context and I expect it to never be used. (It may already be broken and we don't know it.)
 
Can we get rid of streaming array handles and dispatching? This only works in very limited context and I expect it to never be used. (It may already be broken and we don't know it.)

Revision as of 10:54, 18 March 2020

ECP Updates

  • FY21 P6 Activities draft complete
  • FY20 Q2 is nearing completion
    • We should be starting to complete our tasks for this quarter
    • Are we expecting any delays due to COVID-19?
  • 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)
    • Fastest contour in the west

ECP task updates

ECP/VTK-m Project Management

Roundtable

Fixed issues where WorldCoordiantesToParametericCoordinates and other operations would error out a worklet. Now have to deal with ErrorCode returned status.

Changed control-side portals to no longer lock ArrayHandles. Instead, you get an error logged if the portal is changed while you are still using it. Deadlocks should now be much harder to make.

Changing to GitLab continuous integration coming.

Can we get rid of streaming array handles and dispatching? This only works in very limited context and I expect it to never be used. (It may already be broken and we don't know it.)