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

fix: genomic accession mismatch when getting nearest tx junction #356

Merged
merged 56 commits into from
Aug 21, 2024

Conversation

korikuzma
Copy link
Member

@korikuzma korikuzma commented Aug 20, 2024

close #329

  • When lifting over to GRCh38 assembly, genomic accession and genomic position should be updated accordingly

* 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`)
Addresses #224

* `genomic_to_tx_segment` will now require inter-residue coordinates to be passed
addresses #224

* initial work for cleaning up exon coord data retrieval
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)
@korikuzma korikuzma self-assigned this Aug 20, 2024
src/cool_seq_tool/mappers/exon_genomic_coords.py Outdated Show resolved Hide resolved
src/cool_seq_tool/mappers/exon_genomic_coords.py Outdated Show resolved Hide resolved
src/cool_seq_tool/mappers/exon_genomic_coords.py Outdated Show resolved Hide resolved
src/cool_seq_tool/mappers/exon_genomic_coords.py Outdated Show resolved Hide resolved
korikuzma and others added 2 commits August 20, 2024 12:58
Co-authored-by: James Stevenson <james.stevenson@nationwidechildrens.org>
Copy link
Member

@jsstevenson jsstevenson left a 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

Base automatically changed from issue-224-new-structure to staging August 21, 2024 14:18
@korikuzma
Copy link
Member Author

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

@korikuzma korikuzma merged commit 9d8cedf into staging Aug 21, 2024
12 checks passed
@korikuzma korikuzma deleted the issue-329 branch August 21, 2024 16:13
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
Labels
bug Something isn't working priority:high High priority
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants