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

Adding Gene and Transcript Expression to VCF for pVACseq #1159

Open
biounix opened this issue Nov 20, 2024 · 6 comments
Open

Adding Gene and Transcript Expression to VCF for pVACseq #1159

biounix opened this issue Nov 20, 2024 · 6 comments

Comments

@biounix
Copy link

biounix commented Nov 20, 2024

Hi,

If it’s possible to add both gene and transcript expression annotations to the input VCF file for pVACseq (GX and TX fields with vcf-expression-annotator), is it advisable to include both? Or is it better to include just one of them? If the latter, which one would you recommend prioritizing? My guess would be transcript expression since it seems more specific.

Additionally, if both gene and transcript expressions are included, how does pVACseq handle or prioritize this information during processing?

I couldn’t find documentation on this, so apologies if this has been answered elsewhere.

Thank you for your time and for developing such an invaluable toolset!

@chrisamiller
Copy link
Contributor

chrisamiller commented Nov 20, 2024

pVACtools doesn't use the GX/TX information for anything in the binding predictions, etc. It is passed through to the aggregate report table, and is one of the factors used in determining the neoantigen's "Tier". It is also exposed in the pVACview interface, so that you can use that information when prioritizing peptides. To answer your question, if you have both GX and TX, there's generally no reason not to include both, because they can be useful items to think about when thinking about peptide prioritization (even if this particular transcript isn't well-expressed, is the same short peptide part of one of the other transcripts from this well-expressed gene?)

@biounix
Copy link
Author

biounix commented Nov 20, 2024

Great! Thanks for the answer.

@susannasiebert
Copy link
Contributor

To add to @chrisamiller we do use both the TX and GX information in the coverage filter (both use the same --expn-val cutoff). This will impact the neoantigen candidates in the .filtered.tsv. For the aggregated report, gene expression is used for the tiering as part of the Allele Expr value, which is gene expression * tumor RNA VAF. You can find more information about the tiers in the aggregate report on this page of our docs.

@biounix
Copy link
Author

biounix commented Nov 20, 2024

Thanks for your explanation, @susannasiebert!

Then, if expression values are present but not the tumor RNA VAF information (NA), I understand that the expression criteria for tiering are not applied. Is that right?

@susannasiebert
Copy link
Contributor

Correct, it would "auto-pass" that specific criteria and only consider the other criteria for each tier.

@biounix
Copy link
Author

biounix commented Nov 20, 2024

Thank you for clearing that up, much appreciated.

PD: I'm starting to love this tool. So complete and easy to use.

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

No branches or pull requests

3 participants