Difference between revisions of "2010 Winter Project Week Slicer XNAT"
From NAMIC Wiki
Line 1: | Line 1: | ||
− | |||
{| | {| | ||
− | |[[Image:FetchMIDoc_Upload.png|thumb|400px| Upload of tagged data to remote host]] | + | |[[Image:FetchMIDoc_Upload.png|thumb|400px| Upload pipeline of tagged data to remote host]] |
− | |[[Image:FetchMIDoc_LoadAndTagLogic.png |thumb|400px| Download and automatic tagging of data | + | |[[Image:FetchMIDoc_LoadAndTagLogic.png |thumb|400px| Download pipeline and automatic tagging of data types]] |
|} | |} | ||
Revision as of 18:36, 4 January 2010
Home < 2010 Winter Project Week Slicer XNATKey Investigators
- Wendy Plesniak
- John Paulett
- Tim Olsen
- Dan Marcus
Objective
Exchanging data between XNAT and Slicer is currently very slow. We will identify and begin resolving bottlenecks in the current FetchMI module.
Approach, Plan
- Profile data downloads in the FetchMI module and in Slicer's RemoteIO pipeline.
- Walk through the FetchMI code to see how the XNAT API is being utilized. Optimize.
- Determine ways to optimize Slicer's RemoteIO pipeline.
Progress
Progress will be rapid, possibly ferocious.