ParaView 3.0 Deliverables: Difference between revisions

From ParaQ Wiki
Jump to navigationJump to search
No edit summary
No edit summary
Line 30: Line 30:
| Data analysis
| Data analysis
| Get back legacy features of picking by point Id and doing plot of point or cell variable over time.
| Get back legacy features of picking by point Id and doing plot of point or cell variable over time.
| 5
|-
| Better python
| Support for python wrapping and programmable filters (that call pipeline).
| 5
| 5
|-
|-
Line 54: Line 58:
| Testing
| Testing
| Testing, testing, and more testing.
| Testing, testing, and more testing.
| 4
|-
| Client side delivery
| Deliver data to client side with built in aggregation.
| 4
| 4
|-
|-
Line 83: Line 91:
| Fix bugs and add features.
| Fix bugs and add features.
| 3
| 3
|-
| Better python
| Support for python wrapping and V&V support.
| ?
|-
|-
| Multi-block support
| Multi-block support
| Improve multi-block support and make Exodus reader output multiblock.
| Improve multi-block support and make Exodus reader output multiblock.
| 1
|-
| Array calculator improvements
| VisIt's calculator is way better than ours.  For ParaView 3.2, we have should brainstorm to figure out what new features we want of our array calculator and how we implement them.  There may also be some DSTK requirements here.
| 1
| 1
|}
|}

Revision as of 11:43, 30 November 2006

Deliverable Description Priority
Dynamic default parameters ParaView 2 has lots of custom GUI code for filter parameters. ParaView 3 relies much more on server manager XML code and autogenerated panels. Missing from the new panels is the ability to vary parameters based on the size of the input geometry. This is very important in some filters such as the streamlines filter. 5
Annotation Much of the annotation abilities in ParaView 2 are missing in ParaView 3 (corner annotation, turninging off axis annotation, annotation with time value) and some new features (labels on specific cells). 5
New time support Ken Martin has recently updated the time support in VTK. We need to take advantage of that in ParaView 3. For example, we move the time setting parameters from reader parameters to pipeline keys. 5
Pipeline browser improvements Already our pipeline browser is much better than its predecessor. However, there still some improvements to go. Of special importance are feature gaps like handling multiple inputs. 5
Animation We need to reimplement all of the Animation GUI features of ParaView 2. 5
Readers/filters The backbone of ParaView needs to be tight. 5
Data analysis Get back legacy features of picking by point Id and doing plot of point or cell variable over time. 5
Better python Support for python wrapping and programmable filters (that call pipeline). 5
Volume rendering GUI Reimplement the ParaView 2 transfer function editors. 4
Icons 'Knuff said. 4
Custom filters/lookmarks Lots of old features, lots of new features. 4
Linking Add GUI to link server manager proxy objects (such as camera view and pipeline object parameters). 4
Plotting We got the nice charts, now make them really useful. 4
Testing Testing, testing, and more testing. 4
Client side delivery Deliver data to client side with built in aggregation. 4
Support for multiple outputs Multiple outputs are useful for lookmarks/custom filters. It would also be nice to have node sets and side sets be handled as multiple outputs on the Exodus filter. 3
Color map improvements Improve the GUI. Manage connections between views. 3
Undo/redo stability pass It's a new feature. Make sure it works right. 3
Display re-architecture Make it easier to add new views. As the infovis comes online, we will be making many new views we need to integrate into ParaView and its vertical apps. 3
Modules/plugins Rearchitect the "Load Module" feature and make it better. 3
Documentation Make online documentation available. 3
Selection Fix bugs and add features. 3
Multi-block support Improve multi-block support and make Exodus reader output multiblock. 1
Array calculator improvements VisIt's calculator is way better than ours. For ParaView 3.2, we have should brainstorm to figure out what new features we want of our array calculator and how we implement them. There may also be some DSTK requirements here. 1