OMERO is client-server software for visualization, management and analysis of biological microscope images.
Interacting with OMERO from ImageJ
There are several different ImageJ-based tools for working with data from an OMERO database:
OMERO plugin for Fiji/ImageJ
The OME project has developed the OMERO plugin for Fiji/ImageJ. Read about it at:
For versions of OMERO prior to 5.5, OME’s plugin for ImageJ was known as OMERO.insight-ij.
The ImageJ2 team has developed ImageJ-OMERO, a SciJava-based library for bidirectional interoperability between ImageJ2 and OMERO, with plugins to upload and download images, tables, and regions of interest to and from OMERO, and support for running ImageJ scripts on the OMERO server side.
ImageJ-OMERO is accessed via a collection of
OMERO x.x update sites specific to the OMERO server version you are connecting to.
- omero_batch-plugin: a plugin to batch process images from OMERO with a script or macro
- omero_macro-extensions: a plugin to interface with OMERO directly from macros through macro-extensions
- simple-omero-client: a wrapper library which can be called from scripts in Fiji, but can mostly be used in Maven projects to wrap calls to the underlying OMERO Java Gateway (API available here)
The omero_batch-plugin plugin gives users a GUI to help them process images from OMERO or a local folder (with bio-formats) with a script of their choosing, and save results locally or on OMERO.
The omero_macro-extensions plugin adds new macro functions to access data on OMERO directly from macros. For example:
run("OMERO Extensions"); Ext.connectToOMERO(host, port, username, password); images = Ext.list("images", "dataset", dataset_id); image_ids = split(images,","); imageplusID = Ext.getImage(image_ids);
The simple-omero-client is a Maven library, on which the omero_batch-plugin and omero_macro-extensions are built. It is therefore required to run these. However, once installed in Fiji, its API then becomes available for modern scripts.
Instructions for the plugins installation are on their respective release page, and their READMEs should describe how to use them, although this could be improved.
See the publication preprint for further details.