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

Sequences are different in Reference sequence track and Annotations track #480

Closed
shashankbrgowda opened this issue Nov 20, 2024 · 2 comments · Fixed by #562
Closed

Sequences are different in Reference sequence track and Annotations track #480

shashankbrgowda opened this issue Nov 20, 2024 · 2 comments · Fixed by #562
Assignees

Comments

@shashankbrgowda
Copy link
Contributor

Reported by Toby

The genome sequence displayed in the "Reference sequence" track is completely different to that displayed in the "Annotations" track (or more accurately out of sync with each by a few bases).
image

This also seem to result in the splice site checker in the "transcript details" window showing lots of non-canonical splice sites. In the case below (ENST00000661030) I know all the annotated splice sites are actually canonical but are not being displayed as such:
image

However, when I refresh the page this error resolves itself. The genome sequence in both tracks is now the same (although the "horizontal flip" function works slightly differently in each), and the splice sites for ENST00000661030 appear correctly:
image

It seems like if you start at these coordinates: 1:78,938,247..78,938,318[rev] and then start navigating around/altering the co-ords a bit (i.e. by a combination of zooming in and out; flipping the strand etc) you can normally replicate the issue fairly often.....

@garrettjstevens
Copy link
Contributor

@shashankbrgowda and I reproduced this by zooming all the way in before opening the tracks in a fresh session.

@dariober dariober self-assigned this Mar 26, 2025
@dariober dariober moved this to In progress in Apollo 3 Mar 26, 2025
dariober added a commit that referenced this issue Mar 27, 2025
Also fix issue in accessing the end of the reference sequence. The fix
is not ideal since it simply resets the stop coordinate if the sequence
is shorter than declared.
@dariober
Copy link
Contributor

This issue was due to incorrect merging of overlapping regions and it should be resolved here.

There was also a related issue with fetching the end of a reference sequence: Load packages/apollo-cli/test_data/tiny.fasta.gff3, select the "reference sequence track" (annotation track is fine) and go to the end of ctgA, you get:

Image

This is because method getFeatures in ApolloSequenceAdapter tries to access a region extending beyond the end of the contig. For now this is fixed here by simply resetting the stop coordinate if the sequence is shorter than declared. It would be better to find out why it happens though...

@garrettjstevens garrettjstevens linked a pull request Apr 2, 2025 that will close this issue
@github-project-automation github-project-automation bot moved this from In progress to Done in Apollo 3 Apr 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants