Difference between revisions of "2013 Project Week:Slicer Personal Cloud"
(Created page with '__NOTOC__ <gallery> Image:PW-MIT2013.png|Projects List Image:SlicerPersonalCloudOverview.png|Interaction: Overview Image:SlicerPersonalCl…') |
|||
(One intermediate revision by the same user not shown) | |||
Line 4: | Line 4: | ||
Image:SlicerPersonalCloudOverview.png|Interaction: Overview | Image:SlicerPersonalCloudOverview.png|Interaction: Overview | ||
Image:SlicerPersonalCloudConfigure.png|Interaction: Configure | Image:SlicerPersonalCloudConfigure.png|Interaction: Configure | ||
− | Image: | + | Image:SlicerPersonalCloudApply.png|Interaction: Submit a job to the cloud |
Image:SlicerPersonalCloudDownloadandQuery.png|Interaction: Download results and query for job status (work in progress) | Image:SlicerPersonalCloudDownloadandQuery.png|Interaction: Download results and query for job status (work in progress) | ||
</gallery> | </gallery> | ||
Line 11: | Line 11: | ||
* GRC: Rui Li, Jim Miller | * GRC: Rui Li, Jim Miller | ||
* Isomics: Steve Pieper | * Isomics: Steve Pieper | ||
− | |||
<div style="margin: 20px;"> | <div style="margin: 20px;"> |
Latest revision as of 18:02, 7 January 2013
Home < 2013 Project Week:Slicer Personal CloudKey Investigators
- GRC: Rui Li, Jim Miller
- Isomics: Steve Pieper
Objective
Enable Slicer users to schedule long running analyses on their server machine from their client machine. The results will be available for downloading on the client machine when it is ready. One use case would be to set up a module on your laptop, submit to your Personal Slicer Cloud, pack up your laptop for the drive home, and upon arriving at your destination open your laptop to download and review the results computed while you were in transit.
Approach, Plan
Our approach for developing the Slicer personal cloud is that the users will interact with the module on the client side as they would normally do. Instead of running the module locally, the data and parameters are packaged and send over to the cloud server via one mouse click. The current implementation using python packages to manage client and server communication. On the server side, once the request is received, the submitted job is run as a command line module by executing ``Slicer --launch commandString".
Progress
We have implemented the basic pipeline of submitting a job, run the job on the cloud server and downloading the results.
Delivery Mechanism
This work will be delivered to the NA-MIC Kit as a (please select the appropriate options by noting YES against them below)
- ITK Module
- Slicer Module
- Built-in
- Extension -- commandline
- Extension -- loadable
- Other (Please specify) YES