From Genome Analysis Wiki
Jump to: navigation, search

Minimac: 1000 Genomes Imputation Cookbook

121 bytes added, 03:40, 28 January 2015
no edit summary
=== Your Own Data ===
To get started, you will need to store your data in [[Merlin]] format pedigree and data files, one per chromosome. For details, of the Merlin file format, see the [ Merlin tutorial].
Within each file, markers should be stored by chromosome position. Alleles should be stored in the forward strand and can be encoded as 'A', 'C', 'G' or 'T' (there is no need to use numeric identifiers for each allele).
The latest reference panel generated by the 1000 Genomes project uses NCBI Build 37 (HG 19). Make sure that your data is on Build 37 (or Minimac may ignore genotyped markers whose names have changed in build Build 37). If you are trying to convert your data from an earlier genome build to build Build 37, you'll probably find the [ dbSNP merge table] ([ table description on the NCBI website]), which logs rs# changes between dbSNP builds, and the UCSC online [ liftOver tool], which converts genome positions between different genome builds, to be quite useful. We have aslo also documented ([[LiftOver | Link]]) a general procedure to convert genome positions and rs number between builds.
If you are planning to use imputation with the MetaboChip, you might find a list of SNPs whose order varies between NCBI genome build Build 36 and 37 convenient. Here it is: [ List of Metabochip SNPs Whose Order Changes With Build]
Note: For the most recent reference panel in VCF format by default GWAS SNPs are expected to be in the chr:pos format e.g. 1:1000; otherwise, for GWAS SNPs in the rs format you have to set the --rs flag
With older genotyping platforms, low frequency SNPs are also often excluded because they are hard to genotype accurately. With more modern genotyping arrays, the accuracy of genotype calls for low frequency SNPs is less of a concern.
Two good ways to verify that you have used appropriate quality control steps are to generate a Q-Q plot for your dataset and to calculate a genomic control parameter. If these verifications are not satisfactory, it may be useful to investigate before proceeding to imputation.
=== Reference Haplotypes ===
Reference haplotypes generated by the 1000 Genomes project and formatted so that they are ready for analysis are available from the [ MaCH download page]. In our hands, it is ideal to always use the most recent release since generation of additional sequence data, improvements in variant discovery, genotyping and haplotyping strategies typically result in noticeable improvements in data quality. When this page was written, the most recent release of 1000 Genomes project haplotypes was the [ Integrated Phase I release], including 1092 individuals. We recommend to use using the reduced GIANT all population panel (no monomorphic and singleton sites)
[ GIANT.phase1_release_v3.20101123.snps_indels_svs.genotypes.refpanel.ALL.vcf.gz.tgz]
mach1 -d chr1.dat -p chr1.ped --rounds 20 --states 200 --phase --interim 5 --sample 5 --prefix chr$chr.haps
This will request that MaCH estimate haplotypes for your sample, using 20 iterations of its Markov sampler and conditioning each update on up to 200 haplotypes. A summary description of these parameters follows (but for a more complete description, you should go to the [ MaCH website]):
{| class="wikitable" border="1" cellpadding="2"
|style=white-space:nowrap|<code>-d sample.dat</code>
| Data file in [ Merlin format]. Markers should be listed according to their order along the chromosome.
| <code>-p sample.ped</code>
| Pedigree file in [ Merlin format]. Alleles should be labeled on the forward strand.
| <code>--states 200</code>
=== Imputation into Phased Haplotypes - minimac ===
Imputing genotypes using '''minimac''' is a straightforward process: after selecting a set of reference haplotypes, plugging-in the target haplotypes from the previous step and setting the number of rounds to use for estimating model parameters (which describe the length and conservation of haplotype stretches shared between the reference panel and your study samples), imputation should proceed rapidly. Because marker names can change between dbSNP versions, it is usually a good idea to include an ''aliases'' file that provides mappings between earlier marker names and the current preferred name for each polymorphism.
A typical minimac command line, where the string $chr should be replaced with an appropriate chromosome number, might look like this:
| <code>--refHaps ref.hap.gz </code>
| Reference haplotypes (e.g. from [ MaCH download page])
| <code>--vcfReference </code>
Again, you can speed-up things by running this step imputation in parallel and . For example, in our cluster we'd use:
<source lang="text">
=== Reference based chunking ===
REMARK: this works only with SNPIDs in the chr:pos format, or in other words, rs numbers are not supported here. In case you didn't split your data with ChunkChromosome, we highly recommend to run running imputation using our reference based chunking method (minimac.1011.316.12 or newer required)
<source lang="bash">
for start in `seq 0 $chunksize $chromend`
# For females: follow the same protocol as for autosomes
# For males: they have only one X chromosome and are therefore already phased. Simply convert the pedigree file into a MaCH haplotype file (missing genotypes should be encoded as: "0" or "." or "N" )

Navigation menu