2010-09-Leadership-Brainstorming

 Back to Leadership Main

Everybody

• Please check to see that you have enough money budgeted for all necessary travel expenses: Project Weeks, All-Hands Meeting (AHM), core retreats, working meetings, participation in outreach activities.

DBP

Although the full NA-MIC team is engaged in supporting the DBPs, each DBP has been assigned specific algorithm and engineering partners from the Computer Science Cores 1A and 1B who are responsible either for providing technical support to the DBP directly, or for connecting them to the relevant NA-MIC resources. Partners have been allocated a separate line item in the budget that is distinctly allocated to support their time and travel to the DBP site.

DBP teams

• Each new DBP must host an in-person kick-off meeting at their site with their algorithm and engineering partners before the end of the year. The goal of this meeting is to develop concrete and short-term plans for the DBP roadmap project.
  • Utah-NA-MIC-2010-Kickoff
  • Iowa-NA-MIC-2010-Kickoff
  • MGH-NA-MIC-2010-Kickoff
  • UCLA-NA-MIC-2010-Kickoff
• Each DBP will present their plans during their AHM presentation.
• It is crucial to identify the DBP engineer as soon as possible.

• wiki presence: DBP third generation

Computer Science

• Algorithm retreat before the end of the year
• Engineering
  • TCON participation is mandatory for each site. Each engineering group has to be represented at all engineering TCON's.
  • Wishlist for Engineering core:
    • Rons number 1: 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 2: Review Slicer3 bug tracker for issues and feature requests - in particular widgets, command line modules, improved transforms/registration...
    • Annotated thumbnails everywhere: mrml files, scene snapshots, individual volumes and models
      • Ability to replace existing thumbnails, edit annotations
    • Finish Slicer4 (Qt port) on schedule
    • 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
    • Scene snapshot module: reorder, rename
    • 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.
    • organizing multiple data sets from one subject: time series, image fusion etc.
    • VTK 3D Widgets plans
    • Make plans for a new and improved Editor for slicer4
      • Grow Cuts, RSS and fast Marching with volume cropping and volume rendering
      • Gestures in 2d and 3d
    • 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
    • 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

Outreach

• Update the website after NOGA is issued
• Plan Slicer training on the west coast
• Consider a NAMIC training activity at University of Utah to be done in conjunction with January 2011 AHM.

Service

• Centralize testing data outside of code repository (using method from ITKv4?)
• "Core" Slicer distributed with InsightApplications repository with ITKv4
• Switch to centralized CDash ("CDash at Home")
• Support independent dashboard for each extension
  • Track platforms and slicer versions supported by each extension
  • Enable and track inter-extension dependencies
• Transition to GIT
  • Establish a GIT workflow / policy
• Support extensions hosted at other git repositories
  • Use ITKv4 module management technology
• Transition to ITKv4
• factory.slicer.org : Have the new setup ready for the AHM
  • superbuild
  • nightlies
  • extensions
  • dashboards for trunk, extensions, selected
  • updating website to reflect those changes
• support migration of Na-mic and Slicer websites

Leadership

• Press Release
• Update of mailing lists
• New Directions in Registration Workshop