ParaView 3.0 Deliverables: Difference between revisions

From ParaQ Wiki
Jump to navigationJump to search
No edit summary
Line 3: Line 3:
! Description
! Description
! Priority
! Priority
|-
| Python
| Support for python wrapping and programmable filters (that call pipeline).
| 5
|-
|-
| Dynamic default parameters
| 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.
| 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
|-
| Readers/filters
| The backbone of ParaView needs to be tight.
| 5
| 5
|-
|-
Line 12: Line 20:
| 5
| 5
|-
|-
| New time support
| Pipeline browser
| 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.
| 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
| 5
|-
|-
| Animation
| GUI cleanup
| We need to reimplement all of the Animation GUI features of ParaView 2.
| Make the GUI look nice, usable, and information rich.  The parameter panels in the object inspector are of particular importance.  The display tab also needs work.  The spacing of toolbar icons can also be corrected.
| 5
| 5
|-
|-
| Readers/filters
| Data analysis
| The backbone of ParaView needs to be tight.
| Get back legacy features of picking by point Id and doing plot of point or cell variable over time.
| 5
| 5
|-
|-
| Data analysis
| Time
| Get back legacy features of picking by point Id and doing plot of point or cell variable over time.
| 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
| 5
|-
|-
| Better python
| Animation
| Support for python wrapping and programmable filters (that call pipeline).
| We need to reimplement all of the Animation GUI features of ParaView 2.
| 5
| 5
|-
|-
| Volume rendering GUI
| Volume rendering GUI
| Reimplement the ParaView 2 transfer function editors.
| Reimplement the ParaView 2 transfer function editors.
| 4
|-
| Icons
| 'Knuff said.
| 4
| 4
|-
|-
Line 52: Line 52:
| 4
| 4
|-
|-
| Plotting
| Client side delivery
| We got the nice charts, now make them really useful.
| Deliver data to client side with built in aggregation.
| 4
|-
| Icons
| 'Knuff said.
| 4
| 4
|-
|-
Line 60: Line 64:
| 4
| 4
|-
|-
| Client side delivery
| Plotting
| Deliver data to client side with built in aggregation.
| We got the nice charts, now make them really useful.
| 4
| 4
|-
|-
| Support for multiple outputs
| Color map
| Multiple outputs are useful for lookmarks/custom filtersIt would also be nice to have node sets and side sets be handled as multiple outputs on the Exodus filter.
| Improve the GUIManage connections between views.
| 3
| 3
|-
|-
| Color map improvements
| Multiple outputs
| Improve the GUIManage connections between views.
| Multiple outputs are useful for lookmarks/custom filtersIt would also be nice to have node sets and side sets be handled as multiple outputs on the Exodus filter.
| 3
| 3
|-
|-
| Undo/redo stability pass
| Selection
| It's a new feature.  Make sure it works right.
| Fix bugs and add features.
| 3
| 3
|-
|-
| Display re-architecture
| Plugins
| 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.
| Rearchitect the "Load Module" feature and make it better.
| 3
| 3
|-
|-
| Modules/plugins
| Undo/redo
| Rearchitect the "Load Module" feature and make it better.
| It's a new feature.  Make sure it works right.
| 3
| 3
|-
|-
Line 88: Line 92:
| 3
| 3
|-
|-
| Selection
| Display re-architecture
| Fix bugs and add features.
| 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
| 3
|-
|-
| Multi-block support
| Multi-block
| Improve multi-block support and make Exodus reader output multiblock.
| Improve multi-block support and make Exodus reader output multiblock.
| 1
| 1
|-
|-
| Array calculator improvements
| Exodus writer
| VisIt's calculator is way better than oursFor ParaView 3.2, we have should brainstorm to figure out what new features we want of our array calculator and how we implement themThere may also be some DSTK requirements here.
| We broke the Exodus writer a while agoUsers have been complainingWe should fix it.
| 1
| 1
|-
|-
| Exodus writer
| Array calculator
| We broke the Exodus writer a while agoUsers have been complainingWe should fix it.
| VisIt's calculator is way better than oursFor ParaView 3.2, we have should brainstorm to figure out what new features we want of our array calculator and how we implement themThere may also be some DSTK requirements here.
| 1
| 1
|}
|}
Line 111: Line 115:
! December !! January !! Febuary !! March !! Beyond
! December !! January !! Febuary !! March !! Beyond
|-
|-
| Python (DeMarle)
| Better python (DeMarle)
| Time (Geveci)
| New time support (Geveci)
| Plotting (Ayachit)
| Plotting (Ayachit)
| Undo/redo (Ayachit)
| Undo/redo (Ayachit)
Line 119: Line 123:
| Dynamic default parameters (Ayachit)
| Dynamic default parameters (Ayachit)
| Animation (Ayachit)
| Animation (Ayachit)
| Color map (Richardson)
| Color map improvements (Richardson)
| Bug fixes (team)
| Bug fixes (team)
| Multi-block (Geveci)
| Multi-block support (Geveci)
|-
|-
| Readers/filters (Ayachit)
| Readers/filters (Ayachit)
Line 133: Line 137:
| Selection (DeMarle)
| Selection (DeMarle)
| rowspan=6 |  
| rowspan=6 |  
| Array calculator (Ayachit)
| Array calculator improvements (Ayachit)
|-
|-
| Pipeline browser (Richardson)
| Pipeline browser (Richardson)
| Linking (Stimpson)
| Linking (Stimpson)
| Plugins (Stimpson/Cedilnik)
| Modules/plugins (Stimpson/Cedilnik)
| rowspan=5 |  
| rowspan=5 |  
|-
|-
| GUI cleanup (Stimpson)
| GUI panel replacements (Stimpson)
| Client side delivery (DeMarle)
| Client side delivery (DeMarle)
| rowspan=3 |  
| rowspan=3 |  

Revision as of 15:25, 30 November 2006

Deliverable Description Priority
Python Support for python wrapping and programmable filters (that call pipeline). 5
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
Readers/filters The backbone of ParaView needs to be tight. 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
Pipeline browser 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
GUI cleanup Make the GUI look nice, usable, and information rich. The parameter panels in the object inspector are of particular importance. The display tab also needs work. The spacing of toolbar icons can also be corrected. 5
Data analysis Get back legacy features of picking by point Id and doing plot of point or cell variable over time. 5
Time 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
Animation We need to reimplement all of the Animation GUI features of ParaView 2. 5
Volume rendering GUI Reimplement the ParaView 2 transfer function editors. 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
Client side delivery Deliver data to client side with built in aggregation. 4
Icons 'Knuff said. 4
Testing Testing, testing, and more testing. 4
Plotting We got the nice charts, now make them really useful. 4
Color map Improve the GUI. Manage connections between views. 3
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
Selection Fix bugs and add features. 3
Plugins Rearchitect the "Load Module" feature and make it better. 3
Undo/redo It's a new feature. Make sure it works right. 3
Documentation Make online documentation available. 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
Multi-block Improve multi-block support and make Exodus reader output multiblock. 1
Exodus writer We broke the Exodus writer a while ago. Users have been complaining. We should fix it. 1
Array calculator 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

Timeline

December January Febuary March Beyond
Better python (DeMarle) New time support (Geveci) Plotting (Ayachit) Undo/redo (Ayachit) Display re-architecture (Geveci/Ayachit)
Dynamic default parameters (Ayachit) Animation (Ayachit) Color map improvements (Richardson) Bug fixes (team) Multi-block support (Geveci)
Readers/filters (Ayachit) Volume rendering GUI (Richardson) Multiple outputs (Geveci) Clean build process (team) Exodus writer (Stanton)
Annotation (Geveci) Custom filters/lookmarks (Stanton) Selection (DeMarle)   Array calculator improvements (Ayachit)
Pipeline browser (Richardson) Linking (Stimpson) Modules/plugins (Stimpson/Cedilnik)  
GUI panel replacements (Stimpson) Client side delivery (DeMarle)  
Data analysis (Stanton)
Icons (Geveci and team)
Testing (Geveci, Ayachit, Stimpson, Stanton, others)