Difference between revisions of "Slicer3:Remote Data Handling"
From NAMIC Wiki
| Line 13: | Line 13: | ||
For loading remote datasets, we have options for breaking these two steps apart explicitly, or binding them together under the hood. | For loading remote datasets, we have options for breaking these two steps apart explicitly, or binding them together under the hood. | ||
| − | + | ====Breaking apart find data and load data:==== | |
'''Possible workflow A''' | '''Possible workflow A''' | ||
| Line 23: | Line 23: | ||
* 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 Download Manager, and loaded directly into Slicer via a vtkMRMLStorageNode method when download is complete. | * 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 Download Manager, and loaded directly into Slicer via a vtkMRMLStorageNode method when download is complete. | ||
| − | ''' | + | '''Possible workflow C''' |
| + | * User locates a MRML file, .xcat archive, or individual dataset on the HID or an XNAT web interface | ||
| + | * User types the uri into the ''Load Scene'', ''Import Scene'', or ''Add Data'' interfaces. | ||
| + | * If no locally cached versions exist, each remote file in the archive is cached to /tmp by the Download Manager, and loaded directly into Slicer via a vtkMRMLStorageNode method when download is complete. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | ====Bundling together find data and load data:==== | ||
'''Possible workflow 2''' | '''Possible workflow 2''' | ||
Revision as of 21:47, 30 January 2008
Home < Slicer3:Remote Data HandlingContents
Remote I/O for Slicer3
ITK-based mechanism handling remote data (for command line modules, batch processing, and grid processing)
vtkMRMLStorageNode methods for handling remote data (for loading and saving data for interactive use)
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.
For loading remote datasets, we have options for breaking these two steps apart explicitly, or binding them together under the hood.
Breaking apart find data and load data:
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 Download Manager, and then loaded into Slicer via a 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 Download Manager, and loaded directly into Slicer via a vtkMRMLStorageNode method when download is complete.
Possible workflow C
- User locates a MRML file, .xcat archive, or individual dataset on the HID or an XNAT web interface
- User types the uri into the Load Scene, Import Scene, or Add Data interfaces.
- If no locally cached versions exist, each remote file in the archive is cached to /tmp by the Download Manager, and loaded directly into Slicer via a vtkMRMLStorageNode method when download is complete.
Bundling together find data and load data:
Possible workflow 2
- From a 'revised' Add Data interface, user performs remote HID query for available data
