Materials and Methods All Python and R Code Used in These Analyses Is Available At

Materials and Methods All Python and R Code Used in These Analyses Is Available At

Materials and Methods All Python and R code used in these analyses is available at https://github.com/harrispopgen/bxd_mutator_manuscript. We used snakemake (39) to write a collection of pipelines that can be used to reproduce all analyses described in the manuscript. Construction of the BXD RILs Detailed descriptions of the BXD dataset, including the construction of the BXD recombinant inbred lines, can be found in (15). Briefly, the BXD RILs were derived from crosses of the DBA/2J and C57BL/6J inbred laboratory strains initiated in six distinct "epochs" from 1971 to 2014. RILs were produced using one of two strategies: four epochs were produced using the standard F2 cross, and two were produced using the advanced intercross strategy. In the F2 cross design, a male DBA/2J mouse is crossed to a C57BL/6J female to produce F1 animals that are heterozygous for parental ancestry at every position in the genome. Pairs of these F1 animals are then crossed to produce F2s. To generate each individual recombinant inbred line, a brother and sister are picked from among the F2s and mated; this brother-sister mating strategy continues for many generations. In the AIL cross design, F2s are generated as in the standard F2 cross. However, pseudo-random pairs of F2 animals are then crossed to generate F3s, pseudo-random pairs of F3s are crossed to generate F4s, and so on, for up to 14 generations. Then, to generate inbred lines, brother-sister matings are once again initiated. Schematic diagrams of the F2 cross and AIL strategies are shown in Figure S1. Whole-genome sequencing, alignment, and variant calling BXD mice (all males) were euthanized using isoflurane. Tissue (spleen) was collected immediately, flash frozen with liquid nitrogen, and placed in a -80 degree freezer for subsequent analysis. All DNA extraction, library preparations and sequencing was carried out by HudsonAlpha (Huntsville, AL, USA). High molecular weight genomic DNA was isolated from 50 to 80 mg of spleen tissue using the Qiagen MagAttract kit (Qiagen, Germantown, MD). The Chromium Gel Bead and Library Kit (v2 HT kit, revision A; 10X Genomics, Pleasanton, CA, USA) and the Chromium instrument (10X Genomics) were used to prepare libraries for sequencing; barcoded libraries were then sequenced on the Illumina HiSeq X10 system. FASTQ files were aligned to the mm10/GRCm38 reference genome using the 10X LongRanger software (v2.1.6), using the "Lariat" alignment approach. Variant calling was carried out on aligned BAM files using GATK version v3.8-1-0-gf15c1c3ef (40) to generate gVCF files; these gVCFs were then joint-called to produce a complete VCF file containing variant calls for all BXDs and founders. GATK Variant Quality Score Recalibration (VQSR) was then applied to the joint-called VCF. A list of known, "true-positive" variants was created by identifying variants which were shared across three distinct callsets: 1) variants identified in DBA/2J in this study 2) variants identified in DBA/2J in (41) and 3) variants identified in DBA/2J in the Sanger Mouse Genomes Project (33). This generated a set of 3,972,727 SNPs, 404,349 deletions and 365,435 insertions; we were highly confident that these varied between the DBA/2J and reference sequences and expected that each should appear in ~50% of the BXD strains. The SNP and indel variant calls from the Sanger Mouse Genomes project (33) were also used as a training resource for VQSR. Identifying homozygous singleton variants in the BXD RILs To confidently identify singletons (sites with a derived allele in exactly one of the BXD recombinant inbred lines) we iterated over all autosomal variants in the joint-genotyped VCF using cyvcf2 (42) and identified variants that passed the following filters: first, we removed all variants that overlapped segmental duplications or simple repeat annotations in mm10/GRCm38, which were downloaded from the UCSC Genome Browser. We limited our analysis to single nucleotide variation and did not include any small insertion or deletion variants. At each site, we required both founder genotypes (DBA/2J and C57BL/6J) to be homozygous for the reference allele, for each of these genotypes to be supported by at least 10 sequencing reads, and for Phred-scaled genotype qualities in both founders to be at least 20. We then required that exactly one of the BXD RILs had a heterozygous or homozygous alternate genotype at the site; although we only included 94 BXDs in downstream analyses (see section entitled "Criteria for excluding BXD RILs in downstream analyses"), the genome sequences of all sequenced BXDs (except for the small number of BXDs that were isogenic with another line) were considered when identifying potential singletons to ensure that none of the excluded strains possessed a putative singleton allele present in the focal strain. To account for possible genotyping or sequencing errors, we considered heterozygous genotypes with very high allele balance (i.e., fraction of reads supporting the alternate allele >= 0.9) to be effectively homozygous. For candidate heterozygous and homozygous singletons, we required the genotype call to be supported by at least 10 sequencing reads and have Phred-scaled genotype quality at least 20. Finally, we confirmed that at least one other BXD shared a parental haplotype identical-by-descent with the focal strain (i.e., the strain with the putative singleton) at the singleton site but was homozygous for the reference allele at that site. We additionally annotated the full autosomal BXD VCF with SnpEff (20) version 4.3t, using the GRCm38.86 database and the following command: java -Xmx16g -jar /path/to/snpeff/jarfile GRCm38.86 /path/to/bxd/vcf > /path/to/uncompressed/output/vcf Identifying haplotypes shared IBD between the BXD RILs and the parental DBA/2J and C57BL/6J strains For each chromosome in each recombinant inbred line, we used a Hidden Markov Model (HMM) to identify haplotype tracts inherited IBD from each of the two founder lines. First, we iterated over every variant in the joint-genotyped BXD VCF file; we only considered sites where one of the two founder strains (either DBA/2J or C57BL/6J) was homozygous for the alternate allele, and the other strain was homozygous for the reference allele. (Since the reference mouse sequence mm10 is largely derived from the C57BL/6J strain, this was nearly always tantamount to requiring DBA/2J to be homozygous for the alternate allele, except for the rare sites where the BXD founder diverged from the C57BL/6J individual used to generate the mouse reference genome). We further required the genotype of each founder to be supported by at least 10 sequencing reads, and the Phred-scaled genotype quality of each founder genotype to be at least 20. We assumed that these sites represented fixed differences between DBA/2J and C57BL/6J. By comparing the genotypes of all BXD RILs to the two founder genotypes at each of these informative fixed differences, we then identified tracts of sites in which RIL genotypes consistently matched one of the two founders. For each chromosome in each BXD RIL, we constructed an array of length S, where S was the number of fixed differences between C57BL/6J and DBA/2J across that chromosome. Each element i in this array took one of three values: 0 (if the genotype of the RIL at site Si did not match the DBA/2J genotype), 1 (if the genotype of the RIL at site Si matched the DBA/2J genotype), or -1 (if the genotype of the RIL at site Si was unknown, heterozygous, supported by fewer than 10 reads, or had a Phred-scaled genotype quality < 20). We then built an HMM using pomegranate (43) with two states (DBA/2J or C57BL/6J, state and transition probabilities defined in associated code), and inferred long sequences of identical states. These sequences likely represent regions of the genome shared IBD with one of the two founders. Annotating singletons with triplet sequence contexts and conservation scores For each candidate singleton variant, we were interested in characterizing the 5' and 3' sequence context of the mutation, as well as the phastCons conservation score of the nucleotide at which the variant occurred. To determine the sequence context of each variant, we used the mutyper API (44). mutyper ingests a reference sequence and information about a particular variant, and determines the ancestral and derived alleles, as well as the nucleotides that flank that variant. To annotate each variant with its phastCons score, we downloaded phastCons scores derived from a 60-way placental mammal alignment for the mm10/GRCm38 genome build in WIG format from the UCSC Table Browser. We then converted the WIG files to BED format using bedops (45), compressed the BED format files with bgzip, and indexed the compressed BED files with tabix. Within the Python script used to identify singletons, we then used pytabix (https://github.com/slowkow/pytabix) to query the phastCons BED files at each putative singleton. Identifying fixed variants for comparison to singletons We aimed to compare the distribution of phastCons conservation probabilities in the BXD singletons to a "control" set of variants. We defined these control variants as mutations present in one of the two founder genomes (which passed the same filtering criteria required of singletons), and present in all BXDs that inherited the founder haplotype with the mutation at that site. We expected that these "fixed" variants had occurred well before the construction of the BXDs in DBA/2J or C57BL/6J founder stocks. To ensure that we sampled control variants from the full length of the reference genome sequence, we first used bedtools (46) to generate 50-kbp windows across the mm10/GRCm38 reference genome.

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    21 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us