Skip to content

Decisions required to reach a minimum viable product #44

Description

@dhimmel

We're nearing the point where we'll need to implement a machine learning module to execute user queries. We're looking to create a minimum viable product. We can expand functionality later, but for now let's focus on the simplest and most succinct implementation. There are several decisions to make:

  1. Classifier: which classifiers should we support? If we want to support only a single classifier for now, which one?
  2. Predictions: do we want to return probabilities, scores, or class predictions?
  3. Threshold: do we want to report performance measures that depend on a single classification threshold? Or do we want report performance that span thresholds?
  4. Testing: Do we want to use a testing partition in addition to cross-validation? If so, do we refit a model on all observations?
  5. Features Should we include covariates in addition to expression features (see What covariates should we include as features? #21)?
  6. Feature selection: Do we want to perform any feature selection?
  7. Feature extraction: Do we want to perform features extraction, such as PCA (see Integrating dimensionality reduction into the pipeline #43)?

So let's work out these choices, with a focus on simplicity.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions