-
Notifications
You must be signed in to change notification settings - Fork 27
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
Normalization extensions for VRS 2.x #334
Comments
Preferential RLE representation checks out: tested in #336 |
I went digging into the VRS-python code last weekend, and reviewed the comments in #338. Now that we have a model that includes the notion of Starting a discussion thread in VRS (ga4gh/vrs#465) to address this. |
* add normalization example to test notebook * update notebook metadata * a few simple behavior tests * Add keys to ReferenceLengthExpression and LiteralSequenceExpression * Make LiteralSequenceExpression not-identifiable * remove unnecessary / unused code * addresses #338 (comment) * Fix ReferenceLengthExpression tests in test_allele_translator * linewise diff for test_annotate_vcf_grch38_noattrs * Update test_vcf_expected_output_no_vrs_attrs.vcf.gz ReferenceLengthExpression * Fix test_annotate_vcf_grch38_attrs * Fix test_annotate_vcf_grch38_attrs_altsonly --------- Co-authored-by: Kyle Ferriter <kferrite@broadinstitute.org>
As VRS grows to encompass more complex use cases, additional normalization constraints need to be imposed to promote consistency in computed identifiers. In VRS 1.x the primary normalization concern was correcting ambiguous sequence insertions/deletions in repeating regions. However, in 2.x we have additional concerns:
We should implement these additional normalization rules in VRS-Python.
The text was updated successfully, but these errors were encountered: