Difference between revisions of "Teleconference 2016-01-20"

From VTKM
Jump to navigation Jump to search
(Created page with "Attendees: Ken Moreland (SNL), Matt Larsen (LLNL), Eric Bruger (LLNL), Chris Sewell (LANL), Rob Maynard (Kitware), Berk Geveci (Kitware), Jeremy Meredith (ORNL), Tom Fogal (NV...")
 
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
Attendees: Ken Moreland (SNL), Matt Larsen (LLNL), Eric Bruger (LLNL), Chris Sewell (LANL), Rob Maynard (Kitware), Berk Geveci (Kitware), Jeremy Meredith (ORNL), Tom Fogal (NVIDIA)
+
Attendees: Ken Moreland (SNL), Matt Larsen (LLNL), Eric Bruger (LLNL), Chris Sewell (LANL), Rob Maynard (Kitware), Berk Geveci (Kitware), Jeremy Meredith (ORNL), Tom Fogal (NVIDIA), Brent Lesly (OU)
  
 
Chris has a call with Kitware later for a call on distributed memory with VTK-m. Have some students this summer that will be working with VTK-m. Initially planning to look into VTK-m with Legion.
 
Chris has a call with Kitware later for a call on distributed memory with VTK-m. Have some students this summer that will be working with VTK-m. Initially planning to look into VTK-m with Legion.
Line 14: Line 14:
  
 
Matt is in the process of stripping of the rendering things off of his branch and is going to check it into a rendering module for VTK-m.
 
Matt is in the process of stripping of the rendering things off of his branch and is going to check it into a rendering module for VTK-m.
 +
 +
Brent has been working on a tetrahedralization worklet. He is currently in the debugging phase of that.
 +
 +
We went over the [[Version 1.0 ToDo List]]. Here is a snapshot of that.
 +
 +
{| class="wikitable"
 +
! Feature
 +
! Status
 +
|-
 +
| Settling of the core interface
 +
| Other than little things and filters, the core interface is pretty well set.
 +
* Rob has a question about the "dimensionality" of the cell sets. That is supposed to be the topological dimensions of the cells. This would require all the cells having the same dimensionality, which is not really being honored. This is causing some problems. Jeremy and Rob need talk about this.
 +
|-
 +
| Standardization of "filters"
 +
* Proposal for filter interfaces in [https://gitlab.kitware.com/vtk/vtk-m/issues/17 issue #17]
 +
| There is a WIP branch on the implementation of filters with a few initial filters added to it. We should have a design discussion about it.
 +
|-
 +
| Support worklet operations that are not one-to-one output
 +
| Done
 +
|-
 +
| Basic file I/O
 +
| Done. Except Matt has been having trouble loading in VTK files. There appears to be an issue with VTK files exported from VisIt. It is probably some extra meta-data that VisIt is adding. Rob and Sujin have identified the problem and have a potential fix.
 +
|-
 +
| Basic rendering
 +
| Not started yet. There is a [[Rendering Infrastructure]] design document. A lot of the things Matt has been working on could be used. Jeremy and Dave will use that as a start. Matt is in the process of contributing his existing work to VTK-m.
 +
|-
 +
| Clean up Doxygen
 +
| Need to get documentation syncing nightly.
 +
|-
 +
| User's Guide
 +
| Behind. Trying to catch up. Making some progress.
 +
|-
 +
| Green dashboard
 +
|
 +
* Still have problems with some CUDA dashboards
 +
** Some may have been resolved
 +
** There are issues with dejagore running out of memory
 +
* Some working CUDA dashboards have a timer failure
 +
* There have been some interop failures. - Rob thinks they are fixed.
 +
* Some further output issues on Windows (see delve dashboards e.g. https://open.cdash.org/viewTest.php?onlyfailed&buildid=4123995)
 +
** Need to get the buildbot tests running nightly to check up on this issue.
 +
* Some timeout issues on renar (e.g. https://open.cdash.org/viewTest.php?onlyfailed&buildid=4123644). Could be caused by JIT of CUDA kernels or might be because multiple things are running.
 +
** This should be resolved with a branch being merged in today.
 +
|-
 +
| Prototype VTK/ParaView/VisIt integration<br/>
 +
(Technically not part of the release, but should indicate we have viable components.)
 +
| Eric Brugger has made some progress on integrating VTK-m into VisIt. He has an initial implementation and it is working pretty well so far.
 +
|}

Latest revision as of 13:55, 20 January 2016

Attendees: Ken Moreland (SNL), Matt Larsen (LLNL), Eric Bruger (LLNL), Chris Sewell (LANL), Rob Maynard (Kitware), Berk Geveci (Kitware), Jeremy Meredith (ORNL), Tom Fogal (NVIDIA), Brent Lesly (OU)

Chris has a call with Kitware later for a call on distributed memory with VTK-m. Have some students this summer that will be working with VTK-m. Initially planning to look into VTK-m with Legion.

Rob working on filters branch. It is a WIP merge request. It would be good to dedicate a meeting on the filters design. Perhaps we can do that next week.

A branch checked in that made some dramatic changes to testing. It made the test sizes much smaller. That was then lost when the CellSetListTagDefault was expanded to include to rectilinear grids. We need a technical discussion after the version 1.0 release on managing executable sizes (and maybe compile time).

Jeremy has been interested in organizing an event in Europe that would be a tutorial/hackathon for VTK-m. The question is finding a venue where we would have a large enough audience to justify doing the work and travel.

Eric has been making progress on the VTK-m-VisIt integration. There are some things in the VisIt trunk. You can select using either VTK or VTK-m, and if you select VTK-m it will use it for any enabled filter.

Ken noticed that there is a WorkletMapPointToCell, but there is no WorkletMapCellToPoint. Either Ken or Jeremy will add one because not having it is just an oversight.

Matt is in the process of stripping of the rendering things off of his branch and is going to check it into a rendering module for VTK-m.

Brent has been working on a tetrahedralization worklet. He is currently in the debugging phase of that.

We went over the Version 1.0 ToDo List. Here is a snapshot of that.

Feature Status
Settling of the core interface Other than little things and filters, the core interface is pretty well set.
  • Rob has a question about the "dimensionality" of the cell sets. That is supposed to be the topological dimensions of the cells. This would require all the cells having the same dimensionality, which is not really being honored. This is causing some problems. Jeremy and Rob need talk about this.
Standardization of "filters" There is a WIP branch on the implementation of filters with a few initial filters added to it. We should have a design discussion about it.
Support worklet operations that are not one-to-one output Done
Basic file I/O Done. Except Matt has been having trouble loading in VTK files. There appears to be an issue with VTK files exported from VisIt. It is probably some extra meta-data that VisIt is adding. Rob and Sujin have identified the problem and have a potential fix.
Basic rendering Not started yet. There is a Rendering Infrastructure design document. A lot of the things Matt has been working on could be used. Jeremy and Dave will use that as a start. Matt is in the process of contributing his existing work to VTK-m.
Clean up Doxygen Need to get documentation syncing nightly.
User's Guide Behind. Trying to catch up. Making some progress.
Green dashboard
  • Still have problems with some CUDA dashboards
    • Some may have been resolved
    • There are issues with dejagore running out of memory
  • Some working CUDA dashboards have a timer failure
  • There have been some interop failures. - Rob thinks they are fixed.
  • Some further output issues on Windows (see delve dashboards e.g. https://open.cdash.org/viewTest.php?onlyfailed&buildid=4123995)
    • Need to get the buildbot tests running nightly to check up on this issue.
  • Some timeout issues on renar (e.g. https://open.cdash.org/viewTest.php?onlyfailed&buildid=4123644). Could be caused by JIT of CUDA kernels or might be because multiple things are running.
    • This should be resolved with a branch being merged in today.
Prototype VTK/ParaView/VisIt integration

(Technically not part of the release, but should indicate we have viable components.)

Eric Brugger has made some progress on integrating VTK-m into VisIt. He has an initial implementation and it is working pretty well so far.