Difference between revisions of "Teleconference 2024-03-26"

From VTKM
Jump to navigation Jump to search
(Created page with "Attendees: == OASIS Deliverables == The following items are proposed for FY25 (which will end at the end of the fiscal year) * Address requests for support, improvement, a...")
 
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
Attendees:  
+
Attendees: Ken Moreland (ORNL), Mark Bolstad (SNL), Dave Pugmire (ORNL), Nicole Marsaglia (LLNL), Silvio Rizzi (ANL), Vicente Bolea (Kitware), Jeff Amstutz (Nvidia)
  
 
== OASIS Deliverables ==
 
== OASIS Deliverables ==
  
 
The following items are proposed for FY25 (which will end at the end of the fiscal year)
 
The following items are proposed for FY25 (which will end at the end of the fiscal year)
 +
  
 
* 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.
 
* 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.
 +
** Contouring of polygons (such as for contouring slices) added and merged. (Can we get a highlight out of that?)
 
* Strengthen operation of VTK-m on Aurora.
 
* Strengthen operation of VTK-m on Aurora.
 
* Improve documentation with automatic generation and web deployment.
 
* Improve documentation with automatic generation and web deployment.
Line 17: Line 19:
 
The HPSF has granted us some funding to transition our software from VTK-m to Viskores. This funding is provided to Kitware, and the contract is in place.
 
The HPSF has granted us some funding to transition our software from VTK-m to Viskores. This funding is provided to Kitware, and the contract is in place.
  
Vicente cannot be here today to talk about it, but the work will start shortly. You should still be able to make contributions to VTK-m until about March. At the end of the transition, we plan to do the final tagging and switch over completely to Viskores.
+
We are getting ready to transition from VTK-m (last release) to Viskores (first release). This transition will be happening in weeks.
 +
 
 +
There are some changes in the hosting of Viskores. These will be documented as we move forward.
  
 
There will be an HPSF Conference in Chicago May 5 - 8. Viskores will be part of that. I encourage VTK-m/Viskores TAC, developers, and users to attend. In the future, we can leverage the HPSF conference for user group meetings and/or hackathons if there is enough interest.
 
There will be an HPSF Conference in Chicago May 5 - 8. Viskores will be part of that. I encourage VTK-m/Viskores TAC, developers, and users to attend. In the future, we can leverage the HPSF conference for user group meetings and/or hackathons if there is enough interest.
Line 23: Line 27:
 
== Roundtable ==
 
== Roundtable ==
  
From previously:
+
Jeff: The VTK-m graph thing he made a while ago. Should that become part of Viskores proper? This contribution would be specifically graph hookup of Viskores components.
  
ParaView now requires C++17. Should we bump our minimum compiler version?
+
Pretty much everyone is moving to C++17. There is little reason to keep Viskores as C++14. Proposal: stick with C++14 through final release of VTK-m and initial release of Viskores. Next minor release of Viskores will be C++17. Ken will send poll out to TSG to get buy in.
  
 
Silvio tried building ParaView with SYCL with CMake settings that Abhishek gave him. The build works, but testing is forthcoming.
 
Silvio tried building ParaView with SYCL with CMake settings that Abhishek gave him. The build works, but testing is forthcoming.
  
Nicole has mesh with structured cells and explicit coordinates. External faces is throwing exceptions about a bad cast and call.
+
Nicole has mesh with structured cells and explicit coordinates. External faces is throwing exceptions about a bad cast and call. Ascent has a workaround, but Viskores should fix this issue.
  
 
Ascent getting weird ray culling issue.
 
Ascent getting weird ray culling issue.
 
Aurora filesystem for hosting users is very slow. They are supposed to migrate all preinstalled applications to images for every nodes. There is a strong push for installing things with spack. So, it is important that VTK-m installs well with spack. This is so these solutions can be cooked into an image that can be mounted on the nodes.
 
 
Heads up: Kokkos will be requiring C++20 soon.
 
 
ANARI 1.1 is on track for this summer. Will include unstructured and AMR fields.
 

Latest revision as of 11:44, 26 March 2025

Attendees: Ken Moreland (ORNL), Mark Bolstad (SNL), Dave Pugmire (ORNL), Nicole Marsaglia (LLNL), Silvio Rizzi (ANL), Vicente Bolea (Kitware), Jeff Amstutz (Nvidia)

OASIS Deliverables

The following items are proposed for FY25 (which will end at the end of the fiscal year)


  • 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.
    • Contouring of polygons (such as for contouring slices) added and merged. (Can we get a highlight out of that?)
  • Strengthen operation of VTK-m on Aurora.
  • Improve documentation with automatic generation and web deployment.
  • Integrate into High Performance Software Foundation (HPSF) as Viskores.
  • Improve integration between VTK-m/Viskores and VTK.

In the future, we will have to think about how to highlight VTK-m/Viskores. Our most visible deployment is usually through Ascent, but we don't want to take Ascent's thunder. I think Ascent gets its main funding through a different stream, so perhaps we could submit complementary highlights through SciDAC and NNSA.

Viskores / HPSF

The HPSF has granted us some funding to transition our software from VTK-m to Viskores. This funding is provided to Kitware, and the contract is in place.

We are getting ready to transition from VTK-m (last release) to Viskores (first release). This transition will be happening in weeks.

There are some changes in the hosting of Viskores. These will be documented as we move forward.

There will be an HPSF Conference in Chicago May 5 - 8. Viskores will be part of that. I encourage VTK-m/Viskores TAC, developers, and users to attend. In the future, we can leverage the HPSF conference for user group meetings and/or hackathons if there is enough interest.

Roundtable

Jeff: The VTK-m graph thing he made a while ago. Should that become part of Viskores proper? This contribution would be specifically graph hookup of Viskores components.

Pretty much everyone is moving to C++17. There is little reason to keep Viskores as C++14. Proposal: stick with C++14 through final release of VTK-m and initial release of Viskores. Next minor release of Viskores will be C++17. Ken will send poll out to TSG to get buy in.

Silvio tried building ParaView with SYCL with CMake settings that Abhishek gave him. The build works, but testing is forthcoming.

Nicole has mesh with structured cells and explicit coordinates. External faces is throwing exceptions about a bad cast and call. Ascent has a workaround, but Viskores should fix this issue.

Ascent getting weird ray culling issue.