Difference between revisions of "Teleconference 2024-10-09"

From VTKM
Jump to navigation Jump to search
(Created page with "Attendees: == OASIS Deliverables == * Address requests for support, improvement, and new features by current and potential applications such as XGC and WarpX as well as oth...")
 
 
Line 1: Line 1:
Attendees:  
+
Attendees: Ken Moreland (ORNL), Hank Childs (UO), Nicole Marsaglia (LLNL), Silvio Rizzi (ANL), Berk Geveci (Kitware), Jeff Amstutz (Nvidia)
  
 
== OASIS Deliverables ==
 
== OASIS Deliverables ==
Line 7: Line 7:
 
** Another render issue popped up. Can be replicated at small scale. Nicole working on it.
 
** Another render issue popped up. Can be replicated at small scale. Nicole working on it.
 
* Strengthen operation of VTK-m on Aurora.
 
* Strengthen operation of VTK-m on Aurora.
** There are still some failing tests.
+
** Renzo from Intel has tried VTK-m with a new version of the compiler that has some issues fixed. He reports things are working, but we need to follow up to make sure everything is passing now.
** They may be a problem with cell location, which might be an issue with Variant.
 
** Having Intel look into the previously identified union/variant bug found.
 
 
* Improve documentation with automatic generation and web deployment.
 
* Improve documentation with automatic generation and web deployment.
 
** User's guide continues to improve.
 
** User's guide continues to improve.
Line 30: Line 28:
 
Ascent getting weird ray culling issue.
 
Ascent getting weird ray culling issue.
  
Mark talked about some previous metrics where a Catalyst with SPARC integration was copying data back and forth from device. Ken thinks some recent changes may help some of this.
+
ANARI working group going to have a virtual hackathon October 21-23. Good opportunity to work though some VTK-m/ANARI integration.
  
ANARI working group going to have a virtual hackathon October 21-23. Good opportunity to work though some VTK-m/ANARI integration.
+
VTK-m is likely going to be a part of the European ANARI Community Project that is forming.

Latest revision as of 12:36, 9 October 2024

Attendees: Ken Moreland (ORNL), Hank Childs (UO), Nicole Marsaglia (LLNL), Silvio Rizzi (ANL), Berk Geveci (Kitware), Jeff Amstutz (Nvidia)

OASIS Deliverables

  • Address requests for support, improvement, and new features by current and potential applications such as XGC and WarpX as well as other users of ParaView, VisIt, and Ascent.
    • Ascent team solved ray tracing bug in VTK-m 2.2
    • Another render issue popped up. Can be replicated at small scale. Nicole working on it.
  • Strengthen operation of VTK-m on Aurora.
    • Renzo from Intel has tried VTK-m with a new version of the compiler that has some issues fixed. He reports things are working, but we need to follow up to make sure everything is passing now.
  • Improve documentation with automatic generation and web deployment.
    • User's guide continues to improve.
  • Ensure proper building and running at OLCF, ALCF, and NERSC through Spack.
    • Ken verified that Slack builds work on Perlmutter and Frontier.
    • Silvio will establish contact for Ken of someone at ALCF tasked with compiling stuff with Spack. Request that they also compile VTK-m/Kokkos.

Viskores / HPSF

Have formalized the initial TSC. Ken is considering adding the following voting members to the TSC to represent their respective institutions and projects.

  • Silvio Rizzi, representing needs of ANL/ALCF
  • Nicole Marsaglia, representing Ascent and LLNL
  • Gunther Weber, representing topology, LBL, NERSC?

We have a plan to transition from VTK-m to Viskores. We are hoping for some funding from the HPSF to do this.

Roundtable

Ascent getting weird ray culling issue.

ANARI working group going to have a virtual hackathon October 21-23. Good opportunity to work though some VTK-m/ANARI integration.

VTK-m is likely going to be a part of the European ANARI Community Project that is forming.