Skip to content
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

Look into using vrs-python for VCF translation #231

Open
korikuzma opened this issue Feb 1, 2022 · 1 comment
Open

Look into using vrs-python for VCF translation #231

korikuzma opened this issue Feb 1, 2022 · 1 comment
Assignees
Labels
priority:high High priority technical debt A feature/requirement implemented in a sub-optimal way & must be re-written. Contrast to "cleanup"

Comments

@korikuzma
Copy link
Member

I initially did not use _from_gnomad from vrs-python's translator since we tokenize, classify, validate, then translate for toVRS and normalize. I'm wondering if for VAI (+ possible performance purposes), we should use this method to go straight to the VRS object. We could do this in a separate endpoint or refactor the current structure.

@korikuzma korikuzma self-assigned this Feb 1, 2022
@korikuzma korikuzma added priority:high High priority technical debt A feature/requirement implemented in a sub-optimal way & must be re-written. Contrast to "cleanup" labels Dec 22, 2022
Copy link

github-actions bot commented Jan 6, 2025

This issue is stale because it has been open 90 days with no activity. This issue will be closed if no further activity occurs in 14 days.

@github-actions github-actions bot added the stale label Jan 6, 2025
@korikuzma korikuzma removed the stale label Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority:high High priority technical debt A feature/requirement implemented in a sub-optimal way & must be re-written. Contrast to "cleanup"
Projects
None yet
Development

No branches or pull requests

1 participant