Difference between revisions of "Version 1.0 ToDo List"

From VTKM
Jump to navigation Jump to search
Line 6: Line 6:
 
|-
 
|-
 
| Settling of the core interface
 
| Settling of the core interface
| Ken needs to look at dynamic cell set because it has a different than the dynamic array and is causing much more code generation.
+
| 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"
 
| Standardization of "filters"
 
* Proposal for filter interfaces in [https://gitlab.kitware.com/vtk/vtk-m/issues/17 issue #17]
 
* 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.
+
| 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
 
| Support worklet operations that are not one-to-one output
Line 16: Line 17:
 
|-  
 
|-  
 
| Basic file I/O
 
| 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. Sujin will take a look at that.
+
| 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
 
| 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.
+
| 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
 
| Clean up Doxygen
Line 41: Line 42:
 
| Prototype VTK/ParaView/VisIt integration<br/>
 
| Prototype VTK/ParaView/VisIt integration<br/>
 
(Technically not part of the release, but should indicate we have viable components.)
 
(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 is able to run the marching cubes algorithm from within VisIt and generate images.
+
| 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.
 
|}
 
|}

Revision as of 13:51, 20 January 2016

The following is a list of features collected in the months before the VTK-m 1.0 release that are on the short path to be completed.

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.