Difference between revisions of "Teleconference 2022-06-01"

From VTKM
Jump to navigation Jump to search
(Created page with "Attendees: == ECP Updates == * ECP FY23 planning ** https://confluence.exascaleproject.org/display/1ST/FY23+Planning+Instructions ** Preliminary content due '''June 10''':...")
 
 
Line 1: Line 1:
Attendees:  
+
Attendees: Abdelilah Essiari (LLNL), Ken Moreland (ORNL), Sujin Philip (Kitware), Terry Turton (LANL), Tushar Athawale (ORNL), Mark Bolstad (SNL), Manish Mathai (UO), Ollie Lo (LANL)
  
 
== ECP Updates ==
 
== ECP Updates ==
Line 27: Line 27:
  
 
== Roundtable ==
 
== Roundtable ==
 +
 +
No meeting next 2 weeks.
 +
 +
Mark Bolstad is going to refactor the in situ benchmark so that the iteration is done by the benchmark framework rather than itself (to have the iteration iterated). The one trick is to make sure that the data "progresses" from one benchmark iteration to the next rather than use the same data over and over. The benchmark should also internally set a minimum amount of iterations.
  
 
R&D100?
 
R&D100?

Latest revision as of 11:30, 1 June 2022

Attendees: Abdelilah Essiari (LLNL), Ken Moreland (ORNL), Sujin Philip (Kitware), Terry Turton (LANL), Tushar Athawale (ORNL), Mark Bolstad (SNL), Manish Mathai (UO), Ollie Lo (LANL)

ECP Updates

Porting Activities

ECP task updates

ECP/VTK-m Project Management

Roundtable

No meeting next 2 weeks.

Mark Bolstad is going to refactor the in situ benchmark so that the iteration is done by the benchmark framework rather than itself (to have the iteration iterated). The one trick is to make sure that the data "progresses" from one benchmark iteration to the next rather than use the same data over and over. The benchmark should also internally set a minimum amount of iterations.

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.