Giter VIP home page Giter VIP logo

mapping's Introduction

Introgression Mapping for B73 x Teosinte/Landraces

This git page explains the details about introgression mapping of B73 x Teosinte/Landraces populations. We start of with demultiplexing multiple reads into individuals reads, followed by mapping to a reference genome (b73 version 5), and finally visualization of the introgressed region per chromosome. The detailed process are explained below.

Demultiplexing using Sabre

Sabre is used to demultiplex sequences, i.e, separate the sequences from the . Detailed installation process is here. The yaml file used to install the sable in the server is src/sabre.yml. The tcsh script used to run a single forward and reverse read is found in src/sabre_mapping.csh. Separate indexing files are required for separate samples which are found in src/mapping_index_BZea/.

Quality Control using Trimmomatic

QC is an important step before running any analysis. I use Trimmomatic for this. The code is found here.

Alignment to the reference genome

The alignment is done with minimap2. The installation process is found here. The code for running the alignment is found in src/mapping_minimap.csh.

Viewing the alignment

Basic viewing of the alignment can be done with samtools. The detailed installation process for a linux distribution can be found here.

Quality Control

Post-alignment QC is equally important to remove potential sources of error. Using samtools, reads with a mapping quality (Q) score of less than 15 are filtered out to ensure only high-confidence alignments are considered for analysis. Duplicated reads are identified and removed using Picard tools to avoid inflating read counts filtering was also done for base quality score recalibration (BQSR) Furthermore, regions that did not map to the reference genome are also excised from the dataset. The exact commands and scripts for this QC step will be added to the repository for reference.

Genotype Likelihood Estimation

For populations like B73 x Teosinte/Landraces, estimating genotype likelihoods is a necessary step before calling SNPs. This is particularly useful in accounting for the uncertainty in the data due to sequencing errors or allelic dropout. Genotype likelihood estimation can be performed using tools like angsd. Here, we would provide a script and a detailed description of the process to compute the likelihood of genotypes for each individual at each SNP position, taking into account the depth of coverage and the quality of reads.

mapping's People

Contributors

nirwan1265 avatar

Watchers

 avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.