Fix available releases for v2 coverage and liftover #352
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.
A few issues fixed here:
Coverage was not recalculated for v2.1.1. That was accounted for in exome resources, but not genome.
Similar to 1, there was no liftover dataset created for v2.1. That was accounted for in exome resources, but not genome.
Using
removeto exclude those versions from coverage/liftover resources modified the constantEXOME_RELEASES. Thus, after accessing exome coverage resources, v2.1.1 was not available for any other resource that used that constant. For example:currently throws
KeyError: 'default_version 2.1.1 not found in versions dictionary passed to VersionedTableResource.'This changes the
coverageandliftoverfunctions to create new lists of versions instead of modifying constants.