Sandia-Kitware Summit, 2009

Tuesday, April 7

Time	Length	Item	Who
9:00	0.5 hr	Coffee and "A man walks into a bar..." jokes	All
9:30	1 hr	Multicore	Shepherd
10:30	0.5 hr	Charting EKG	Wylie
11:00	1 hr	Annotation	Shead
12:00	0.5 hr	Working Lunch	All
12:30	1 hr	Statistics Tutorial	Thompson
1:30	1 hr	Plugins Loading Management Subtractive Plugins Controlling UI Client/Server Plugins Branding for ParaView Bringing OverView into ParaView fold	Shead
2:30	0.5 hr	OverView Release	Wylie
3:00	0.5 hr	Qt 4.5 Migration LGPL File segregation Font migration	Wylie
3:30	0.5 hr	ParaView 3.6 status/release schedule	Moreland
4:00	1 hr	MARS Fragment generation in exodus Crater identification Visualizing Tracers Milestone status Announcements of feature identification capability Export Control	Ice
5:00	0.5 hr	CSCS Particle Stuff	Moreland

Wednesday, April 8

Time	Length	Item	Who
9:00	0.5 hr	Coffee and "A man walks into a bar..." jokes	All
9:30	1 hr	New View/Representation Heirarchy	Wylie, Baumes
10:30	0.5 hr	Time Cleanup Time variable range loading (bug 8596) Issue with filters making inputs temporal	Ayachit
11:00	1 hr	In-Situ General in situ library Project coordination Data Array Strides and Iteration	Fabian, Geveci, Thompson, Moreland
12:00	0.5 hr	Working Lunch	All
12:30	1.5 hr	Informatics Strategery	Schroeder, Rogers
2:00	1.5 hr	Array Refactoring	Shead
3:30	0.5 hr	Lookmarks: Major push or jettison?	Moreland
4:00	---	Miscellaneous Pipeline Selection Conversion Easy File Reader Creation Unordered Color Maps Auto Variable Loading	---

Breakout Sessions

Item	Who
ParaView 3.8 Deliverables	Moreland, Ayachit, Ice

Action Items

• QtItemView should go away. -Brian
• Depricate vtkQtChartRepresentation. -Utkarsh
• Rename vtkQtChartViewBase to vtkQtChartView. -Utkarsh
• Add a set representation from input connection convenience function. This function may not always work on views with more complicated inputs (such as hierarchical graph view). -Pat
• Follow up with looking at Tim's Python wrappings for Qt views and to add wrappings for Chart views. -Pat
• Make ParaView startup be a branding startup. -Utkarsh

Plugins

It is a general consensus that it is beneficial to all if the ParaView and OverView main windows merged into one. This would work by making this main window be quite blank. The window would then load in a set of plugins, defined by the branding, which then populate the GUI. In this mode, subtractive plugins become much less important, which is good as this is a pretty dangerous concept.

We identified an open issue where ParaView and OverView have different selection mechanisms. We want to be able to mix sci vis and info vis, so we should find a way to unify the selections. We might be able to capture the difference as an autostart plugin, but that does not help much with respect to mixing sci vis to info vis.