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

feat: support GTF formats other than ensembl #115

Open
ninsch3000 opened this issue Mar 10, 2023 · 0 comments
Open

feat: support GTF formats other than ensembl #115

ninsch3000 opened this issue Mar 10, 2023 · 0 comments
Labels
future will not be fixed for NOW

Comments

@ninsch3000
Copy link
Collaborator

ninsch3000 commented Mar 10, 2023

Is your feature request related to a problem? Please describe.
Currently, ZARP has only been tested with/only works with ensembl style GTF files. In order to use GTF files from other sources some adaptations have to be made to the workflow.

Describe the solution you'd like
Identify which changes have to be made in the workflow (Probably chromosome names and other fields will not be correctly parsed) and make the appropriate changes.

From gitlab comment of @mkatsanto:

Currently we only support Ensembl. Maybe we could also test refseq and gencode.
This would required conversion for the chromosome name notation e.g and some other fields towards the end.

  • Check results for genes that are the same across different annotations
  • Check if the extra features (3utrs for example) are considered by alfa or this causes an issue.
  • Which rules do we expect to produce different results?
  • Make sure in the documentation that we mainly support Ensembl.
  • Mention we haven't tested extensively for all organisms so things might not work properly for rare organisms.

Describe alternatives you've considered
Mention in the documentation that only ensembl style GTFs are supported

@ninsch3000 ninsch3000 added the future will not be fixed for NOW label Mar 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
future will not be fixed for NOW
Projects
None yet
Development

No branches or pull requests

1 participant