ParaView 3 Telecon 01/16/2007

Item	People	Description
1	Moreland	Action Items
2	All	ParaView 3.0 Deliverables
3	Geveci	Time Implementation
4	Geveci	Icons
5	Greenfield	Selection crash
6	Goldman	Esim Vis project for XYCE
7	Moreland	Resolved bugs

Discussion

ParaView Deliverables

Time

He's working on it.

Animation

Committed basic GUI for animation. Just the left panel from PV 2. Selections for properties that are animatable. Entries for contours is missing. Time is still coming. Also can create animations with multiple views.

Ken observed that it seems to be really slow in some circumstances.

Client Side Delivery

Added a page to recent updates on what he has already done. Made modifcations that automate the whole process. The reduction filter can now take two algorithms.

Linking

Clint put in the initial checkin on Friday to show the current links. Cannot create or edit links yet.

Custom Filters/Lookmarks

Design document on Wiki.

Berk has suggested to take a chunk of time during next weeks meeting to talk about lookmarks.

Time

One request of PV 3 was to take the time value out of the individeal reader objects and have a global time value. Time is no longer a parameter of the filter, but is passed to the filter via its consumers. Put time requests in displays, and that gets propogated to views.

There will be a global time in PV. It will be animatable by the animation panel. All the views will be synced to this time. This is by value, not by steps. There needs to be a way to decouple the time from the view. This is so that we can have something like a "film strip" type of view.

When the user opens a reader or a source, query the time values, and store them in a data structure in the animation manager. You can animate such that each frame corresponds to a time value in a reader. You can also animate in time uniformly. The time that is in the animation is linked to the time in the reader. If you want the functionality where you have two readers in the same view with different time steps, we will need to do some sort of shift scaling. That probably will not make it this month.

Dave brought up the point that in Exodus files with mode shapes, it is common for different timesteps to have the same time value. There is also this funny business about setting the mode shape by changing the global time in some dark corner of the GUI. To get around this, it is decided that the Exodus reader should have some special case where if there are mode shapes, the mode (stored in the time value) is placed back in the Exodus reader panel. This makes the most sense, because in the case of mode shapes, the "time" in the exodus file is not really time, so it makes little sense to shove it into our time system.

We also need to make sure that as readers are deleted, that the animation panel "unloads" the time values for that reader correctly (keeping in mind that other readers might also have these steps). It is also possible for the time values to change in a reader at any time after "Accept" is hit. For examples, the Exodus reader may have mode shapes turned on or off, which makes its time values inaccessable or accessable.

Icons

We all like the Icons. There has been some comments on the mailing list. Those comments have been passed to Elevataion Design. They will send Berk vector and bitmap files.

Selection Crash

If you are forwarding X and do a selection (under Red Hat), you get a crash. Dave DeMarl has volunteered to fix that (which is good since he is already assigned the bug).