-
Notifications
You must be signed in to change notification settings - Fork 35
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
Suggestion: Build Ensembl transcript sequences by concatenating genomic exons #103
Labels
Comments
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
github-actions
bot
added
the
stale
Issue is stale and subject to automatic closing
label
Sep 18, 2023
This issue was closed because it has been stalled for 7 days with no activity. |
reece
added
stale closed
Issue was closed automatically due to inactivity
and removed
stale closed
Issue was closed automatically due to inactivity
labels
Nov 27, 2023
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
github-actions
bot
added
the
stale
Issue is stale and subject to automatic closing
label
Mar 8, 2024
jsstevenson
added
enhancement
New feature or request
keep alive
exempt issue from staleness checks
and removed
stale
Issue is stale and subject to automatic closing
labels
Mar 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
I have been told by Ensembl that:
This means you could effectively get all Ensembl transcripts by making them from exon coordinates.
I have already implemented this - see Example code feel free to take
If you do your own liftover (ie produce Ensembl transcript alignments for a build where the sequence doesn't match) then this guarantee may be broken, perhaps only take official alignments?
Example use case: biocommons/hgvs#621
The text was updated successfully, but these errors were encountered: