SNV and Indel support
pVACseq offers epitope binding predictions for missense, inframe indel, and frameshift mutations.
pVACseq uses a single-sample VCF file as its input. This VCF file must be annotated with VEP. See the Input File Preparation for more information.
No local install of epitope prediction software needed
pVACseq utilizes the IEDB RESTful web interface. This means that none of the underlying prediction software, like NetMHC, needs to be installed locally.
We only recommend using the RESTful API for small requests. If you use the RESTful API to process large VCFs or to make predictions for many alleles, epitope lengths, or prediction algorithms, you might overload their system. This can result in the blacklisting of your IP address by IEDB, causing 403 errors when trying to use the RESTful API. In that case please open a ticket with IEDB support to have your IP address removed from the IEDB blacklist.
Support for local installation of the IEDB Analysis Resources
Using a local IEDB installation is strongly recommended for larger datasets or when the making predictions for many alleles, epitope lengths, or prediction algorithms. More information on how to install IEDB locally can be found on the Installation page.
MHC Class I and Class II predictions
Both MHC Class I and Class II predictions are supported. Simply choose the desired prediction algorithms and HLA alleles during processing and Class I and Class II prediction results will be written to their own respective subdirectories in your output directory.
By using the IEDB RESTful web interface, pVACseq leverages their extensive support of different prediction algorithms.
|MHC Class I Prediction Algorithm||Version|
|MHC Class II Prediction Algorithm||Version|
Automatic filtering on the binding affinity ic50 value narrows down the results to only include “good” candidate peptides. The binding filter threshold can be adjusted by the user for each pVACseq run. pVACseq also support the option of filtering on allele-specific binding thresholds as recommended by IEDB. Additional filtering on the binding affitinity can be manually done by the user by running the standalone binding filter on the filtered result file to narrow down the candidate epitopes even further or on the unfiltered all_epitopes file to apply different cutoffs.
Readcount and expression data are extracted from an annotated VCF to automatically filter with adjustable thresholds on depth, VAF, and/or expression values. The user can also manually run the standalone coverage filter to further narrow down their results from the filtered output file.
If the input VCF is annotated with transcript support levels, pVACseq will filter on the transcript support level to only keep high-confidence transcripts of level 1. This filter can also be run standalone.
As a last filtering step, pVACseq applies the top score filter to only keep the top scoring epitope for each variant. As with all previous filter, this filter can also be run standalone.
Scoring of candidate neoepitopes
Filtered neoepitopes are scored and ranked based on the binding affinity, fold change between mutant and wildtype binding affinity, gene expression, RNA and DNA VAF.
Incorporation of proximal germline and somatic variants
To incorporate proximal variants into the neoeptioe predictions, users can provide a phased VCF of proximal variants as an input to their pVACseq runs. This VCF is then used to incorporate amino acid changes of nearby variants that are in-phase to a somatic variant of interest. This results in corrected mutant and wildtype protein sequences that account for proximal variants.
NetChop and NetMHCstab integration
Cleavage position predictions are added with optional processing through NetChop.
Stability predictions can be added if desired by the user. These predictions are obtained via NetMHCstab.