Postgres #187
Merged
Postgres #187
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…es automatically on container launch
…le name, added usage instructions.
woa_normbias can't handle pre-1900 profiles because it uses datetime.datetime.strftime which fails if given a date before 1900. Profiles from before 1900 are set to have year=1900. This should not have an impact on QC results but will prevent an error.
…check Update cotede_test.py to handle pre-1900 profiles
…, in case of connection loss
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These changes migrate AutoQC to read and write data to and from a postgres database, per @castelao's suggestion some time ago. QC results are consistent with
masterover 2000 profiles, up to some well-understood and resolved bugs in en_track (see #179 for details), and over 1000 profiles for the cotede suite (#184 was in the way of the second block of 1000 for those qc tests).Key differences in usage and qc test writing are all detailed in the top-level README; briefly, running is now in three steps (db creation, qc running, and result summarization), and qc test signature is now
test(p, parameters), where the newparametersargument is a dictionary carrying static parameters for tests to recycle across profiles.