Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Requirement #9942 (new)

Opened 11 years ago

Last modified 11 years ago

Server Analysis API

Reported by: spli Owned by: spli
Priority: critical Milestone: GatherReqs
Component: API Keywords: analysis
Cc: analysis@… Business Value: n.a.
Total Story Points: n.a. Roif: n.a.
Mandatory Story Points: n.a.

Description (last modified by spli)


Create an API so that external analysis algorithms can be integrated with OMERO.


There is a scripting API but it is designed for relatively small jobs. This requirement is for an API to handle large computationally intensive jobs over many images and datasets.


This is intended to cover the backend components such as running jobs and handling storage of intermediate and final results.

There will be some user-interface development to visualise results, but any major visualisation work should probably form a separate requirement.

OMERO.searcher and WND-CHRM will be used to develop and evaluate the API, and will also form reference implementations/examples.


The general workflow from a user's point of view is as follows:

  1. Preprocess images #9947
  2. Calculate image features, store them #9948
  3. Train an algorithm to understand images #9949
  4. Use the trained algorithm to make predictions or search images #9951
  5. View the results #9952

Depending on the algorithm some of these steps will be transparent to a user. For example, a general search application such as OMERO.searcher may continuously run in the background, automatically calculating features and updating its knowledge, so a user would only be exposed to the search interface.

A data-exploration tool might effectively build any machine learning into the visualisation stage for real-time exploration. This means only the feature extraction and visualisation steps are required.

The context of a learning algorithm (#9950) will require some thought to make it usable by non-specialists.

See also

  • #7902 Message queue support, this would be useful for resource-intensive calculations on large datasets where a cluster is available.
  • #1856 Scripting improvements.

Change History (3)

comment:1 Changed 11 years ago by spli

  • Component changed from General to API
  • Description modified (diff)
  • Keywords analysis added

comment:2 Changed 11 years ago by spli

  • Description modified (diff)

comment:3 Changed 11 years ago by spli

  • Description modified (diff)
Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.41380 sec.)

We're Hiring!