Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make sure database metric values are up to date #74

Open
fergusL opened this issue Feb 11, 2021 · 0 comments
Open

Make sure database metric values are up to date #74

fergusL opened this issue Feb 11, 2021 · 0 comments
Assignees

Comments

@fergusL
Copy link
Contributor

fergusL commented Feb 11, 2021

Currently the screener service will calculate metrics for any file that fails the screen_success() check. When we add a new metric, the screen_success() will also be updated to check the new metric, if an entry does not have the new metric it will fail the screen success check and have a new set of metrics calculated.

If a metric function gets updated, there needs to be a way to determine that the entries in the database contain old metric values and need to be recalculated. One way of doing this is to include the date of screening with each metric value, which will then be used somehow by screen_success to determine if the metric was calculated with the most recent version of the metric... so somehow need to record when metric functions were last updated?

@fergusL fergusL self-assigned this Feb 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant