Difference between revisions of "Version 1.0 ToDo List"

From VTKM
Jump to navigation Jump to search
(Created page with "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 th...")
 
 
(11 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
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.
 
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.
  
−
{|
+
{| class="wikitable"
 
! Feature
 
! Feature
 
! Status
 
! Status
 
|-
 
|-
 
| 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.
+
| 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"
 
| Standardization of "filters"
−
* Proposal for filter interfaces in [https://gitlab.kitware.com/vtk/vtk-m/issues/17 issue #17]
+
| Done
−
| 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.
 
 
|-
 
|-
 
| Support worklet operations that are not one-to-one output
 
| Support worklet operations that are not one-to-one output
Line 16: Line 18:
 
|-  
 
|-  
 
| Basic file I/O
 
| Basic file I/O
−
| Done
+
| Done.
 
|-
 
|-
 
| Basic rendering
 
| Basic rendering
−
| Not started yet. There is a [[Rendering Infrastructure]] design document.
+
|
 +
* 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
−
| Behind. Trying to catch up.
+
| Behind. Trying to catch up. Making some progress.
 
|-
 
|-
 
| Green dashboard
 
| Green dashboard
 
|
 
|
−
* Still have problems with some CUDA dashboards
+
* Updated dashboard CUDA cards.
−
* Some working CUDA dashboards have a timer failure
+
** Memory issues no longer there.
−
* There have been some interop failures. - Rob thinks they are fixed.
+
** There is currently an issue with CUDA 7.5 and newer cards. It is a known bug with Thrust/CUB.
−
* Some further output issues on Windows (see delve dashboards e.g. https://open.cdash.org/viewTest.php?onlyfailed&buildid=4123995)
 
−
* 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.
 
 
|-
 
|-
 
| 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.)
−
| There was some integration for the SC demo, but that might not be very close to how we integrate in general. Still need to work on that.
+
|
 +
* 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"