View source for 2011 Winter Project Week:Slicer IGT Looking Forward

__NOTOC__
<gallery>
Image:PW-SLC2011.png|[[2011_Winter_Project_Week#Projects|Projects List]]
</gallery>


<font color=red>The session will be held from 14:30 on Wednesday, January 12</font>
==Key Investigators==
* BWH: Noby Hata, Laurent Chauvin,Junichi Tokuda, Andriy Fedorov
* Queens: Andras Lasso, Tamas Ungi
* Robarts: Martin Rajchl, Feng Li 
* PSI:Vladimir M. Nikonovskiy
* Kitware: Danielle Pace


<div style="margin: 20px;">
<div style="width: 27%; float: left; padding-right: 3%;">

<h3>Objective</h3>
To define objectives for Slicer IGT for the next five years...




</div>

<div style="width: 27%; float: left; padding-right: 3%;">

<h3>Approach, Plan</h3>
Invite IGT researcher to a brain storming session on 230pm, on Wednesday, and discuss (updated) unmet needs in Slicer.

</div>

<div style="width: 40%; float: left;">

<h3>Progress</h3>
The meeting was successfully held with 10+ participants. The following issue was noted

*Ascension tracker === currently using IGSTK, with Open IGT Link. coding into the module necessary? it is necessary for new users.

*Streaming data is not well supported, should be more supported. Video data. 4D US. Ultrasonix. Hardcode. Open IGT may not be a viable option. 
*Transparent switching bteween shared memory is a good idea! open igt link
*Customization of module 
*Handling financial proper way is tricky. 
*New Workflow management proposed from BWH team. Use Bundle of "modules" instead of coding subcomponents in the workflow mechanism. The added value of this approach is that the it facilitates IGT investigators to share "codes" and "method." Otherwise, we are duplicating codes across the modules.

*Performance. 
*DICOM listner/Database/query/retrieve (something equivalent to OsiriX)
*Support for sparse images
*MRML with time stamp attributes


</div>
</div>

<div style="width: 97%; float: left;">

==Delivery Mechanism==






</div>