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 #10366 (closed)

Opened 6 years ago

Closed 6 years ago

Consider saving WND-CHRM classifier instead of generating on the fly

Reported by: spli Owned by: spli
Priority: minor Milestone: OMERO-4.4.7
Component: General Version: n.a.
Keywords: n.a. Cc: analysis@…
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: 2013-03-12 (6))

Description

The WND-CHRM classifier has slightly complex storage requirements as it uses nearest neighbour, so all training samples must be stored. At present the classifier is re-trained from the saved features everytime a set of predictions are made, maybe it would be better to separate the training and prediction stages, and either store the classifier state in OMERO.tables or (easier) jsut dump it to a Python pickle file saved as an OriginalFile?.

Change History (3)

comment:1 Changed 6 years ago by jburel

  • Sprint changed from 2013-02-12 (5) to 2013-03-12 (6))

Referencing ticket #10230 has changed sprint.

comment:2 Changed 6 years ago by spli

See parent story #10230

comment:3 Changed 6 years ago by spli

  • Resolution set to fixed
  • Status changed from new 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.79985 sec.)

We're Hiring!