Difference between revisions of "Teleconference 2024-23-09"
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), Dave Pugmire (ORNL), Abhishek Yenpure (Kitware), Mark Bolstad (SNL), Silvio Rizzi (ANL), Nicole Marsaglia (LLNL), Hank Childs (UO) |
== OASIS Deliverables == | == OASIS Deliverables == | ||
| Line 6: | Line 6: | ||
** Ascent team solved ray tracing bug in VTK-m 2.2 | ** 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. | ** Another render issue popped up. Can be replicated at small scale. Nicole working on it. | ||
| + | ** Cyrus has noted that there appears to be an issue with contouring a surface. He is not getting the lines he expects. | ||
* Strengthen operation of VTK-m on Aurora. | * 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. | ** 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. | ||
| Line 12: | Line 13: | ||
* Ensure proper building and running at OLCF, ALCF, and NERSC through Spack. | * Ensure proper building and running at OLCF, ALCF, and NERSC through Spack. | ||
** Ken verified that Slack builds work on Perlmutter and Frontier. | ** Ken verified that Slack builds work on Perlmutter and Frontier. | ||
| − | ** Silvio | + | ** Silvio connected Ken with Sean Koyama who helped set up the Spack build. It has progressed further but still needs some updates. |
| + | ** Ken added SYCL compile option to spack package. This has been accepted by spack. | ||
== Viskores / HPSF == | == Viskores / HPSF == | ||
Latest revision as of 12:20, 23 October 2024
Attendees: Ken Moreland (ORNL), Dave Pugmire (ORNL), Abhishek Yenpure (Kitware), Mark Bolstad (SNL), Silvio Rizzi (ANL), Nicole Marsaglia (LLNL), Hank Childs (UO)
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.
- Cyrus has noted that there appears to be an issue with contouring a surface. He is not getting the lines he expects.
- 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 connected Ken with Sean Koyama who helped set up the Spack build. It has progressed further but still needs some updates.
- Ken added SYCL compile option to spack package. This has been accepted by spack.
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.
