ParaView 3 Telecon 01-23-2008: Difference between revisions
No edit summary |
No edit summary |
||
Line 12: | Line 12: | ||
|- | |- | ||
| 4 || Karelitz || MARS issues | | 4 || Karelitz || MARS issues | ||
|- | |||
| 5 || Karelitz || V&V Milestone | |||
|} | |} | ||
== VTK/ParaView Charts == | == VTK/ParaView Charts == | ||
ETI will start at the beginning of Feb. | |||
== GUI Plugins == | == GUI Plugins == | ||
Tim will create a Wiki page for requirements. | |||
== Deliverables == | == Deliverables == | ||
Line 22: | Line 28: | ||
=== Multiblock (Utkarsh, Berk, ETI) === | === Multiblock (Utkarsh, Berk, ETI) === | ||
Some stuff remaining. How to deliver structure to client. More things in ParaView. | |||
Dave T. expects a checkin-worthy something by the end of next week. | |||
=== SILO Reader (Pat) === | === SILO Reader (Pat) === | ||
Kitware is looking at a better way to handle meta data to provide better controls over things like selecting by material or block or assembly. This might move its way to Exodus as well. | |||
=== Selection (Dave Cole) === | === Selection (Dave Cole) === | ||
Ongoing. This will be stalled next week as many of Kitware will be out of town. | |||
=== Plugin improvements (ETI) === | === Plugin improvements (ETI) === | ||
Done. | |||
=== ParaView/Titan Chart Merger (Jeff, Utkarsh, Philippe, ETI) === | === ParaView/Titan Chart Merger (Jeff, Utkarsh, Philippe, ETI) === | ||
Line 50: | Line 62: | ||
=== 2D Image View type (Utkarsh) === | === 2D Image View type (Utkarsh) === | ||
There is now an image representation. Loads images as textures. | |||
=== Box and Sphere Widgets (Will) === | === Box and Sphere Widgets (Will) === | ||
Line 63: | Line 75: | ||
* Rendering speed problem. | * Rendering speed problem. | ||
** Fixed. | |||
* Save and disconnect. | * Save and disconnect. | ||
* Where is fragment identification happening? | ** Have a patch. | ||
** Also have a simple MPI-only example that shows the same problem with OpenMPI. | |||
** Need to figure out the "right" way to fix this. | |||
== V&V Milestone == | |||
Where is fragment identification happening? Why is it happening within the CTH Extract Parts filter? The CTH data set has lots of issues with tracking parts over boundaries. Having something that also worked with unstructured grid would be less efficient. The implementation for unstructured grids should not be hard. |
Latest revision as of 13:38, 24 January 2008
Item | People | Description |
---|---|---|
1 | Chart Task Force | VTK/ParaView Charts |
2 | Shead | GUI Plugins |
3 | All | ParaView 3.4 Deliverables |
4 | Karelitz | MARS issues |
5 | Karelitz | V&V Milestone |
VTK/ParaView Charts
ETI will start at the beginning of Feb.
GUI Plugins
Tim will create a Wiki page for requirements.
Deliverables
Multiblock (Utkarsh, Berk, ETI)
Some stuff remaining. How to deliver structure to client. More things in ParaView.
Dave T. expects a checkin-worthy something by the end of next week.
SILO Reader (Pat)
Kitware is looking at a better way to handle meta data to provide better controls over things like selecting by material or block or assembly. This might move its way to Exodus as well.
Selection (Dave Cole)
Ongoing. This will be stalled next week as many of Kitware will be out of town.
Plugin improvements (ETI)
Done.
ParaView/Titan Chart Merger (Jeff, Utkarsh, Philippe, ETI)
See above.
Volume Rendering Algorithm Chooser (Dave Cole)
After selection.
Plot multiple points/cells over time (Berk)
After multiblock work.
Textures (Utkarsh)
Done unless there is time to implement assigning any array to texture coordinates.
2D Image View type (Utkarsh)
There is now an image representation. Loads images as textures.
Box and Sphere Widgets (Will)
Will said he is working on it. Should be working before the release.
Custom filter cleanup (Utkarsh)
Done unless we have time left over.
MARS issues
- Rendering speed problem.
- Fixed.
- Save and disconnect.
- Have a patch.
- Also have a simple MPI-only example that shows the same problem with OpenMPI.
- Need to figure out the "right" way to fix this.
V&V Milestone
Where is fragment identification happening? Why is it happening within the CTH Extract Parts filter? The CTH data set has lots of issues with tracking parts over boundaries. Having something that also worked with unstructured grid would be less efficient. The implementation for unstructured grids should not be hard.