Skip to content

Release Hail Table format of SV and CNV data #1690

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

Closed
ch-kr opened this issue Mar 11, 2025 · 5 comments
Closed

Release Hail Table format of SV and CNV data #1690

ch-kr opened this issue Mar 11, 2025 · 5 comments
Assignees

Comments

@ch-kr
Copy link
Contributor

ch-kr commented Mar 11, 2025

We currently only release VCFs for the SV and CNV data. It would be beneficial to release the transformed Hail Tables containing these data as well, similar to the v4 browser variants HT release.

I'll reach out to the CNV/SV teams to help with documentation for this release, since we should update this page with descriptions of these new tables

@ch-kr
Copy link
Contributor Author

ch-kr commented Mar 13, 2025

Adding comment to add checklist of release steps:

  • Get documentation of fields in SV/CNV tables from Xuefang and Jack
  • Rename populations in HTs to gen_anc_grps prior to release (request for browser team to rename this field for public release)
  • Add descriptions to browser HTs help doc
  • Review/approve/merge PR adding descriptions to help doc (this is ready to be merged when closer to release)
  • Add sections and links to these HTs on downloads page
  • Stage HTs to public staging bucket once PR above is approved (will need someone from browser team to do this due to permissions)
  • Sync HTs from GCP to AWS (KC will do this)

@ch-kr
Copy link
Contributor Author

ch-kr commented Mar 19, 2025

adding a comment here to add another two items:

@ch-kr
Copy link
Contributor Author

ch-kr commented Apr 11, 2025

hey -- not urgent, but I wanted to check in on the status of this ticket. is there anything you need from me?

@phildarnowsky-broad
Copy link
Contributor

@ch-kr looking into this now

@phildarnowsky-broad
Copy link
Contributor

Per @ch-kr we're not converting the v2 SVs for now, which we may revisit if there turns out to be demand for them.

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

2 participants