Difference between revisions of "Version 1.0 ToDo List"
Jump to navigation
Jump to search
| 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. | ||
* There is a similar question about the "order" on the fields. Right now, it is not used, and ''we should remove it''. In the future, as we implement higher order cells, we will probably have to represent the interpolation as basis functions rather than | * There is a similar question about the "order" on the fields. Right now, it is not used, and ''we should remove it''. In the future, as we implement higher order cells, we will probably have to represent the interpolation as basis functions rather than | ||
|- | |- | ||
| Standardization of "filters" | | Standardization of "filters" | ||
| − | + | | Done | |
| − | | | ||
|- | |- | ||
| Support worklet operations that are not one-to-one output | | Support worklet operations that are not one-to-one output | ||
| Line 32: | Line 32: | ||
| | | | ||
* Still have problems with some CUDA dashboards | * Still have problems with some CUDA dashboards | ||
| − | ** | + | ** Mostly fixed. Might be a timeout issue. |
| − | * There have been some interop failures | + | * There have been some interop failures. |
** Probably actually an X-windows issue. Chuck will look into this. Not currently at the top of his priority. | ** Probably actually an X-windows issue. Chuck will look into this. Not currently at the top of his priority. | ||
* The new GCC 5.0 compiler is giving warnings in the testing code. | * 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<br/> | | Prototype VTK/ParaView/VisIt integration<br/> | ||
Revision as of 12:40, 16 March 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.
|
| Standardization of "filters" | Done |
| Support worklet operations that are not one-to-one output | Done |
| Basic file I/O | Done. |
| Basic rendering | Rendering is almost ready. Working out some build issues on the dashboard. |
| 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 |
|
| Prototype VTK/ParaView/VisIt integration (Technically not part of the release, but should indicate we have viable components.) |
|
