User Story #1739 (new)
Opened 14 years ago
Last modified 13 years ago
EM software integrated with OMERO — at Initial Version
| Reported by: | wmoore | Owned by: | wmoore |
|---|---|---|---|
| Priority: | major | Milestone: | Unscheduled |
| Component: | General | Keywords: | n.a. |
| Cc: | Story Points: | n.a. | |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
Investigate the options for using OMERO as the image repository for single particle analysis work-flows. This is a very ambitious task to do properly, and will probably require significant help from developers of the single-particle software. Current aim is to see whether a proof of principle is possible.
Example workflows:
- http://www.wadsworth.org/spider_doc/spider/docs/techs/recon/mr.html
- http://people.chem.byu.edu/belnap/pft3dr/tutorial/tutorial.html
- http://blake.bcm.edu/emanwiki/EMAN2/Tutorials
Importantly, EMAN2 is written in Python, and SPIDER has some Python scripts (full bindings in development).
The 2 main options are (as always):
Client-side software
E.g. Have SPIDER or EMAN2 running on the client. Adapt existing scripts to access data on OMERO. Shouldn't be too hard to do with individual scripts using small numbers of images. But when many large images are required, this becomes impracticable.
Server-side software
Use the OMERO scripting service to call Python functions in SPIDER or EMAN installed on the server. Scripts will still have to convert pixel data into the correct file type (temporary data duplication), but won't have to move data over the wire.
