Difference between revisions of "EngineeringRetreat2010"

From NAMIC Wiki
Jump to: navigation, search
Line 9: Line 9:
 
=Wishlist for Engineering core=
 
=Wishlist for Engineering core=
 
==Short term goals==
 
==Short term goals==
(targeted for AHM?)
+
*targeted for AHM
 +
*Assign owner
 +
 
 
* Rons number 1: Augment scenes and scenesnapshots
 
* Rons number 1: Augment scenes and scenesnapshots
 
**Thumbnails: user selectable toggle: 3d viewer (default), whole frame, red slice viewer
 
**Thumbnails: user selectable toggle: 3d viewer (default), whole frame, red slice viewer

Revision as of 18:25, 22 October 2010

Home < EngineeringRetreat2010
Back to Events

Goals: Develop clarity and a plan for this year's work; establish broader strategic vision for the next four NAMIC years.

Logistics

  • When: November 17-18 (Wednesday and Thursday). Start time: noon Wednesday, end time: early afternoon Thursday
  • Where: Boston SPL, 1249 Facility
  • Who: Engineering Core leaders and key personnel

Wishlist for Engineering core

Short term goals

  • targeted for AHM
  • Assign owner
  • Rons number 1: Augment scenes and scenesnapshots
    • Thumbnails: user selectable toggle: 3d viewer (default), whole frame, red slice viewer
    • Annotation: User-provided description of scenesnapshot/scene
    • Tool to replace thumbnails, edit annotations
  • Rons number 2: unified load: harmonize loading of different types of data, from local and remote data sources. Make plans for logic components, local database & UI design
  • Rons number 3: Review Slicer3 bug tracker for issues and feature requests - in particular widgets, command line modules, improved transforms/registration...
  • Rons number 4: Keep Slicer4 Qt port on schedule
  • Scene snapshot module: reorder, rename
  • organizing multiple data sets from one subject: time series, image fusion etc.

longer term infrastructure improvements

  • Make plans for a new and improved Editor for slicer4
  • Grow Cuts, RSS and fast Marching with volume cropping and volume rendering
  • Investigate use of a binary mask used with volume rendering to specify non-rectilinear ROIs, to display segmentation results, and to display effects of interactive editing
  • extended save: save to local and remote destinations. Make plans for logic components, DB transaction, and UI design.
  • GUI Testing
  • Support scenes containing data that spans multiple scales in time and space
    • visualize, indicate correspondence and support interactions with a scene in which the data differ by orders of magnitude and change over time
  • Infrastructure that supports simultaneous GPU-based volume rendering and GPU-based interactive segmentation methods (vtkWidgets)
  • Define a "Core" Slicer that can be distributed with InsightApplications repository of ITKv4
    • Two audiences:
      • Simple Interface for Radiologists
      • Simple, Extensible Platform for Developers (for custom apps/interfaces).
  • Guidelines and examples for GPU-based algorithms
  • Interactive/iterative command-line modules (e.g., tied to a vtkWidget)
  • DICOM via CTK
  • Determine an alternative to Mantis/bug-tracking. We have over 495 bugs.
  • Batch processing (IPython) examples
    • includes an algorithm validation framework
  • Interact with ITKv4, CTK, NiPy, and other like-minded projects.
  • Review Slicer application framework to support modularization and customization

Agenda

See also

Attendees

  1. Steve Pieper
  2. Will Schroeder
  3. Jim Miller
  4. Ron Kikinis