Summit Dec 2013: Difference between revisions
From ParaQ Wiki
Jump to navigationJump to search
| Line 51: | Line 51: | ||
* Improve parallel STL CSV writing so that you don't need to collect everything on process 0 (all at once). | * Improve parallel STL CSV writing so that you don't need to collect everything on process 0 (all at once). | ||
** Sounds crazy, but we have a use case to get data in professional graphics tools. | ** Sounds crazy, but we have a use case to get data in professional graphics tools. | ||
===Alan's Talking Points=== | |||
* ParaView documentation, especially compared to EnSight and VisIt | |||
* Python documentation, especially compared to VisIt. | |||
* ParaView python and scripting. (I will get an e-mail off before then with feedback i heard at SC). | |||
* Statistics. Statistics in parallel. Clearly mark statistics filters that give wrong results in parallel. | |||
* Updating VisIt reader | |||
* 3d view menus. 2d view menus. Toolbars (do we default them off, or on?) | |||
* Efficiently parallelizing CAM reader - and priority. | |||
* Future of Prism | |||
* Do we need another "cleanup release"? | |||
* Probe - interactive. Display X,Y,Z on the 3d view. Display any variable. | |||
* Needed miscellaneous functionality - volume, min, max, average, calculator accessing global data. | |||
* Material interface filter and non AMR data. | |||
* Document how the trace recorder works. | |||
* Create precanned Macros that ship with ParaView? | |||
* Possibly changing the layout of the settings panel to more of a Chrome layout. (This was Utkarsh's idea, I am still on the fence.) | |||
==Meeting Notes== | ==Meeting Notes== | ||
Revision as of 12:10, 27 November 2013
Location: Kitware Inc., Santa Fe, NM
Agenda
| Thursday, Dec 5, 2013 | |
|---|---|
| Time | Item |
| 8:30-9:00 | Coffee and knock-knock jokes |
| 9:00-11:00 | VTK-m Planning (Ken, Berk, Chris) |
| 11:00-12:00 | VTK-m Changes to ParaView (Berk, Ken, Jim or Chris) |
| 12:00-1:00 | Lunch |
| 1:00-3:00 | Software Engineering Issues (Utkarsh, Alan)
|
| 3:00-4:00 | NIH VTK Changes (Berk) |
| 4:00-5:00 | ParaWeb (Sebastian) |
Topic Suggestions
Add suggestions here, we can then put them on the agenda.
Deprecating Components
- Policy for deprecating code: with changes to Panels and others, we have lot of dead/uncovered/sparing used code. How to deal with it?
- What happens to components like Prism which are not being actively ported to new style?
- How about discarding old panels that don't seem to be used as much e.g. Statistics Inspector
Simplifying Plots
- Making Plots "editable" by interacting in the View rather than having to go to the "View Settings" page.
Parallel STL/CSV Writers
- Improve parallel STL CSV writing so that you don't need to collect everything on process 0 (all at once).
- Sounds crazy, but we have a use case to get data in professional graphics tools.
Alan's Talking Points
- ParaView documentation, especially compared to EnSight and VisIt
- Python documentation, especially compared to VisIt.
- ParaView python and scripting. (I will get an e-mail off before then with feedback i heard at SC).
- Statistics. Statistics in parallel. Clearly mark statistics filters that give wrong results in parallel.
- Updating VisIt reader
- 3d view menus. 2d view menus. Toolbars (do we default them off, or on?)
- Efficiently parallelizing CAM reader - and priority.
- Future of Prism
- Do we need another "cleanup release"?
- Probe - interactive. Display X,Y,Z on the 3d view. Display any variable.
- Needed miscellaneous functionality - volume, min, max, average, calculator accessing global data.
- Material interface filter and non AMR data.
- Document how the trace recorder works.
- Create precanned Macros that ship with ParaView?
- Possibly changing the layout of the settings panel to more of a Chrome layout. (This was Utkarsh's idea, I am still on the fence.)
