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

Remove support for UCSC transcripts #523

Open
holtgrewe opened this issue Jun 9, 2021 · 5 comments
Open

Remove support for UCSC transcripts #523

holtgrewe opened this issue Jun 9, 2021 · 5 comments

Comments

@holtgrewe
Copy link
Member

Is your feature request related to a problem? Please describe.
I think the create more problems than they solve as they provide a third alignment of transcripts to the reference. RefSeq and ENSEMBL are enough.

Describe the solution you'd like
Remove support for them in code and documentation.

Describe alternatives you've considered
N/A

Additional context
N/A

@holtgrewe
Copy link
Member Author

@pnrobinson what do you think?

@pnrobinson
Copy link
Contributor

Why don't we fix the current bug with building the ser files, leave out UCSC, and if it turns out people really want to have it we can add back support later on?

@holtgrewe
Copy link
Member Author

Sounds good to me.

@holtgrewe
Copy link
Member Author

Actually, there is no bug in building the .ser files but a bug in the alignment projection... It turns out you should look at the number of bases in the transcript rather than in the reference when checking your alignments.

@julesjacobsen
Copy link
Contributor

Can we keep UCSC support? The UCSC data is stable (to my knowledge) so shouldn't cause a maintenance burden. I thought the projection bug was for RefSeq data as this is the one which required the alignment objects?

I'm obviously motivated by Exomiser maintenance and UCSC is provided as an option for people to use. I don't know how many people use this option, however.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants