ParaView 3 Telecon 01-17-2008: Difference between revisions
(New page: {| cellpadding="2" cellspacing="4" |- ! style="background:#abcdef" | Item ! style="background:#abcdef" | People ! style="background:#abcdef" | Description |- | 1 || Chart Task Force || [ht...) |
No edit summary |
||
(5 intermediate revisions by 2 users not shown) | |||
Line 7: | Line 7: | ||
| 1 || Chart Task Force || [https://www.kitware.com/InfovisWiki/index.php/Common_Chart_Architecture VTK/ParaView Charts] | | 1 || Chart Task Force || [https://www.kitware.com/InfovisWiki/index.php/Common_Chart_Architecture VTK/ParaView Charts] | ||
|- | |- | ||
| 2 || | | 2 || Shead || GUI changing plugins | ||
|- | |- | ||
| 3 || Karelitz || MARS issues | | 3 || All || [[ParaView 3.4 Deliverables]] | ||
|- | |||
| 4 || Karelitz || MARS issues | |||
|} | |} | ||
== VTK/ParaView Charts == | == VTK/ParaView Charts == | ||
Many Titan projects are backing up on the charting. We really need to get things going. We have set a deadline as the end of February. | |||
ETI is not available right now. Everyone is working on another project. In February they should have two people able to work on the charting so that they can get the charting done. | |||
Those who require this charting work to build their own charting components should be proactive in determining if the implementation is sufficient for their needs. Some time in mid-February, those involved (e.g. Jeff Baumes and Andy Wilson) should take a look at the developing implementation and ensure that there is no feature gaps. | |||
== GUI changing plugins == | |||
Tim has had some success moving some of the TV work into ParaView plugins. There is some motivation to simply move the entire concept of OverView to a set of ParaView plugins. | |||
The main stumbling block to this is that simply adding something to ParaView does not make much sense for several InfoVis applications. A security investigator analyzing threats would wonder what the heck an isosurface is for. Thus, to implement OverView as plugins, there needs to be some more control over the user interface. | |||
== Deliverables == | == Deliverables == | ||
Line 18: | Line 32: | ||
=== Multiblock (Utkarsh, Berk, ETI) === | === Multiblock (Utkarsh, Berk, ETI) === | ||
Some issues with readers/writers. Ironing things out. | |||
Dave T. is working on multiblock Exodus. | |||
=== SILO Reader (Pat) === | === SILO Reader (Pat) === | ||
The latest version of VisIt has more data files. Our reader now works with all of these. | |||
Alan S. is getting some distributed SILO files. To be sent later today (assuming release OK). | |||
=== Selection (Dave Cole) === | === Selection (Dave Cole) === | ||
Ongoing. | |||
=== Plugin improvements (ETI) === | === Plugin improvements (ETI) === | ||
Clint was writing some code right before the meeting. Pretty much done. | |||
=== ParaView/Titan Chart Merger (Jeff, Utkarsh, Philippe, ETI) === | === ParaView/Titan Chart Merger (Jeff, Utkarsh, Philippe, ETI) === | ||
Line 57: | Line 79: | ||
== MARS issues == | == MARS issues == | ||
* Rendering speed problem. Between Jan 3 and Jan 15, rendering with display lists suddenly got a lot slower (by a factor of about 10). | |||
* Save and disconnect: does not bloat, but does not work either. The 0 process is in an SSend, everything else is in an all gather. |
Latest revision as of 13:46, 17 January 2008
Item | People | Description |
---|---|---|
1 | Chart Task Force | VTK/ParaView Charts |
2 | Shead | GUI changing plugins |
3 | All | ParaView 3.4 Deliverables |
4 | Karelitz | MARS issues |
VTK/ParaView Charts
Many Titan projects are backing up on the charting. We really need to get things going. We have set a deadline as the end of February.
ETI is not available right now. Everyone is working on another project. In February they should have two people able to work on the charting so that they can get the charting done.
Those who require this charting work to build their own charting components should be proactive in determining if the implementation is sufficient for their needs. Some time in mid-February, those involved (e.g. Jeff Baumes and Andy Wilson) should take a look at the developing implementation and ensure that there is no feature gaps.
GUI changing plugins
Tim has had some success moving some of the TV work into ParaView plugins. There is some motivation to simply move the entire concept of OverView to a set of ParaView plugins.
The main stumbling block to this is that simply adding something to ParaView does not make much sense for several InfoVis applications. A security investigator analyzing threats would wonder what the heck an isosurface is for. Thus, to implement OverView as plugins, there needs to be some more control over the user interface.
Deliverables
Multiblock (Utkarsh, Berk, ETI)
Some issues with readers/writers. Ironing things out.
Dave T. is working on multiblock Exodus.
SILO Reader (Pat)
The latest version of VisIt has more data files. Our reader now works with all of these.
Alan S. is getting some distributed SILO files. To be sent later today (assuming release OK).
Selection (Dave Cole)
Ongoing.
Plugin improvements (ETI)
Clint was writing some code right before the meeting. Pretty much 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)
In queue.
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. Between Jan 3 and Jan 15, rendering with display lists suddenly got a lot slower (by a factor of about 10).
- Save and disconnect: does not bloat, but does not work either. The 0 process is in an SSend, everything else is in an all gather.