Skip to content

Tuning error conditions #455

@ericbuckley

Description

@ericbuckley

Summary

Verify that for each of the conditions described below, that would cause tuning to fail, the appropriate errors are caught, logged and reported to the tuning_job.details column.

Details / Tasks

  1. The database is empty (user forgets to seed their database before tuning)
  2. Not enough samples (there are not enough database rows to sample from)
  3. Not enough pairs (there is not enough data to create X true match pairs or Y non match pairs)
  4. No default algorithm (could be an error, but should probably just skip over RMS calculations and report in the details)
  5. Too low match pairs (the true match pairs / non match pairs config value is too low)
  6. Too low sample size (the sample size config value is too low)
  7. Sample size smaller than match pair (the sample size config value is too low to effectively create N non-match pairs)

Metadata

Metadata

Assignees

Labels

featureqaTechnical improvements to increase code quality
No fields configured for Feature.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions