ParaView 3.2 Deliverables: Difference between revisions

From ParaQ Wiki
Jump to navigationJump to search
Line 76: Line 76:
| Better error reporting
| Better error reporting
| We need much better error reporting.
| We need much better error reporting.
|-
| Custom filters
| Custom filters are now maybe 70%. They need more work.
|-
|-
| Miscellaneous
| Miscellaneous

Revision as of 08:11, 13 April 2007

Descriptions

Deliverable Description
Better testing
  • Increase coverage
  • Test compositing
  • Memory checking
Compositing Support for desktop delivery without MPI
Display rearchitecture 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.
Multi-block Improve multi-block support:
  • Multi-block selection
  • Multi-block client delivery
  • Block inspector
Exodus reader
  • Switch to Dave T.'s new reader (with support for face/edge data).
  • Have multi-block output.
  • Support global variables.
  • Multiple outputs for main geometry, node/edge/face sets, and global variables?
Exodus writer It should work. If the original data was from Exodus files, the Exodus-specific metadata should be maintained.
Array calculator
  • Incorporate features from VisIt calculator.
  • Brainstorm on our own features.
Animation
  • GUI components for viewing all tracks (perhaps like in ParaView 2 or like a filmstrip keyframe viewer or both).
  • Support for viewing multiple animation steps at once.
    • Filmstrip viewer.
    • Comparative vis manager.
  • Support disconnect from server, create animation
Selection
  • Selecting points/cells from multiple sources.
  • Frustum selection.
  • Threshold selection (integrated with histogram bar chart).
  • Selecting blocks (and providing some sort of manipulation like turn off).
  • Selection based on probe (handle widget). It should support multiple handle widgets.
3D Widgets
  • It should be possible to snap 3D widget to surface with (P)
  • Add box widget
Annotation
  • Much better labeling - of selection and datasets in general. We need a way of visually matching a selection and an element inspector
Spreadsheet view Implement a model for a client side table that allows users to browse their data. It should only bring the portion of that data the user is viewing to the client (or a bigger cache that is still small)
Line chart/Bar chart
  • Better labeling and annotation
  • Line styles
  • Better zoom
Support for multiple output (custom) filters
Better error reporting We need much better error reporting.
Custom filters Custom filters are now maybe 70%. They need more work.
Miscellaneous
  • Texture Mapping.
  • Investigate browse/search dialog for adding filters.