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

Offset error when entering genomic coordinates between exons #323

Closed
jarbesfeld opened this issue Sep 4, 2024 · 5 comments
Closed

Offset error when entering genomic coordinates between exons #323

jarbesfeld opened this issue Sep 4, 2024 · 5 comments
Assignees
Labels
bug Something isn't working priority:high High priority

Comments

@jarbesfeld
Copy link
Contributor

Describe the bug

A Transcript Segment object is currently not being created when a genomic coordinate that occurs between exons is supplied to start or end.

Steps to reproduce

  1. Select Transcript Segment Object, genomic coordinates and transcript
  2. For transcript, enter NM_152263.3
  3. For chromosome, enter NC_000001.11
  4. For ending position, enter 154191900

Expected behavior

We would expect exon 1 to be chosen with an offset of 1

Current behavior

The offset is not appearing in the top right of the object (instead a loading circle shows)

Possible reason(s)

It's possible the code needs to be updated to include the offset calculation when a genomic breakpoint occurs in between exons. This should allow for the correct offset to be computed.

Suggested fix

No response

Branch, commit, and/or version

I was looking at http://fusion-curation-dev-eb.us-east-2.elasticbeanstalk.com/assayed-fusion

Screenshots

No response

Environment details

Mac M1

Additional details

No response

Contribution

None

@jarbesfeld jarbesfeld added the bug Something isn't working label Sep 4, 2024
@jarbesfeld
Copy link
Contributor Author

I think this would be good to address now, since it's likely that users will have cases where aligned genomic breakpoints occur between exons

@jsstevenson
Copy link
Member

I can't remember where we wrote this down, but Alex had at one point suggested some kind of visual warning if you try to put in a coordinate that's more than 50 bp's away from an exon

@korikuzma korikuzma added the priority:high High priority label Sep 4, 2024
@korikuzma
Copy link
Member

@jarbesfeld says this is the highest priority issue after #311

@katiestahl
Copy link
Contributor

Copy link

Closed by #336.

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

No branches or pull requests

4 participants