ParaView 3 Telecon 01/23/2007: Difference between revisions
No edit summary |
No edit summary |
||
(3 intermediate revisions by the same user not shown) | |||
Line 17: | Line 17: | ||
| 6 || Karelitz || DART Metadata | | 6 || Karelitz || DART Metadata | ||
|- | |- | ||
| 7 || Moreland || [http://www.paraview.org/Bug/query.php?status%5B%5D=5&emailsearch1=email&email1=&emailtype1=like&emailfield1%5B%5D=owner&title=&title_type=like&description=&description_type=like&url=&url_type=like&start_date=&end_date=&closed_start_date=&closed_end_date=&projects=14&versions=&closedinversion=&tobeclosedinversion=&components=&op=doquery&savedqueryoverride=0&order=severity.sort_order&sort=asc&op=doquery Resolved bugs] | | 7 || Moreland || Camera view link fast path | ||
|- | |||
| 8 || Moreland || [http://www.paraview.org/Bug/query.php?status%5B%5D=5&emailsearch1=email&email1=&emailtype1=like&emailfield1%5B%5D=owner&title=&title_type=like&description=&description_type=like&url=&url_type=like&start_date=&end_date=&closed_start_date=&closed_end_date=&projects=14&versions=&closedinversion=&tobeclosedinversion=&components=&op=doquery&savedqueryoverride=0&order=severity.sort_order&sort=asc&op=doquery Resolved bugs] | |||
|- | |||
| 9 || Moreland || Next week's ring leader | |||
|} | |} | ||
== Deliverables == | |||
=== Time (Geveci) === | |||
If a read provides time through the pipeline, you get to see that in the information tab. Updated exodus reader to work better with time stuff. PExdous reader now work. Added some time stuff to the update suppressor. | |||
Next, update the displays and views to incoporate that. Utkarsh will update the animation to use it. | |||
=== Animation (Ayachit) === | |||
Put in the disconnect and save animation, but could not yet resolve the multi-view issue for that. That has been tabled. | |||
Enabled automatically turning off the geometry cache if the geometry is too big or there are too many steps. Also added loop button. | |||
=== Client Side Delivery (DeMarl) === | |||
Added the "sum" operation. Waiting to see more use cases. Dave K. will be sending Dave D. as they come in in the next few weeks. | |||
All filters are geometry independent. | |||
=== Linking (Stimpson) === | |||
Linking dialog box is now in and allows you to create and edit links. | |||
Right now links are one way. The group has decided that, for now, all links should be "bi-directional." We can add uni-directional later if there is a use case. | |||
=== Bugs/Misc (Richardson) === | |||
Working on selecting multiple items to the pipeline and apply multi-input filters like append to them all right away. | |||
== Esim Vis == | |||
After talks between Jon and Berk and Utkarsh, it sounds like his use cases will be addressed in next month's deliverables. | |||
== New Custom Filter Features == | |||
After much discussion, it seems reasonable to separate the functionality of lookmarks and custom filters in both implementation and GUI. Lookmarks simply save a section of state that can be restored whereas custom filters make an actual composite filter that is applied. | |||
For now, lookmarks will record everything about the view, but not about multiple views. | |||
== Global Dataset Variables == | |||
In Exodus files, there are a bunch of field variables that are one-per-data set. If the variables are placed in field data, it should be an easy fix to send them downstream. Dave K. will create a bug and assign it to Berk. | |||
== DART Metadata == | |||
When you change the value of a checkbox for a parts or materials, that selection would be propogated to the other checkboxes of other types in ParaView 2. This is not working on ParaView 3. | |||
The issue is that the properties on the reader are interrelated. | |||
== Camera link view fast path == | |||
We want a special GUI for linking camera views. What should it look like? | |||
Mark suggested that there be a right-click popup menu on each view with "Link Camera" and "Unlink Camera" entries. On selecting these entries, a rubber band will extend to the cursor, and the user clicks on the corresponding view to link or unlink the camera to. | |||
Of course, there should be entries in the main menu bar (probably under View) that allow to link and unlink the camera of the current view. Toolbar buttons are also probably appropriate. |
Latest revision as of 14:10, 23 January 2007
Item | People | Description |
---|---|---|
1 | Moreland | Action Items |
2 | All | ParaView 3.0 Deliverables |
3 | Goldman | Esim Vis project for XYCE |
4 | Stanton | New Custom Filter Features |
5 | Karelitz | Global dataset variables |
6 | Karelitz | DART Metadata |
7 | Moreland | Camera view link fast path |
8 | Moreland | Resolved bugs |
9 | Moreland | Next week's ring leader |
Deliverables
Time (Geveci)
If a read provides time through the pipeline, you get to see that in the information tab. Updated exodus reader to work better with time stuff. PExdous reader now work. Added some time stuff to the update suppressor.
Next, update the displays and views to incoporate that. Utkarsh will update the animation to use it.
Animation (Ayachit)
Put in the disconnect and save animation, but could not yet resolve the multi-view issue for that. That has been tabled.
Enabled automatically turning off the geometry cache if the geometry is too big or there are too many steps. Also added loop button.
Client Side Delivery (DeMarl)
Added the "sum" operation. Waiting to see more use cases. Dave K. will be sending Dave D. as they come in in the next few weeks.
All filters are geometry independent.
Linking (Stimpson)
Linking dialog box is now in and allows you to create and edit links.
Right now links are one way. The group has decided that, for now, all links should be "bi-directional." We can add uni-directional later if there is a use case.
Bugs/Misc (Richardson)
Working on selecting multiple items to the pipeline and apply multi-input filters like append to them all right away.
Esim Vis
After talks between Jon and Berk and Utkarsh, it sounds like his use cases will be addressed in next month's deliverables.
New Custom Filter Features
After much discussion, it seems reasonable to separate the functionality of lookmarks and custom filters in both implementation and GUI. Lookmarks simply save a section of state that can be restored whereas custom filters make an actual composite filter that is applied.
For now, lookmarks will record everything about the view, but not about multiple views.
Global Dataset Variables
In Exodus files, there are a bunch of field variables that are one-per-data set. If the variables are placed in field data, it should be an easy fix to send them downstream. Dave K. will create a bug and assign it to Berk.
DART Metadata
When you change the value of a checkbox for a parts or materials, that selection would be propogated to the other checkboxes of other types in ParaView 2. This is not working on ParaView 3.
The issue is that the properties on the reader are interrelated.
Camera link view fast path
We want a special GUI for linking camera views. What should it look like?
Mark suggested that there be a right-click popup menu on each view with "Link Camera" and "Unlink Camera" entries. On selecting these entries, a rubber band will extend to the cursor, and the user clicks on the corresponding view to link or unlink the camera to.
Of course, there should be entries in the main menu bar (probably under View) that allow to link and unlink the camera of the current view. Toolbar buttons are also probably appropriate.