View source for 2010-09-Leadership-Brainstorming

 [[Leadership:Main| 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=

{|
|-
|align="left"|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.
|-
|[[image:2010-DBP-CS-teams.png|center|thumb|500px|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: [[DBP3:Main|DBP third generation]]

=Computer Science=
*[[AlgorithmRetreat2010|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:
*** Infrastructure that supports simultaneous GPU-based volume rendering and GPU-based interactive segmentation methods (vtkWidgets)
*** 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
*** Investigate use of a binary mask to specify non-rectilinear ROIs, to display segmentation results, and to display effects of interactive editing
*** Finish [http://www.slicer.org/slicerWiki/index.php/Slicer4 Slicer4] (Qt port) on schedule
*** Review [http://www.na-mic.org/Bug/view_all_bug_page.php Slicer3 bug tracker] for issues and feature requests - in particular widgets, command line modules, improved transforms/registration...
*** Interact with [http://www.kitware.com/blog/home/post/49 ITKv4], [http://commontk.org CTK], [http://nipy.sourceforge.net/software/projects/ NiPy], and other like-minded projects.
*** [http://www.na-mic.org/Wiki/index.php/Projects:ARRA:SlicerAM:KWWidgets VTK 3D Widgets] plans
*** Make plans for a new and improved [http://www.slicer.org/slicerWiki/index.php/Modules:Editor-Documentation-3.6 Editor] for slicer4
****Graph Cuts, RSS and fast Marching with volume cropping and volume rendering
****Gestures in 2d and 3d
***Thumbnails everywhere: mrml files, scene snapshots,
***Scene snapshot module: reorder, rename
***unified load: harmonize loading of different types of data, from local and remote data sources. Make plans for logic components, local database & UI design
***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.

=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?)
* [[2010-Slicer-Factory|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
*[[PeopleCycle2Staging|Update of mailing lists]]
*[[Event:2011_Registration_Retreat|New Directions in Registration Workshop]]