IMViewer: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
(5 intermediate revisions by the same user not shown) | |||
Line 5: | Line 5: | ||
= Browser based user initiated large scale image processing = | = Browser based user initiated large scale image processing = | ||
== | == Viewer interaction == | ||
* After user submits the request the request itself is stored in database (so next visitor may see what has been | * Browser based user interaction allows following selections using large image viewer | ||
*# Sub-region at desired resolution (maybe with more general shapes) | |||
*# Process to be performed on the image and its parameters | |||
*# The Tag and way to store results | |||
*# Time of execution | |||
* After user submits the request the request itself is stored in database (so next visitor may see what processing has been configured) | |||
* The results (metadata and the image chunks at multiple resolutions | * The results (metadata and the result image-chunks at multiple resolutions | ||
* | *# Stored as another document in the MongoDB | ||
*# Can be viewed along with the base image | |||
*# Can be shared / reviewed by another user | |||
== Server administration == | |||
* Maintain a list of possible applications (algorithms) that can be invoked, | |||
*# Inputs they accept | |||
*# Error handling and reporting | |||
*# Estimate of required time and timeout | |||
*# Resources (RAM, disk space, etc) they will requirA | |||
* Batch process execution | |||
*# Monitor the progress, see the results | |||
*# Interrupt the process | |||
*## Take a look at results | |||
*## Modify the settings | |||
*# Resume / discard | |||
* Resource managements | |||
*# User priviledges | |||
*# Time scheduling | |||
* Creation of reports | |||
== Relation to Midas == | == Relation to Midas == | ||
Not sure how what is already | Not sure how what is already included in current (or current vision of) Midas, and how existing Midas infrastructure can be leveraged once large image viewer is integrated in Midas. | ||
# Making Midas a processing powerhouse | # Making Midas a processing powerhouse | ||
== Some use cases == | == Some use cases == |
Latest revision as of 21:14, 2 March 2011
[category:IMViewer]
Browser based user initiated large scale image processing
Viewer interaction
- Browser based user interaction allows following selections using large image viewer
- Sub-region at desired resolution (maybe with more general shapes)
- Process to be performed on the image and its parameters
- The Tag and way to store results
- Time of execution
- After user submits the request the request itself is stored in database (so next visitor may see what processing has been configured)
- The results (metadata and the result image-chunks at multiple resolutions
- Stored as another document in the MongoDB
- Can be viewed along with the base image
- Can be shared / reviewed by another user
Server administration
- Maintain a list of possible applications (algorithms) that can be invoked,
- Inputs they accept
- Error handling and reporting
- Estimate of required time and timeout
- Resources (RAM, disk space, etc) they will requirA
- Batch process execution
- Monitor the progress, see the results
- Interrupt the process
- Take a look at results
- Modify the settings
- Resume / discard
- Resource managements
- User priviledges
- Time scheduling
- Creation of reports
Relation to Midas
Not sure how what is already included in current (or current vision of) Midas, and how existing Midas infrastructure can be leveraged once large image viewer is integrated in Midas.
- Making Midas a processing powerhouse
Some use cases
- Crowd sourcing of manual (seed based) segmentation and neuron tracking process (similar to Zooniverse).
- Manual marking for training data (e.g. cell membrane, mitochondria ..)
- Remote invocation of anything more involving