ParaView 3 Telecon 05/08/2007: Difference between revisions
From ParaQ Wiki
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 17: | Line 17: | ||
| 6 || Moreland || [[Animation GUI]] | | 6 || Moreland || [[Animation GUI]] | ||
|} | |} | ||
== V&V Scripting == | |||
Greg Weirs is a user of PV who knows little of PV and VTK code. Greg has been the primary V&V driver. Most of our V&V request come indirectly from him. | |||
He is trying to use PV to do quantitative analysis. He wants the dynamic interaction that PV provides while being able to write scripts in the programmable filter. Once he gets the information he desires through PV, he is trying to repeat that for other data. Right now, he is using Python scripting to do so. | |||
The scripts written so far are the same basic operations done in the GUI. They use the programmable filter fairly heavily. The chalanging parts: | |||
* The pipeline/visualization model is different that what Greg and his colleagues are used to. It is difficult for him to match his problem description (e.g. pull some values out of an array) to the PV paradigms. | |||
* The multiple passes of the pipeline (REQUEST_INFORMATION, REQUEST_DATA, etc) are confusing. | |||
* PV and VTK tend to think in the global sense in that you attach filters to the entire data set. In the V&V analysis world, you are often focused on the cell level (it's values, its neighbors, etc.). | |||
Only major request: there is no direct access form the GUI to the data model (cells, points, connectivity, fields, etc.). | |||
== Deliverables == | |||
Revision as of 12:21, 8 May 2007
| Item | People | Description |
|---|---|---|
| 1 | All | ParaView 3.2 Deliverables Progress |
| 2 | Weirs | V&V Scripting |
| 3 | Karelitz | Use Logarithmic Scale greyed out |
| 4 | All | Open level 4 bugs |
| 5 | Moreland | Resolved bugs |
| 6 | Moreland | Animation GUI |
V&V Scripting
Greg Weirs is a user of PV who knows little of PV and VTK code. Greg has been the primary V&V driver. Most of our V&V request come indirectly from him.
He is trying to use PV to do quantitative analysis. He wants the dynamic interaction that PV provides while being able to write scripts in the programmable filter. Once he gets the information he desires through PV, he is trying to repeat that for other data. Right now, he is using Python scripting to do so.
The scripts written so far are the same basic operations done in the GUI. They use the programmable filter fairly heavily. The chalanging parts:
- The pipeline/visualization model is different that what Greg and his colleagues are used to. It is difficult for him to match his problem description (e.g. pull some values out of an array) to the PV paradigms.
- The multiple passes of the pipeline (REQUEST_INFORMATION, REQUEST_DATA, etc) are confusing.
- PV and VTK tend to think in the global sense in that you attach filters to the entire data set. In the V&V analysis world, you are often focused on the cell level (it's values, its neighbors, etc.).
Only major request: there is no direct access form the GUI to the data model (cells, points, connectivity, fields, etc.).
