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
−
| Rob working on interface for finding what device adapters are available at runtime. Probably will move device adapter traits outside of internal.
+
| Ken needs to look at dynamic cell set because it has a different than the dynamic array and is causing much more code generation.
 
|-
 
|-
 
| 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]
−
| Rob is going to work on this. Originally the design was to compile filters into libraries, but the latest design is using a header-based approach. The current status is at https://gitlab.kitware.com/robertmaynard/vtk-m/tree/vtkm_filters.
+
| There is a WIP branch on the implementation of filters with a few initial filters added to it.
 
|-
 
|-
 
| Support worklet operations that are not one-to-one output
 
| Support worklet operations that are not one-to-one output
Line 16: Line 16:
 
|-  
 
|-  
 
| Basic file I/O
 
| Basic file I/O
−
| Done. Except Matt has been having trouble loading in VTK files. He has had to modify the files to get them to work. Action item: Matt needs to send an example file that does not work to the Kitware folks to take a look.
+
| 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.
 
|-
 
|-
 
| Basic rendering
 
| Basic rendering
−
| Not started yet. There is a [[Rendering Infrastructure]] design document.
+
| 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.
 
|-
 
|-
 
| Clean up Doxygen
 
| Clean up Doxygen

Revision as of 13:37, 13 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 Ken needs to look at dynamic cell set because it has a different than the dynamic array and is causing much more code generation.
Standardization of "filters" There is a WIP branch on the implementation of filters with a few initial filters added to 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. Sujin will take a look at that.
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.
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 is able to run the marching cubes algorithm from within VisIt and generate images.
Retrieved from "https://m-old.vtk.org/index.php?title=Version_1.0_ToDo_List&oldid=261"