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"

User Story #9950 (new)

Opened 11 years ago

Last modified 11 years ago

Analysis: Context handling for predictors

Reported by: spli Owned by: spli
Priority: critical Milestone: Unscheduled
Component: General Keywords: analysis
Cc: analysis@… Story Points: n.a.
Sprint: n.a. Importance: n.a.
Total Remaining Time: n.a. Estimated Remaining Time: n.a.

Description (last modified by spli)

Some analysis algorithms may be applicable to all iamges and datasets. Others are designed to work on either a particular type of image, or require careful selection of a training dataset for optimal performance.

This means we need to store and manage the context of each classifier/predictor. A single algorithm may have multiple contexts, which will may include:

  • List of the training images which defines the context.
  • Feature weights, which indicate which features were used for the training process (this may be a subset of the complete set), and weights for each of these features.
  • Additional parameters which are automatically determined during training.
  • Performance information during training. Some of these fields are common between classifiers (e.g. continuous: MSE, Pearman/Spearman? coefficients/p-values, discrete: error rates, confusion matrix), some will be algorithm specific.
  • Individual image predictions. Useful for checking performance, comparing classifiers, or to look for outliers.
  • Also additional image specific prediction data such as confidence measures.
  • Test set predictions. This may or may not be the same as the training set.
  • Cross-validation performance during training. Particularly useful if the classifier is directly used to generate results for publication.
  • Externally defined algorithm specific parameters.

We'd also like a way of characterising the contexts to reduce the complexity faced by a user when selecting which algorithm/context. For example, if an algorithm is designed for colour images there is no point in trying it on greyscale images.

Change History (2)

comment:1 Changed 11 years ago by spli

  • Description modified (diff)

comment:2 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.66861 sec.)

We're Hiring!