Difference between revisions of "Slicer3:Remote Data Handling"

From NAMIC Wiki
Jump to: navigation, search
Line 61: Line 61:
 
[[image:XNATSlicer.png]]
 
[[image:XNATSlicer.png]]
  
==Questions:==
+
* when we upload a file, can we get back a URI that includes ticket information? (we can use this to write a MRML file)
 
+
* can XNAT-generated uris end with the filename.extension, so that firefox will know to save them to disk, rather than to interpret them as html?
(Steve) Essentially the process I want to be able to do is:
 
 
 
- query xnat using tags and get back xcat
 
 
 
- have xcat include subject id which can be used to request more subject details
 
 
 
- set/tag a tag on a subject / project / session / scan / reconstruction...
 
 
 
- construct a valid xar for StoreXAR that the right IDs to put it in Additional Resources section of a Session for future download.
 
 
 
 
 
(Wendy) From the Slicer application, I'd like to make sure it's as simple as
 
possible to load data from an xnat db, and to save it back,
 
somehow annotated with whatever was done to it during the Slicer session.
 
There may be multiple ways we want to download/upload data but I think a common workflow
 
is below:
 
 
 
'''Download'''
 
 
 
I think we're assuming that users will commonly download a .xcat file
 
from an xnat host's web interface to local disk. That file will be parsed
 
by Slicer  and all remote references will be downloaded and opened
 
by the app.
 
 
 
* My understanding is that the .xcat file will contain a uri value that http curl can get, and satisfactory
 
'ticket' information,  -- if that's so, we're good for remote loading. '''??''' I go to central.xnat.org, look at OAS1_0019_MR1, and then
 
** choose "MR sessions"
 
** choose "download images"
 
** Select "catalog XML"
 
** check only the scans and uncheck the rest, then download.
 
** Look at the uris in the downloaded file: URI="http://central.xnat.org/archive/cache/Sot7eKn29AJP4U7dO1oNOde44SRZJSeRnjItTaDZgkjltRVrIbj5Q9vRpuQBSUp5"
 
** Is this something that http/curl can handle, which contains the ticket information?
 
* If the uri value has invalid ticket information, I think we may want to
 
prompt for username, password, xnat host, apply for new (or reactivate
 
old) ticket string, and re-create the uri. It would be good to have a
 
prescription for how to do this.
 
* (We may want richer metadata in the .xcat file for the sake of data provenance, and Nicole may have more specific suggestions on this topic.)
 
 
 
'''Upload'''
 
 
 
I'm guessing we'll commonly use Slicer's save data widget to save the scene or selected datasets. If a dataset came from an xnat db, as a first pass, we'll want to store the data back by default. We'll need to:
 
 
 
* mark up data using XCEDE schema (do we know how?),
 
* we'll need to write new tags to track provenance (our own tags?),
 
* change names of files to avoid overwriting originals (is there a favored strategy?)
 
* use StoreXAR to put things back -- to the same directory, but with new version name?
 
 
 
'''Other'''
 
 
 
* If the xcat file were to reference local datasets (on disk), what would the uri look like? (file://C:/cygwin/home/wjp/file.nii) and what would cachepath and relative path look like?
 
  
 
= Implementation: new classes =
 
= Implementation: new classes =

Revision as of 14:42, 8 May 2008

Home < Slicer3:Remote Data Handling

Back to Slicer3 Projects List


Presentations, Uses Cases and Pseudo Code

Slicer's original (local) data handling schematic

Originally, MRML files, XCEDE catalog files, XNAT archives and individual datasets were only loadable from local disk, and remote datasets were downloaded (via web interface or command line) outside of Slicer. In the BIRN 2007 AHM we demonstrated downloading .xar files from a remote database, and loading .xar and .xcat files into Slicer from local disk using Slicer's XNAT archive reader and XCEDE2.0 catalog reader. This original scheme for data handling is shown below:

DataLoadingCurrent.png

Goal for how Slicer would upload/download from remote data stores

Eventually, we would like to query web services, download data remotely or locally from the Application itself, and have the option of uplaoding to remote stores as well. A sketch of the architecture planned in a meeting (on 2/14/08 with Steve Pieper, Nicole Aucoin and Wendy Plesniak) is shown below, including:

  • a collection of vtkURIHandlers,
  • an (asynchronous) Data I/O Manager and
  • a Cache manager,

all created by the main application and pointed to by the MRMLScene.:

DataLoadingTarget.png

Two general use cases used to drive a first pass implementation

  • First, is loading a combined FIPS/FreeSurfer analysis, specified in an Xcede catalog (.xcat) file that contains uris pointing to remote datasets, and view this with Slicer's QueryAtlas. (Prior to fBIRN AHM in 2008, it was not possible to get an .xcat via the HID web GUI; our approach was to manually upload a test Xcede catalog file and its constituent datasets to SRB. A copy of the .xcat file was kept locally, and SRB was accessed for each uri listed in it.)
  • Second, is running a batch job in Slicer that processes a set of remotely held datasets. Each iteration would take as arguments the XML file parameterizing the EMSegmenter, the uri for the remote dataset, and a uri for storing back the segmentation results. This use case has not yet been implemented.

The schematic of the functionality we'll need is shown below:

DataLoadingStartPlan.png

Current MRML, Logic and GUI Components

Slicer's Remote data handling architecture has been implemented to support remote download and upload of uris. Its components include a Cache Manager, a Data I/O Manager, and a URI Handler Collection in MRML; a Data I/O Manager Logic that engages the Application Logic's queueing and multi-threading mechanisms; and a Cache and Data I/O Manager GUI to provide feedback, information and control on the desktop. These components can also be configured through the Application Settings Interface, and these user preferences are saved in the Application Registry. Schematic and screenshots are shown below:

RemoteIO.png


S3CacheAndRemoteIOSettings.png

S3CacheAndRemoteIOGUI.png


Test-case URIs:

XNAT questions

XNATSlicer.png

  • when we upload a file, can we get back a URI that includes ticket information? (we can use this to write a MRML file)
  • can XNAT-generated uris end with the filename.extension, so that firefox will know to save them to disk, rather than to interpret them as html?

Implementation: new classes

MRML extensions

MRML-specific implementations and extensions of the following classes:

  • vtkDataIOManager
  • vtkMRMLStorageNode methods
  • vtkMRML<DataType>StorageNode methods
  • vtkPasswordPrompter
  • vtkDataTransfer
  • vtkCacheManager
  • vtkURIHandler

GUI extensions

GUI implementations of the following classes:

  • vtkSlicerDataTransferWidget
  • vtkSlicerCacheAndDataIOManagerGUI
  • vtkSlicerPasswordPrompter

Logic extensions

  • vtkDataIOManagerLogic

Application Interface extensions

  • Set CacheDirectory default = Slicer3 temp dir
  • Set CacheFreeBufferSize default = 10Mb
  • Set CacheLimit default = 20Mb
  • Enable/Disable CacheOverwriting default = true
  • Enable/Disable ForceRedownload default = false
  • Enable/Disable asynchronous I/O default = false
  • Instance & Register URI Handlers (?)

Important Notes

  • MRML Scene file reading will always be synchronous.
  • Read/write of individual datasets referenced in the scene should work with or without the asynchronous read/write turned on, and with or without the dataIOManager GUI interface.





ITK-based mechanism handling remote data (for command line modules, batch processing, and grid processing) (Nicole)

This one is tenatively on hold for now.

Workflows to support

The first goal is to figure out what workflows to support, and a good implementation approach.

Currently, Load Scene, Import Scene, and Add Data options in Slicer all encapsulate two steps:

  • locating a dataset, usually accomplished through a file browser, and
  • selecting a dataset to initiate loading.

Then MRML files, Xcede catalog files, or individual datasets are loaded from local disk.

For loading remote datasets, the following options are available:

  • break these two steps apart explicitly (easiest option),
  • bind them together under the hood,
  • or support both of these paradigms.

For now, we choose the first option.

workflows:

Possible workflow A

  • User downloads .xcat or .xml (MRML) file to disk using the HID or an XNAT web interface
  • From the Load Scene file browser, user selects the .xcat or .xml archive. If no locally cached versions exist, each remote file listed in the archive is downloaded to /tmp directory (always locally cached) by the Data I/O Manager, and then cached (local) uri is passed to vtkMRMLStorageNode method when download is complete.

Possible workflow B

  • User downloads .xcat or .xml (MRML) file to disk using the HID or an XNAT web interface
  • From the Load Scene file browser, user selects the .xcat or .xml archive. If no locally cached versions exist, each remote file in the archive is downloaded to /tmp (only if a flag is set) by the Data IO Manager, and loaded directly into Slicer via a vtkMRMLStorageNode method when download is complete. (How does load work if we don't save to disk first?)

Workflow C

  • describe batch processing example here, which includes saving to local or remote.

In each workflow, the data gets saved to disk first and then loaded into StorageNode or uploaded to remote location from cache.

What data do we need in an .xcat file?

For the fBIRN QueryAtlas use case, we need a combination of FreeSurfer morphology analysis and a FIPS analysis of the same subject. With the combined data in Slicer, we can view activation overlays co-registered to and overlayed onto the high resolution structural MRI using the FIPS analysis, and determine the names of brain regions where activations occur using the co-registered morphology analysis.

The required analyses including all derived data are in two standard directory structures on local disk, and *hopefully* somewhere on the HID within a standard structure (check with Burak). These directory trees contain a LOT of files we don't need... Below are the files we *do* need for fBIRN QueryAtlas use case.

FIPS analysis (.feat) directory and required data

For instance, the FIPS output directory in our example dataset from Doug Greve at MGH is called sirp-hp65-stc-to7-gam.feat. Under this directory, QueryAtlas needs the following datasets:

  • sirp-hp65-stc-to7-gam.feat/reg/example_func.nii
  • sirp-hp65-stc-to7-gam.feat/reg/freesurfer/anat2exf.register.dat
  • sirp-hp65-stc-to7-gam.feat/stats/(all statistics files of interest)
  • sirp-hp65-stc-to7-gam.feat/design.gif (this image relates statistics files to experimental conditions)

FreeSurfer analysis directory, and required data

For instance, the FreeSurfer morphology analysis directory in our example dataset from Doug Greve at MGH is called fbph2-000670986943. Under this directory, QueryAtlas needs the following datasets:

  • fbph2-000670986943/mri/brain.mgz
  • fbph2-000670986943/mri/aparc+aseg.mgz
  • fbph2-000670986943/surf/lh.pial
  • fbph2-000670986943/surf/rh.pial
  • fbph2-000670986943/label/lh.aparc.annot
  • fbph2-000670986943/label/rh.aparc.annot

What do we want HID webservices to provide?

  • Question: are FIPS and FreeSurfer analyses (including QueryAtlas required files listed above) for subjects available on the HID yet? --Burak says not yet.
  • Given that, can we manually upload an example .xcat and the datasets it points to the SRB, and download each dataset from the HID in Slicer, using some helper application (like curl)?
  • (Eventually.) The BIRN HID webservices shouldn't really need to know the subset of data that QueryAtlas needs... maybe the web interface can take a BIRN ID and create a FIPS/FreeSurfer xcede catalog with all uris (http://....) in the FIPS and FreeSurfer directories, and package these into an Xcede catalog.
  • (Eventually.) The catalog could be requested and downloaded from the HID web GUI, with a name like .xcat or .xcat.gzip or whatever. QueryAtlas could then open this file (or unzip and open) and filter for the relevant uris for an fBIRN or Qdec QueryAtlas session.


  • Then, for each uri in a catalog (or .xml MRML file), we'll use (curl?) to download; so we need all datasets to be publicly readable.
  • Can we create a directory (even a temporary one) on the SRB/BWH HID for Slicer data uploads?
  • We need some kind of upload service, a function call that takes a dataset and a BIRNID and uploads data to appropriate remote directory.

For more info, see this page for more discussion of QueryAtlas's current use of Xcede catalogs, and assumptions...

Slicer's Data I/O Manager

DataIOManager.png