Maize Mo17 SNPs

2018-07-11
Loading...
Thumbnail Image
Statistics
View Statistics

Collection period

Date completed

Date updated

Time period coverage

Geographic coverage

Source information

Journal Title

Journal ISSN

Volume Title

Title

Maize Mo17 SNPs

Published Date

2018-07-11

Author Contact

Zhou, Peng
zhoux379@umn.edu

Type

Dataset
Genomics Data

Abstract

Genome resequencing of Mo17 was done as part of the bioMAP project (REF). 477 million 100bp paired-end reads were generated for Mo17 giving an average of 95x coverage. Reads were first trimmed by Trimmomatic (Bolger et al. 2014) and mapped to the maize B73 genome AGPv4 (Jiao et al. 2017) using BWA-MEM (Li and Durbin 2010). PCR duplicates were marked and removed using GATK (McKenna et al. 2010). Variants were called by GATK haplotypecaller and filtered using different filters for SNPs: (QD > 2, FS < 60, MQ > 40, MQRankSum > -12.5, ReadPosRankSum > -8, SOR < 4) and for InDels: (QD > 2, FS < 200, ReadPosRankSum > -20, SOR < 10). Moreover, variants located in regions with unusually high coverage (DP > Mean + 2*SD) and heterozygous calls (GT == '0/1') were also removed. The final variant file containing 8.04 million variants with 164 thousand CDS variants was deposited in DRUM.

Description

Referenced by

Related to

Replaces

License

Publisher

Funding information

item.page.sponsorshipfunderid

item.page.sponsorshipfundingagency

item.page.sponsorshipgrant

Previously Published Citation

Suggested citation

Zhou, Peng. (2018). Maize Mo17 SNPs. Retrieved from the Data Repository for the University of Minnesota (DRUM), https://doi.org/10.13020/D6T38X.
View/Download file
File View/OpenDescriptionSize
Mo17.vcf.gzZmays_Mo17_SNP.vcf.gz210.58 MB
Readme.txtReadme4.06 KB

Content distributed via the University Digital Conservancy may be subject to additional license and use restrictions applied by the depositor. By using these files, users agree to the Terms of Use. Materials in the UDC may contain content that is disturbing and/or harmful. For more information, please see our statement on harmful content in digital repositories.