-
Notifications
You must be signed in to change notification settings - Fork 216
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
The best solution for one-to-one correspondence between genes and transcripts #343
Comments
In order to obtain as many transcripts as possible corresponding to genes,i do
In the end, I realized that this was a bad idea, based on the KMT2B I annotated
but in MANE select (base on GRCh38) |
I have a similar question. I have a list of genes, some of which I'd like to annotate using manually curated ENST IDs, and the rest I am using the canonical ENST ID. My question is: Can I just provide the custom ENST IDs that I need, or do I need to provide a full list of ENST IDs if I am using the --custom-enst flag? (i.e. by providing a partial list, will only the genes with ENST IDs in that list get annotated?) Thanks, |
@nuttynutmore - you are correct. If you're happy with VEP's selection of canonical isoform, then you don't need to include it in your @user-tq - the logic for selecting a single reportable effect on a single transcript per gene is implemented here. Typically, your |
Thank you for developing this awsome tool.
I would like to know what is the best practice for selecting a unique transcript based on vep2maf. I am in a clinical analysis scenario, focusing on dozens of genes.
I plan to create a corresponding table of genes and transcripts based on grch37 based on the MANE project.
Then let vcf2maf accept this table and filter it. I noticed that custom inst seems to be able to solve this problem.
But I am a bit confused, different versions of transcripts should produce different tables. How can I clarify my transcript version? And if there are genes outside of these dozens in my data, maby they won't be annotated?
The text was updated successfully, but these errors were encountered: