-
Notifications
You must be signed in to change notification settings - Fork 0
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
fix: genomic accession mismatch when getting nearest tx junction #356
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Only focused on `UtaDatabase` for now * `alt_pos_change` was renamed to `pos_change`
Addresses part of #224 * `transcript_to_genomic_coordinates` renamed to `tx_segment_to_genomic` * `genomic_to_transcript_exon_coordinates` renamed to `genomic_to_tx_segment`
Addresses #224 * Move `get_tx_exons_genomic_coords` from `UtaDatabase` to `ExonGenomicCoordsMapper` as a private method (`_get_tx_exons_genomic_coords`)
…x_segment` Addresses #224
Addresses #224 * `genomic_to_tx_segment` will now require inter-residue coordinates to be passed
…exons_genomic_coords
addresses #224 * initial work for cleaning up exon coord data retrieval
…dsMapper`" This reverts commit d4fb059.
addresses #224 * Use `ExonGenomicCoordsMapper._get_all_exon_coords` instead
* include `ord` in `get_alt_ac_start_or_end` response. This represents the exon number (0-based)
* include include `ord` in `UtaDatabase.get_tx_exon_aln_v_data` response. This represents the exon number (0-based)
jarbesfeld
approved these changes
Aug 20, 2024
jsstevenson
requested changes
Aug 20, 2024
Co-authored-by: James Stevenson <james.stevenson@nationwidechildrens.org>
jsstevenson
reviewed
Aug 20, 2024
jsstevenson
reviewed
Aug 20, 2024
jsstevenson
requested changes
Aug 20, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one small change request
Made some changes. I reverted back to tuple since it's lightweight. Named tuple / pydantic model seemed a little extra. I can change back if you disagree |
jsstevenson
approved these changes
Aug 21, 2024
korikuzma
added a commit
that referenced
this pull request
Aug 21, 2024
close #329 * When lifting over to GRCh38 assembly, genomic accession and genomic position should be updated accordingly
korikuzma
added a commit
that referenced
this pull request
Aug 21, 2024
close #329 * When lifting over to GRCh38 assembly, genomic accession and genomic position should be updated accordingly
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
close #329