Difference between revisions of "2010 Winter Project Week Slicer XNAT"
From NAMIC Wiki
(Created page with '==Key Investigators== * Wendy Plesniak * John Paulett * Tim Olsen * Dan Marcus <div style="margin: 20px;"> <div style="width: 27%; float: left; padding-right: 3%;"> <h3>Objecti…') |
|||
(5 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
+ | |||
+ | {| | ||
+ | |[[Image:FetchMIDoc_Upload.png|thumb|400px| Upload pipeline of tagged data to remote host]] | ||
+ | |[[Image:FetchMIDoc_LoadAndTagLogic.png |thumb|400px| Download pipeline and automatic tagging of data types]] | ||
+ | |} | ||
+ | |||
==Key Investigators== | ==Key Investigators== | ||
* Wendy Plesniak | * Wendy Plesniak | ||
Line 9: | Line 15: | ||
<h3>Objective</h3> | <h3>Objective</h3> | ||
− | Exchanging data between XNAT and Slicer is currently very slow. We will identify and begin resolving bottlenecks in the current FetchMI module. | + | Exchanging data between XNAT and Slicer is currently very slow. We will identify and begin resolving bottlenecks in the current FetchMI module and Remote I/O pipeline. |
</div> | </div> | ||
Line 16: | Line 22: | ||
<h3>Approach, Plan</h3> | <h3>Approach, Plan</h3> | ||
− | Walk through the FetchMI code to see how the XNAT API is being utilized. | + | * 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. | ||
</div> | </div> | ||
Line 23: | Line 31: | ||
<h3>Progress</h3> | <h3>Progress</h3> | ||
Progress will be rapid, possibly ferocious. | Progress will be rapid, possibly ferocious. | ||
+ | |||
+ | * Wendy found a bug in the upload pipeline! not yet fixed, but high priority. | ||
+ | * Instrumented the download pipeline with profiling methods to tease out where time is being spent. | ||
+ | * Reviewed with Tim and Dave -- transfer times seem appropriate. | ||
+ | * Tim and Dave reviewed Wendy's informatics code, appears that the code is appropriate. | ||
+ | * Profiling reveals that bulk of time is being spent in the Remote I/O pipeline... | ||
+ | * Discussed with Ron, Dan, Jim some ways to bypass cache in Slicer to speed up download. | ||
+ | * Profiling will continue and if necessary, we will extend the Remote I/O pipeline for improved performance. | ||
</div> | </div> | ||
</div> | </div> | ||
<div style="width: 97%; float: left;"> | <div style="width: 97%; float: left;"> | ||
+ | |||
+ | <h3> Reference material </h3> | ||
+ | [[Image:FetchMI_Arch.png]] | ||
</div> | </div> |
Latest revision as of 16:46, 8 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 and Remote I/O pipeline.
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.
- Wendy found a bug in the upload pipeline! not yet fixed, but high priority.
- Instrumented the download pipeline with profiling methods to tease out where time is being spent.
- Reviewed with Tim and Dave -- transfer times seem appropriate.
- Tim and Dave reviewed Wendy's informatics code, appears that the code is appropriate.
- Profiling reveals that bulk of time is being spent in the Remote I/O pipeline...
- Discussed with Ron, Dan, Jim some ways to bypass cache in Slicer to speed up download.
- Profiling will continue and if necessary, we will extend the Remote I/O pipeline for improved performance.