Skip to content

Dev #1050

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

Merged
merged 26 commits into from
Mar 6, 2025
Merged

Dev #1050

merged 26 commits into from
Mar 6, 2025

Conversation

jklugherz
Copy link
Contributor

No description provided.

@jklugherz jklugherz requested a review from a team as a code owner February 26, 2025 20:29
@jklugherz jklugherz requested a review from hanars March 3, 2025 18:34
ht = ht.annotate(gnomad_svs=sv.gnomad_svs(ht, gnomad_svs_ht))
ht = ht.drop('info.GNOMAD_V4.1_TRUTH_VID')
return ht.annotate_globals(
versions=ht.globals.versions.annotate(gnomad_svs='1.0'),
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wouldn't this already be the version- shouldn't we bump it?

Copy link
Contributor Author

@jklugherz jklugherz Mar 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this migration will create the gnomad_svs table, but you're right, the globals annotation happens when we call ReferenceDataset.gnomad.get_ht so we don't need to set the version/enums here.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oooh, there's some confusing bits here.

ReferenceDataset.gnomad_svs.get_ht sets the globals on the gnomad_svs reference dataset (gs://seqr-reference-data/v3.1/GRCh38/gnomad_svs/1.0.ht if persisted). This code was setting the globals on the SV annotations table as they're not currently there. It's not overwhelmingly important, as we exclude gnomad_svs from consideration when computing the reference datasets to update, and it would also be annotated by the normal process because I kept separate for_reference_genome_dataset_type_annotations (which includes gnomad_svs) and for_reference_genome_dataset_type_annotations_updates methods (which does not). I felt the migration should include the correct globals on annotations table for completeness though!

Copy link
Contributor Author

@jklugherz jklugherz Mar 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

right I got jumbled, this is an annotation table migration.

This code was setting the globals on the SV annotations table as they're not currently there

This is good reason to keep the globals annotation in this migration. @hanars, I'm going to ad the globals versions and enums annotations back and re-request review.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, it would be awesome if these had tests, but not entirely sure it would have caught this 😬.

ht = ht.drop('info.GNOMAD_V4.1_TRUTH_VID')
return ht.annotate_globals(
versions=ht.globals.versions.annotate(gnomad_svs='1.0'),
enums=ht.globals.enums.annotate(gnomad_svs=hl.Struct()),
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this feels unnecessary, as this would already be in the existing table globals and does not seem to be changing

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jklugherz jklugherz requested a review from hanars March 3, 2025 20:37
@jklugherz jklugherz requested a review from hanars March 4, 2025 17:13
@jklugherz jklugherz merged commit 9e9f2b3 into main Mar 6, 2025
5 checks passed
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

Successfully merging this pull request may close these issues.

3 participants