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.
- Dave is working on a glut example/
|
| 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
|
- Still have problems with some CUDA dashboards
- Mostly fixed. Might be a timeout issue.
- The new GCC 5.0 compiler is giving warnings in the testing code.
- There is a merge request to address this. Most are cleaned up.
- Still working on some failure to vectorize warnings.
|
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
|
