feat: redesign StudyLocusOverlap
model to include overlapping variants in struct
#384
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.
This PR includes significant modifications to the
StudyLocusOverlap
dataset schema:leftLocus
andrightLocus
information. Instead of having separate entries for each variant in overlappingStudyLocusId
pairs, the new schema represents these in a unified manner*.StudyLocusId
pair now corresponds to a single row, simplifying the overlap representation betweenleftStudyLocusId
andrightStudyLocusId
.statistics
field, that included some of the stats both left and right forleftLocus
andrightLocus
. These follow same schema and have the same content aslocus
, with the only exception that the variants in these arrays are just the overlapping ones (therefore, both arrays contain the same variants).Coloc
andEcaviar
now anticipate the grouped schemaL2GGoldStandard.filter_unique_associations
is now simpler with the grouped schema*Roughly, we have shifted from this schema:
to this one
Pending to be run ATM