IMViewer: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
(Created page with " == Browser based user initiated processing pipeline == * User selects following using large image viewer (like the one above) ** a region at desired resolution ** The proce...") |
|||
| Line 1: | Line 1: | ||
[category:IMViewer] | |||
= Browser based user initiated large scale image processing = | |||
== User interaction == | |||
* User selects following using large image viewer (like the one above) | * User selects following using large image viewer (like the one above) | ||
** a region at desired resolution | ** a region at desired resolution | ||
| Line 12: | Line 15: | ||
** Stored as another document in the MongoDB | ** Stored as another document in the MongoDB | ||
== Server administration == | |||
# Maintaining a list of processes (algorithms) that can be invoked, and what inputs they accept | |||
## Error handling and reporting | |||
## Timeouts | |||
== Relation to Midas == | |||
Not sure how what is already available in included in current (or current vision of) Midas, and much similar functionality is in Midas currently or after integrating large image viewer. | |||
# Making Midas a processing powerhouse | |||
, or if not | , or if not | ||
running server side processes on the selected regions | running server side processes on the selected regions | ||
== 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 | |||
Revision as of 22:04, 23 February 2011
[category:IMViewer]
Browser based user initiated large scale image processing
User interaction
- User selects following using large image viewer (like the one above)
- a region at desired resolution
- The process and the parameters to run
- After user submits the request the request itself is stored in database (so next visitor may see what has been processed already)
- The results (metadata and the image chunks at multiple resolutions
- Stored as another document in the MongoDB
Server administration
- Maintaining a list of processes (algorithms) that can be invoked, and what inputs they accept
- Error handling and reporting
- Timeouts
Relation to Midas
Not sure how what is already available in included in current (or current vision of) Midas, and much similar functionality is in Midas currently or after integrating large image viewer.
- Making Midas a processing powerhouse
, or if not running server side processes on the selected regions
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
