Difference between revisions of "Version 1.0 ToDo List"

From VTKM
Jump to navigation Jump to search
 
(5 intermediate revisions by the same user not shown)
Line 8: Line 8:
 
| Other than little things and filters, the core interface is pretty well set.
 
| 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.
 
* 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.
 +
** The latest thought was to have a flag that states a mixed dimensionality flag.
 +
** The latest latest thought that there are not a lot of "pros" for dimensionality. Jeremy has an action item to remove it.
 
|-
 
|-
 
| Standardization of "filters"
 
| Standardization of "filters"
−
* Proposal for filter interfaces in [https://gitlab.kitware.com/vtk/vtk-m/issues/17 issue #17]
+
| Done
−
| 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 17: Line 18:
 
|-  
 
|-  
 
| 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. Rob and Sujin have identified the problem and have a potential fix.
+
| Done.
 
|-
 
|-
 
| 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. Matt is in the process of contributing his existing work to VTK-m.
+
|
 +
* Checked in with support from OSMesa (required).
 +
* An EGL implementation is on its way, but probably won't be official in the 1.0 release. The problem is that it relies on a change in GLEW that has not been released yet.
 +
* Dave created a glut example. To be merged to master.
 
|-
 
|-
 
| Clean up Doxygen
 
| Clean up Doxygen
−
| Need to get documentation syncing nightly.
+
| Need to get documentation syncing nightly. Chuck looking into this.
 
|-
 
|-
 
| User's Guide
 
| User's Guide
Line 30: Line 34:
 
| Green dashboard
 
| Green dashboard
 
|
 
|
−
* Still have problems with some CUDA dashboards
+
* Updated dashboard CUDA cards.
−
** Some may have been resolved
+
** Memory issues no longer there.
−
** There are issues with dejagore running out of memory
+
** There is currently an issue with CUDA 7.5 and newer cards. It is a known bug with Thrust/CUB.
−
* 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/>
 
| 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 has an initial implementation and it is working pretty well so far.
+
|
 +
* 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. He has lately added further cell type support (particularly unstructured grids).
 +
* Rob working on VTK/VTK-m filter integration. Can now move data between VTK and VTK-m
 
|}
 
|}

Latest revision as of 12:35, 11 May 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.
    • The latest thought was to have a flag that states a mixed dimensionality flag.
    • The latest latest thought that there are not a lot of "pros" for dimensionality. Jeremy has an action item to remove it.
Standardization of "filters" Done
Support worklet operations that are not one-to-one output Done
Basic file I/O Done.
Basic rendering
  • Checked in with support from OSMesa (required).
  • An EGL implementation is on its way, but probably won't be official in the 1.0 release. The problem is that it relies on a change in GLEW that has not been released yet.
  • Dave created a glut example. To be merged to master.
Clean up Doxygen Need to get documentation syncing nightly. Chuck looking into this.
User's Guide Behind. Trying to catch up. Making some progress.
Green dashboard
  • Updated dashboard CUDA cards.
    • Memory issues no longer there.
    • There is currently an issue with CUDA 7.5 and newer cards. It is a known bug with Thrust/CUB.
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. He has lately added further cell type support (particularly unstructured grids).
  • Rob working on VTK/VTK-m filter integration. Can now move data between VTK and VTK-m
Retrieved from "https://m-old.vtk.org/index.php?title=Version_1.0_ToDo_List&oldid=321"