Difference between revisions of "Events:Slicer4-Review-07-2011"

From NAMIC Wiki
Jump to: navigation, search
Line 46: Line 46:
  
 
===Infrastructure===
 
===Infrastructure===
* Move to git/gerrit
+
* Move to git/gerrit (TBD - can it be used with git-svn or is the suggestion to retire svn?)
 
* GUI Testing
 
* GUI Testing
 
** Instrumenting CTK widgets
 
** Instrumenting CTK widgets
 
** Conversion of tutorials to tests
 
** Conversion of tutorials to tests
 +
** What will this provide that [http://sikuli.org/ Sikuli] does not?  Sonia is ready to use Sikuli unless there is a good reason not to.
 
* Tk/Tcl
 
* Tk/Tcl
** Removing the last dependencies
+
** Removing the last dependencies in core interaction loops
 +
** Maintain functionality for Editor
 
* Performance optimization
 
* Performance optimization
 
** Module for profiling events
 
** Module for profiling events

Revision as of 23:32, 12 July 2011

Home < Events:Slicer4-Review-07-2011

What

Slicer 4 review and programming sprint

When

July 19, 10 am -21, 4pm 2011

Who

Slicer 4 core programmers

Where

Demo room, 2nd floor, 1249 Boylston Street, Boston, MA

Why

Work on

Main Topics

  • Critical Features
  • Bug fixes
  • Download setup and integration with the existing Slicer website

Priority TBD

UI

  • Reformat capabilities: We need a widget and possibly a slider based interface.
  • Main GUI
    • face lift for the Slice viewers: reduce permanent non-image components. Reduce the number and depth of submenus.
    • 3D viewer should have similar appearance to slice viewers
  • Update tutorials
    • After main gui
    • Using GUI Testing
  • Volume rendering transfer function
    • Jittery, and banding
    • Threshold
    • Better appearance of the elements of the transfer function. They look ugly and are not antialiased. Check the graph in Ohloh and mouse over it. Looks much nicer!
    • Group selection and shifting

Under the hood

  • GPU Volume Rendering
    • Support for ATI and MAC
    • How many GPU render engines to support/provide?
      • Ron says: I just need a single one that works for flythroughs and can handle the combination of volume rendering, cross-sections, surface models, annotations
  • hierarchies
    • display: the current display is confusing.
    • drag and drop capability
  • Annotations
    • vtkWidgets
    • GUI layout
    • compositing with volume rendering does not work properly
    • Working group (?)

Infrastructure

  • Move to git/gerrit (TBD - can it be used with git-svn or is the suggestion to retire svn?)
  • GUI Testing
    • Instrumenting CTK widgets
    • Conversion of tutorials to tests
    • What will this provide that Sikuli does not? Sonia is ready to use Sikuli unless there is a good reason not to.
  • Tk/Tcl
    • Removing the last dependencies in core interaction loops
    • Maintain functionality for Editor
  • Performance optimization
    • Module for profiling events
  • Extensions
    • Support for superbuild
    • Requirements for testing, documentation, tutorials, and continued support from developers
      • How to name different levels of compliance
  • Downloads
    • Statistics on packages and on individual extensions
    • Web pages
    • Technologies
  • Charts
    • Reference Implementation (Marcus)
  • MIDAS
    • sceneviews support
  • Interactive CLI modules

Agenda

Attending

  1. Ron Kikinis
  2. Steve Pieper
  3. Nicole Aucoin
  4. Julien Finet
  5. Daniel Haehn (only 07/19)
  6. Jean-Christophe Fillion-Robin
  7. Stephen Aylward
  8. Will Schroeder
  9. Jim Miller