Difference between revisions of "Teleconference 2015-12-02"
Jump to navigation
Jump to search
(Created page with "Attendees: Ken Moreland (SNL), Rob Maynard (Kitware) Progress on the todo list for VTK-m V1.0: * Settling of the core interface * Standardization of "filters" ** What is the...") |
|||
Line 1: | Line 1: | ||
− | Attendees: Ken Moreland (SNL), Rob Maynard (Kitware) | + | Attendees: Ken Moreland (SNL), Rob Maynard (Kitware), Matt Larsen, Chris Sewell (LANL), Tom Fogal (NVIDIA), Jeremy Meredith (ORNL), Dave Pugmire (ORNL) |
+ | |||
+ | Matt brought up an issue that the current vtkm::Min and Max are slow because they are calling fmin and fmax, which are not getting inlined. We should always use vtkm::Min/Max with the possible exception of compiling for a CUDA device (where these functions are special to the compiler). | ||
Progress on the todo list for VTK-m V1.0: | Progress on the todo list for VTK-m V1.0: | ||
− | * Settling of the core interface | + | * Settling of the core interface - Rob working on interface for finding what device adapters are available at runtime. Probably will move device adapter traits outside of internal. |
− | * Standardization of "filters" | + | * Standardization of "filters" - Rob is going to work on this. The current suggested approach is that filters compile to libraries and there will be a mechanism to select some alternate form of standard storage and other lists to recompile for different layouts. |
** What is the distinction between multipass worklets and filters? | ** What is the distinction between multipass worklets and filters? | ||
** Rob has a proposal for filter interfaces in [https://gitlab.kitware.com/vtk/vtk-m/issues/17 issue #17] | ** Rob has a proposal for filter interfaces in [https://gitlab.kitware.com/vtk/vtk-m/issues/17 issue #17] |
Revision as of 13:31, 2 December 2015
Attendees: Ken Moreland (SNL), Rob Maynard (Kitware), Matt Larsen, Chris Sewell (LANL), Tom Fogal (NVIDIA), Jeremy Meredith (ORNL), Dave Pugmire (ORNL)
Matt brought up an issue that the current vtkm::Min and Max are slow because they are calling fmin and fmax, which are not getting inlined. We should always use vtkm::Min/Max with the possible exception of compiling for a CUDA device (where these functions are special to the compiler).
Progress on the todo list for VTK-m V1.0:
- Settling of the core interface - Rob working on interface for finding what device adapters are available at runtime. Probably will move device adapter traits outside of internal.
- Standardization of "filters" - Rob is going to work on this. The current suggested approach is that filters compile to libraries and there will be a mechanism to select some alternate form of standard storage and other lists to recompile for different layouts.
- What is the distinction between multipass worklets and filters?
- Rob has a proposal for filter interfaces in issue #17
- Support worklet operations that are not one-to-one output
- Basic file I/O
- Basic rendering
- Documentation
- Clean up doxygen
- User's Guide
- Green dashboard
- Prototype VTK/ParaView/VisIt integration
- (Technically not part of the release, but should indicate we have viable components.)