This is NOT the distribution site for Polysolver software. This is a modification made for pipeline incorperation from v1.0. If you're looking for Polysolver please see:

http://archive.broadinstitute.org/cancer/cga/polysolver

Shukla SA, Rooney MS, Rajasagi M, Tiao G, Dixon PM, Lawrence MS, Stevens J, Lane WJ, Dellagatta JL, Steelman S, Sougnez C, Cibulskis K, Kiezun A, Hacohen N, Brusic V, Wu CJ, Getz G. Comprehensive analysis of cancer-associated somatic mutations in class I HLA genes. Nat Biotechnol. 2015 Nov;33(11):1152-8. PubMed PMID: 26372948; PubMed Central PMCID: PMC4747795.

https://www.ncbi.nlm.nih.gov/pubmed/26372948

If you want to run Polysolver, you should try to directly use the above.

If you are using hla-polysolver as part of a pipeline be sure to site the above Polysolver software and publication. This is modification under Polysolver's "BSD-style License" with the purpose of maintaing a stable platform for supplying the required files for to work with the LOHHLA pipeline (McGranahan N., et. al. https://doi.org/10.1016/j.cell.2017.10.001) and other pipelines. The mutual requirements include legacy versions of dependencies that are not described in the manuals so this hla-polysolver fork is intended to provide a clear connection to those undocumented dependencies and ease their depolyment on conda and docker environments. This fork was generated from v1.0 Polysolver and is not affiliated with Polysolver or the Broad Institute. Please see LICENSE for the particular requirements and respect the license requirements of the dependencies. And to make adjustments or updated genomes/annotations as necessary. My work on this fork is free to use reuse and modify under the Apache 2.0 license, but please pay attention to the included LICENSE notice for Polysolver and its dependancies there are a lot of boutique licenses to pay attention to including Broad licenses and Commercial Novoalign license.

hla-polysolver

Changes in hla-polsyolver 1.0.0 from polysolver v1.0

• Added added build recipie for conda
• Remove absolute path references that break the run
• Use the install of build.sh to make it so environment variables are set automatically when run within Conda
• Reduced use of enviornment variables
• Remove Novoalign index from the source code. Now is pre-built when building the conda environment, and is included along with other necessary data in the conda environment. If you are doing a local run and not using Conda see build.sh to see how to create this data file.
• Change from hardcoded perl and bash to whichever the user has installed under /usr/bin/env. This is better for non-conda runs but has the added benefit of using Conda's perl when running.
• Installed the shell scripts for hla typing, mutation calling, and annotation in the Conda enviornment so they are in the PATH of the Conda environment.
• Cleaning up the command calls and piping allows running the installed scripts from outside of the source directory.
• Removed hardcoded author paths
• Hardcoded temporary directory to /tmp. Not a great thing, but should work on most linux, and I plan to fix this soon.
• Added old picard tools dependency (likely what polysolver referred to as GATK)
• Updated data to include necessary fastas to complete mutation calling pipeline (part 2 of polysolver)

Running in Conda

hla-polysolver is mainly intended for use by adding it to a conda environment.

You can do this by setting your ~/.condarc file to include

channels:
  - defaults
  - bioconda
  - conda-forge
  - vacation

Then if you can install the usual conda way. I recommend creating a seperate environment for it because of its many ancient dependancies. You probably don't want them in your every day working environment.

$ conda create -n polysolver -c vacation hla-polysolver

Then after the environement is created you can activate it.

$ source activate polysolver

And then you can run polysolver as described int the testing description. If you get the github repository you will have access to the testing data.

(polysolver)$ git clone https://github.com/jason-weirather/hla-polysolver.git

And you can run the test.

(polysolver)$ shell_call_hla_type hla-polysolver test/test.bam Unknown 1 hg19 STDFQ 0 output
(polysolver)$ shell_call_hla_mutations_from_type hla-polysolver/test/test.bam hla-polysolver/test/test.tumor.bam output/winners.hla.txt hg19 STDFQ output
(polysolver)$ shell_annotate_hla_mutations indiv output

This will produce results in a folder called output.

Building the Conda Enviroment yourself

Requirements to build the linux conda environment that didn't seem to pick up from conda revolved around the strelka caller and maybe its vcftools ... may need to have these in the environment to build

• zlib1g-dev
• g++

TABLE OF CONTENTS

1. Description 1.1 POLYSOLVER 1.2 POLYSOLVER-based mutation detection 1.3 Annotation of mutations
2. Installation
3. Testing 3.1 POLYSOLVER 3.2 POLYSOLVER-based mutation detection 3.3 Annotation of mutations
4. Running 4.1 POLYSOLVER 4.2 POLYSOLVER-based mutation detection 4.3 Annotation of mutations

1. Description

This software package consists of 3 main tools:

1.1 POLYSOLVER (POLYmorphic loci reSOLVER)

This tool can be used for HLA typing based on an input exome BAM file and is currently infers infers alleles for the three major MHC class I (HLA-A, -B, -C).

Script: shellcallhla_type

Input parameters:

-bam: path to the BAM file to be used for HLA typing
-race: ethnicity of the individual (Caucasian, Black, Asian or Unknown)
-includeFreq: flag indicating whether population-level allele frequencies should be used as priors (0 or 1)
-build: reference genome used in the BAM file (hg18 or hg19)
-format: fastq format (STDFQ, ILMFQ, ILM1.8 or SLXFQ; see Novoalign documentation)
-insertCalc: flag indicating whether empirical insert size distribution should be used in the model (0 or 1)
-outDir: output directory

Output:

winners.hla.txt: file containing the two inferred alleles for each of HLA-A, HLA-B and HLA-C

1.2 POLYSOLVER-based mutation detection

This tool works on a tumor/normal pair of exome BAM files and inferred mutations in the tumor file. It assumes that POLYSOLVER has already been run on the normal BAM.

Script: shellcallhlamutationsfrom_type

Input parameters:

-normal_bam_hla: path to the normal BAM file
-tumor_bam_hla: path to the tumor BAM file
-hla: inferred HLA allele file from POLYSOLVER (winners.hla.txt or winners.hla.nofreq.txt)
-build: reference genome used in the BAM file (hg18 or hg19)
-format: fastq format (STDFQ, ILMFQ, ILM1.8 or SLXFQ; see Novoalign documentation)
-outDir: output directory

Output:

call_stats.$allele.out: Mutect output for each inferred allele in winners.hla.txt
$allele.all.somatic.indels.vcf: Strelka output for each inferred allele in winners.hla.txt

1.3 Annotation of mutations

This tool annotates the predicted mutations from (ii) with gene compartment and amino acid change information

Script: shellannotatehla_mutations

Input parameters:

-indiv: individual ID, used as prefix for output files
-dir: directory containing the raw call files (Mutect: call_stats*, Strelka: *all.somatic.indels.vcf). Also the output directory

Output:

(a). Mutect $indiv.mutect.unfiltered.nonsyn.annotated - list of all unfiltered mutations $indiv.mutect.filtered.nonsyn.annotated - list of cleaned non-synonymous mutations $indiv.mutect.filtered.syn.annotated - list of cleaned synonymous changes $indiv.mutect.ambiguous.annotated - list of ambiguous calls. This will generally be empty (save for the header). It will be populated if the same mutation (ex. p.A319E) is found in two or more alleles in the individual, with the same allele fractions. In such cases one allele is randomly chosen and included in the .nonysn.annotated file while the complete list of alleles is listed in the .ambiguous.annotated file. If the ethnicity of the individual is known, an alternate method would be to pick the allele with the highest frequency.

(b). Strelka $indiv.mutect.unfiltered.nonsyn.annotated - list of all unfiltered indels (as detected by Strelka) $indiv.strelkaindels.filtered.annotated - list of cleaned indels (as detected by Strelka) $indiv.strelkaindels.ambiguous.annotated - see description of $indiv.mutect.ambiguous.annotated in (a). above

2. Installation

The POLYSOLVER suite of tools depends upon the following packages and utilities:

Samtools (http://samtools.sourceforge.net/) GATK (https://www.broadinstitute.org/gatk/download) Novoalign (http://www.novocraft.com/main/downloadpage.php) Perl modules ((http://www.cpan.org/modules/INSTALL.html) - Math::BaseCalc - List::MoreUtils - List::Util - Parallel::ForkManager - POSIX - Dumpvalue - Data::Dumper Bioperl (http://www.bioperl.org/wiki/InstallingBioPerl) Mutect (http://www.broadinstitute.org/cancer/cga/mutectdownload) Strelka (https://sites.google.com/site/strelkasomaticvariantcaller/home/download)

Also make changes to the config.sh file to set up the following environmental variables

-PSHOME: POLYSOLVER home directory -SAMTOOLSDIR: directory containing the samtools executable -JAVADIR: directory containing the JAVA executable -NOVOALIGNDIR: directory containing the Novoalign executables -GATKDIR: directory containing the GATK jar files -MUTECTDIR: directory containing the Mutect executable (for POLYSOLVER-based mutation detection only) -STRELKADIR: directory containing the Strelka (for POLYSOLVER-based mutation detection only)

The following command should make the necessary changes prior to running the tools (assuming the tcsh shell):

source scripts/config.sh

3. Testing

Your installation can be tested by running the following command from $PSHOME:

3.1 POLYSOLVER

scripts/shellcallhla_type test/test.bam Unknown 1 hg19 STDFQ 0 test

If successful, the following command should not yield any differences:

diff test/winners.hla.txt test/orig.winners.hla.txt

3.2 POLYSOLVER-based mutation detection

scripts/shellcallhlamutationsfrom_type test/test.bam test/test.tumor.bam test/winners.hla.txt hg19 STDFQ test

If successful, the following command should not yield any differences:

diff test/callstats.hlab39010102l.out test/orig.callstats.hlab39010102l.out

3.3 Annotation of mutations

scripts/shellannotatehla_mutations indiv test

If successful, the following command should not yield any differences:

diff test/indiv.mutect.filtered.nonsyn.annotated test/orig.indiv.mutect.filtered.nonsyn.annotated

4. Running

The tools can be run using the following commands:

4.1 POLYSOLVER

$PSHOME/scripts/shellcallhla_type

example:

$PSHOME/scripts/shellcallhla_type test/test.bam Unknown 1 hg19 STDFQ 0 test

4.2 POLYSOLVER-based mutation detection

$PSHOME/scripts/shellcallhlamutationsfrom_type

example:

$PSHOME/scripts/shellcallhlamutationsfrom_type test/test.bam test/test.tumor.bam test/winners.hla.txt hg19 STDFQ test

4.3 Annotation of mutations

$PSHOME/scripts/shellannotatehla_mutations

example:

$PSHOME/scripts/shellannotatehla_mutations indiv test