Difference between revisions of "Teleconference 2022-08-03"

From VTKM
Jump to navigation Jump to search
Line 29: Line 29:
 
Status of dashboards
 
Status of dashboards
 
* macos_xcode13 (dragnipur) is back up but there appears to be a [https://open.cdash.org/build/8077303/configure git lfs] error and the tests are not being run.
 
* macos_xcode13 (dragnipur) is back up but there appears to be a [https://open.cdash.org/build/8077303/configure git lfs] error and the tests are not being run.
 +
** Causing CI to report an error that does not show up on the dashboard.
 
* The pascal runner (jool?) seems to be back up.
 
* The pascal runner (jool?) seems to be back up.
 
* The "external" buildbot builds no longer run.
 
* The "external" buildbot builds no longer run.

Revision as of 08:30, 3 August 2022

Attendees:

ECP Updates

  • Finalize next P6 Activity
  • Get key people on AD allocations
    • The following AD codes will be running early on Frontier
      • LatticeQCD, ExaSMR, ExaSky (HACC), CANDLE, EQSIM, Subsurface, WDMApp, WarpX
    • If we are providing software assistance for any of these, or we are planning a KPP-3, we should have a member as part of their allocation.
  • 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
    • Some work with MFIX. Going to execute on Summit. Might wait for run on early access machine before highlight.

Porting Activities

ECP task updates

ECP/VTK-m Project Management

Roundtable

Status of dashboards

  • macos_xcode13 (dragnipur) is back up but there appears to be a git lfs error and the tests are not being run.
    • Causing CI to report an error that does not show up on the dashboard.
  • The pascal runner (jool?) seems to be back up.
  • The "external" buildbot builds no longer run.
    • dragnipur already moved to new system.
    • What is the status of osheim? It is not run on buildbot but not in the runners either.

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.