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"

Task #10570 (closed)

Opened 11 years ago

Closed 9 years ago

Define a classifier XMLAnnotation format

Reported by: spli Owned by: spli
Priority: major Milestone: Partner
Component: API Version: 4.4.9
Keywords: analysis Cc: analysis@…
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: 0.0d
Sprint: n.a.

Description

Define an XMLAnnotation format, as used for example with the multi-dimensional Modulo work
http://www.openmicroscopy.org/site/support/file-formats/working-with-ome-xml/6d-7d-and-8d-storage

This will probably have two main requirements.

Storage of trained classifier instances

Store classifier parameters and trained state:
For example, in
https://github.com/manics/omero-pychrm/tree/20130228-pi_dev_demo
PyCHRM classifiers are stored in the form of three tables which are attached to the project containing the training data:

  • Feature weights
  • Class labels/indexes
  • Selected features values (nearest neighbour means the values of the selected original features are required, along with the original class label).

In addition we should probably store the classifier parameters, and possibly some sort of versioning information.

Storage of classifier results

Store classifier predictions, possibly multiple per image/object. In https://github.com/manics/omero-pychrm/tree/20130228-pi_dev_demo the idea of tagsets containing the labels associated with a classifier instance was used (#10367).

We could use an XMLAnnotation to store the final predictions from running a classifier instance, for instance by listing image IDs instead of tagging them. This gives us more flexibility than using tagsets which are limited to a single level, and which are defined by a namespace so it's not possible to also have a classifier namespace. It is also extensible to classifiers which have parameters controlling the prediction as well as the training, since these additional parameters can be easily recorded.

Change History (6)

comment:1 Changed 11 years ago by spli

  • Cc analysis@… added
  • Keywords analysis added
  • Milestone changed from Unscheduled to OMERO-4.5
  • Sprint set to 2013-04-09 (7))
  • Status changed from new to accepted

Initial draft for the classifier XMLAnnotation here:
https://gist.github.com/manics/5238573

comment:2 Changed 11 years ago by jamoore

a5d34ad53b1b23de9c629887769c1dc0305f4746 (second revision) certainly looks very easy to read. Will be interesting to see how difficult this will be for you to work with.

comment:3 Changed 11 years ago by jburel

  • Sprint changed from 2013-04-09 (7)) to 2013-05-07 (8)

Moved from sprint 2013-04-09 (7))

comment:4 Changed 11 years ago by jburel

  • Milestone changed from OMERO-4.4.x to OMERO-4.4.9
  • Sprint changed from 2013-05-07 (8) to Blocker 4.4.9 (1)

Moved from sprint 2013-05-07 (8)

comment:5 Changed 10 years ago by spli

  • Milestone changed from OMERO-4.4.x to Partner
  • Version set to 4.4.9

comment:6 Changed 9 years ago by spli

  • Remaining Time changed from 1 to 0
  • Resolution set to wontfix
  • Status changed from accepted to closed
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.81377 sec.)

We're Hiring!