ParaView 3.6 Deliverables: Difference between revisions
From ParaQ Wiki
Jump to navigationJump to search
(New page: {| border=1 ! Name ! Description ! Owner |- |ParaView/Titan Chart Merger |If not already complete. |- | Tables | * Make vtkTables a supported pipeline object type. It should have its own ...) |
No edit summary |
||
Line 14: | Line 14: | ||
* csv readers/writers should work principally (perhaps exclusively) with tables. | * csv readers/writers should work principally (perhaps exclusively) with tables. | ||
* Support reading other delimited text files. | * Support reading other delimited text files. | ||
* Simple conversion from tables to other data (such as collection of points). | |||
|- | |- | ||
| Multicore | | Multicore | ||
Line 23: | Line 24: | ||
| Simplified state/scripting | | Simplified state/scripting | ||
| Right now getting any scripting in ParaView has a high learning curve. State files are unreadable and almost completely uneditable. To do any scripting at all, you need to learn a significant chunk of Python bindings. To make this easier, ParaView should output a much more friendly way of scripting things. Either the state written out should be much simpler (show only the things that pertain to the current view) or be able to write out a very simplified Python script to get back to the state, or both. | | Right now getting any scripting in ParaView has a high learning curve. State files are unreadable and almost completely uneditable. To do any scripting at all, you need to learn a significant chunk of Python bindings. To make this easier, ParaView should output a much more friendly way of scripting things. Either the state written out should be much simpler (show only the things that pertain to the current view) or be able to write out a very simplified Python script to get back to the state, or both. | ||
|- | |||
| Particle Support | |||
| Leverage the work from CSCS. | |||
* Provide a particle representation that renders points more intelligently | |||
** Spheres with size vs. squares of pixel width | |||
** Optional sizing based on a scalar | |||
** Appropriate alpha blending (at least when particles are small) | |||
* Filters for meshless data? (Need to get customer requirements.) | |||
** Sampling point cloud? | |||
** Surface extraction? | |||
|- | |- | ||
| Movie view | | Movie view |
Revision as of 08:32, 8 April 2008
Name | Description | Owner |
---|---|---|
ParaView/Titan Chart Merger | If not already complete. | |
Tables |
| |
Multicore | Multi-core desktops are becoming commonplace. It is now reasonable for a user to invest in an 8 core desktop with several GB of memory in lieu of a visualization cluster. Unfortunately, ParaView has no good way of taking advantage of the multiple cores. | |
D4 | Time to get rolling on the next generation distributed data decomposition filter. D4 Design | |
Simplified state/scripting | Right now getting any scripting in ParaView has a high learning curve. State files are unreadable and almost completely uneditable. To do any scripting at all, you need to learn a significant chunk of Python bindings. To make this easier, ParaView should output a much more friendly way of scripting things. Either the state written out should be much simpler (show only the things that pertain to the current view) or be able to write out a very simplified Python script to get back to the state, or both. | |
Particle Support | Leverage the work from CSCS.
| |
Movie view | Add movie file readers that behave like an image reader the supports time. When viewed in a 2D image view with the time controls, ParaView becomes a simple movie viewer. | |
Temporal cleanup |
| |
Custom filter cleanup |
| |
Shaders | Implementation in 2.6 is "experimental" and does not seem to be of any practical use to anyone. Utkarsh is working on new GPU pipeline stuff. Next generation should take advantage of that. |