Monthly Build Goals

Beyond

• More features

See ParaView 3.2 Deliverables for details.

October 2007

• Selecting blocks
• Exodus to multiblock
• New array calculator – BERK
• Better error reporting
• Texture map
• Hardware shaders

See ParaView 3.2 Deliverables for details.

September 2007 (ParaView 3.4)

• Multiblock selection
• Filmstrip viewer and comparative vis manager
• 3D widgets
• Plot along polylilne – BERK
• Threshold selection
• Spreadsheet view
• Icons for pipeline browser

See ParaView 3.2 Deliverables for details.

August 2007

• Clean up memory issues; Amy
• Multiblock inspector; Dave D.
• Volume render blocks of multiblock data; Dave D.
• Support server disconnect animation; Utkarsh
• Chart vector support; Mark
• Better custom filters; Berk
• Misc lookmarks; Eric
• Frustum selection; Dave D.
• Fast temporal plots; Eric
• Global exodus variable; Eric
• Better labeling selection and datasets; Yumin
• Remaining chart features; Mark
  • Include context menu interactivity

See ParaView 3.2 Deliverables for details.

July 2007 (ParaView 3.2)

• Display Re-architecture; Utkarsh
• Multiple Output; Berk
• Test compositing; Amy
• Setup valgrind; Amy
• Multiblock client delivery; Dave D.
• Animation GUI panel; Clint
• Switch to new exodus reader; Eric
• DART metadata support; Eric
• Exodus writer; Eric
• Chart – better zoom, legends, line styles and axis controls; Mark
• Fix linux progress in client server; Clint

See ParaView 3.2 Deliverables for details.

June 2007

• Annotation - better controls and widgets.
• Bug fixes

See ParaView 3.2 Deliverables for details.

April 2007 (ParaView 3.0)

• Undo/redo
• Bug fixes
• Clean build process

See ParaView 3.0 Deliverables for details.

March 2007

• Plotting
• Color map
• Multiple outputs
• Selection
• Plugins

See ParaView 3.0 Deliverables for details.

February 2007

• Time
• Animation
• Volume rendering GUI
• Custom filters/lookmarks
• Linking
• Client side delivery
• Icons

See ParaView 3.0 Deliverables for details.

January 2007

Released January 10, 2007.

Delivery goals:

• Python
  • Finished
• Dynamic default parameters
  • Finished
• Readers/filters
  • Finished, but the file dialog still needs to have the ability to show grouped files.
• Annotation
  • Mostly finished. An new feature was added where text annotation can be added as a source. The annotation works, but there are still a few bugs.
• Pipeline browser
  • Mostly finished. The "out-of-sync" feature missed the release by a few days. There are a few issues with the change input dialog that are being addressed.
• GUI cleanup
  • Finished everything except the ability to load material xml files.
• Data analysis
  • Delayed so that it is better integrated with the plotting and selection deliverables, which are slated for February.

See ParaView 3.0 Deliverables for descriptions and ParaView 3 Telecon 01/02/2007#December Deliverables for notes on their completion.

December 2006

Released December 12, 2006.

• Reading multiple exodus files.
• Many property panel improvements and fixes.
• File dialog fixes.
• Improved chart code.
• Improved testing framework, which now includes python.
• Improved pipeline browser.
• Play/Pause in VCR controls.
• Light Kit controls added.
• Auto generated and custom panel improvements.
• More robust server connection, w/ feedback.
• File dialog improvements.

Gap

Due to a change in leadership, there is a gap in the feature tracking. During the Sandia-Kitware-ETI Summit, Nov. 29-30, 2006, we defined a set of ParaView 3.0 Deliverables and made a timeline for them. The build goals picks up from there.

September 2006

• Final Icons - Delayed, contracted out
• Selection - Continuing
  • Select cells/points, graph current variable over time.
• Multiview
• Additional Filter Inspector work (auto-generated and custom)

August 2006

• Disconnect/Reconnect for movie making. Minimum: disconnect, with nice job shutdown.
• 'Simple' movie making works for 99% of SNL cases.
• Selection
  • Select cells/points, get results in spreadsheet. Results are all loaded variable values for the current timestep.
  • Select cells/points, use the selection set as the input to a 'subset' filter.
• Multiview
• Include all (most) filters
• Save Settings (QSettings)
• Simple, integrated graphing, including:
  • Determine if Charts should have a Qt model/view architecture. Make graphs work with VTK datasets.
  • Graph tool bar
  • Graphing of selection set
  • Graphing of output of a probe
  • Graphing of output of a filter (?)
• View control toolbar (reset view, +x,-x,+y,-y,+z,-z, etc)
• Display settings toolbar
  • 'Current Variable' combo should include var info (from the last tab of the current ParaView)
  • Representation
  • Scalar bar on/off

June 2006

• TS PGraph.
  • Extraction/Reduction filters and Render Module completed.
  • Hooking data to Clients.
  • Preliminary design for Client UI interaction (how does a user actually chart data?)

May (release date Friday, May 26th 2006)

The focus this month will be Client, Client, Client, and getting information and code passed around as efficiently as possible.

• Process: Add informal and frequent UI discussions, with live demos.
• Goal: Make the client useable.
• Goal: Fully support 5 common filters.
  • Exodus Reader
  • Threshold
  • Cut
  • Clip
• CS Accept/Reset
  • UI iteration on Exodus object inspector.
• TS 3D Widget Integration
• MR Pipeline Browser II.
  • Fan-in support.
  • Delete of pipeline items.
  • Save/Restore working properly.
  • Testing, documentation in repository.
  • Next: integration with Accept/Reset.
• CM Prism over ParaQ.
  • Commit preliminary Prism code to ParaQ repository.
  • Pursue Compound Filter work, because we'll likely use it to support Geometry and SESAME views.

April (release date Friday, April 28th 2006)

• Full support for building pipelines, including:
  • 3D widgets
  • Pipeline editor with fan-out support (user can easily understand connections, types of objects, state of those objects)
  • Undo/Redo on all operations
• File->Open, File->Save, File->Save As, File->New all need to work.
• Top-level 'Accept/Reset' buttons, properly connected to all operations.
• Bottom status bar (for now, this will mainly give feedback on popup help)
• Simple, Two-panel Default UI configuration:
  • Left Panel: pipeline browser and object inspector
  • Right Panel: render window.
  • Initial support for UI configuration file, including initial application geometry.
• Properly functioning Top-level VCR time controls (see bug 3075)
• Properly functioning Top-level Current Variable controls.
• First round support for Compound filters:
  • Compound Filter Toolbar, which shows loaded compound filters.
  • Ability to load compound filters from a designated place in the distribution (no need for user to browse).
  • Stretch goal: ability to save a set of filters as a compound filter. Saves current settings only - no control over UI when it is loaded.
• Initial Release Test Plan, captured in a recorded test.

Connection questions

• How will we connect to a parallel server?

Possible Add-ons (for completeness)

• Help
• Quick way to send feedback
• Usage tracking

March (release date Friday, March 31 2006)

Goals

This is our first monthly build, designed to start the habits of our development process. So, it's a bit light on content. It's our initial executable release, not intended to be released to users. This is a chance for us to get our repository ready for full-on development, and get Testing, Coverage, and Testplans in place.

Action Items

Item	Bug	Who	Status	Desc.
001	2976	BG	Done	Reformat repository
002	2977	BG	Done	Doxygen operates on entire repository
003	2977	BG	Done	Code properly commented (so Doxgen works on the entire repository
004	2978	BG	Not complete	Dashboard is green. BG will pursue miscreants and ne'er-do-wells
005	2979	BG	Ongoing	Adequate code coverage
006	2980	MR	Done (with ongoing feature requests)	Auto-generated object inspectors should be improved. In particular, useful widgets when possible, and the most eye-pleasing design possible. A general goal is that the automatically-generated object inspectors should be as well-designed, useful, and pleasing to the eye as possible.
007	2981	TS	Done	Demo-specific code removed
008	(none)	DR	Done	Action Items should be put into bug tracker. Make sure that all people are in bug tracker.

Summary of results

Good first month effort. It took quite a bit to re-format and update the repository - more than was originally expected. The updated auto-generated UI elements look super, but several XML-related things we'd like to do before we consider this item totally finished (check the bug tracker for these items). We tagged the repository, and we're addressing next month's build task at Sandia, so that we can be prepped for a quick turnaround of the April release.

The ParaQ dashboard is now 'useful', according to Berk, but we're not at a 'green' state yet. This was likely an unrealistic goal, given the timeframe of this release. There needs to be time (and, more importantly, the support for taking the time) for developers to write tests, and to make certain their checkins haven't broken the dashboard. We're definitely ramping up on this, so make space in your development schedule for tests and dashboard cleanup.

Our coverage will ramp up as SNL and ETI develop more tests for the UI components. Per Tim's suggestion, this will start in earnest in mid-April, when he's developed the infrastructure for runtime name checking on Qt objects.

We need to carry over the 'Code coverage' and 'Green dashboard' items and monitor them for a while. Still, a good first month - Nice work, everyone!