IMViewer: Difference between revisions

From KitwarePublic
Jump to navigationJump to search
Line 18: Line 18:
== Server administration ==  
== Server administration ==  


# Maintaining a list of processes (algorithms) that can be invoked, and what inputs they accept
# Maintain a list of possible applications (algorithms) that can be invoked,  
## Inputs they accept
## Error handling and reporting  
## Error handling and reporting  
## Timeouts 
## 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
 
# Creation of reports


== Relation to Midas ==  
== Relation to Midas ==  

Revision as of 20:44, 24 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

  1. Maintain a list of possible applications (algorithms) that can be invoked,
    1. Inputs they accept
    2. Error handling and reporting
    3. Estimate of required time and timeout
    4. Resources (RAM, disk space, etc) they will requirA
  1. Batch process execution
    1. Monitor the progress, see the results
    2. Interrupt the process
      1. Take a look at results
      2. Modify the settings
      3. Resume / discard
  1. Creation of reports

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.

  1. Making Midas a processing powerhouse

, or if not running server side processes on the selected regions

Some use cases

  1. Crowd sourcing of manual (seed based) segmentation and neuron tracking process (similar to Zooniverse).
  2. Manual marking for training data (e.g. cell membrane, mitochondria ..)
  3. Remote invocation of anything more involving