(A) Regulatory System Analysis with respect to microRNAs

(B) Computational Epigenomics & Regulomics:

(C) Computational issues with Next Generation Sequencing:

Department of Biotechnology,
Institute of Himalyan Bioresources Technology
CSIR, Palampur(Himachal Pradesh), India.
Email: ravishihbt.res.in; ravish9gmail.com

More @ http://scbb.ihbt.res.in/SCBB_dept/Lab_Member.php

First cover a full workflow from preparation, reads counting, data preprocessing, gene set test, to pathway visualization in about 40 lines of codes. The same workflow can be used for GO analysis or other types of gene set analysis too. We also describe joint workflows, i.e. to do gene-level analysis using one of the major RNA-Seq analysis tools, DEseq/DEseq2, edgeR, limma and Cufflinks, and feed the results into GAGE/Pahview for pathway analysis or visualization. All these workflows are implemented in R/Bioconductor.

The work ows cover the most common situations and issues for RNA-Seq data pathway analysis. Issues like data quality assessment are relevant for data analysis in general yet out the scope of this tutorial. Although we focus on RNA-Seq data here, but pathway analysis work ow remains similar for microarray, particularly step 3-4 would be the same. Please check gage and pathview vigenttes for details.

Note: You need to update to current release versions of R(3.0.2)/ Bioconductor(2.13) to use all the features. 

Reference: 

Please check it out:
http://bioconductor.org/packages/release/bioc/html/gage.html
http://bioconductor.org/packages/release/bioc/vignettes/gage/inst/doc/RNA-seqWorkflow.pdf

Usage: perl run_rcorrector.pl [OPTIONS]
OPTIONS:
	Required
	-s seq_files: comma separated files for single-end data sets
	-1 seq_files_left: comma separated files for the first mate in the paried-end data sets
	-2 seq_files_right: comma separated files for the second mate in the paired-end data sets
	-i seq_files_interleaved: comma sperated files for interleaved paired-end data sets
	Optional
	-k INT: kmer_length (<=32, default: 23)
	-od STRING: output_file_directory (default: ./)
	-t INT: number of threads to use (default: 1)
	-trim : allow trimming (default: false)
	-maxcorK INT: the maximum number of correction within k-bp window (default: 4)
	-wk FLOAT: the proportion of kmers that are used to estimate weak kmer count threshold, lower for more divergent genome (default: 0.95)
	-ek INT: expected number of kmers; does not affect the correctness of program but affects the memory usage (default: 100000000)
	-stdout: output the corrected reads to stdout (default: not used)
	-verbose: output some correction information to stdout (default: not used)
	-stage INT: start from which stage (default: 0)
		0-start from begining(storing kmers in bloom filter) ;
		1-start from count kmers showed up in bloom filter;
		2-start from dumping kmer counts into a jf_dump file;
		3-start from error correction.

Address of the bookmark: https://github.com/mourisl/Rcorrector/

http://rosalind.info/problems/list-view/

Address of the bookmark: http://rosalind.info/problems/list-view/

by Dr. Pandurang Kolekar, Bioinformatics Engineer, Strand Life Sciences

Abstract:

Unique Molecular Identifiers (UMIs) are short random nucleotide sequences that are increasingly being used in high-throughput sequencing experiments. In this webinar, we will highlight the UMI-friendly features of Strand NGS v3.1 including support for handling well known and customised UMI libraries, QC metrics, consensus alignment, UMI-based family size filters for read list, genome browser enabled with UMI-specific features and filters, UMI-aware variant calling parameters, and exporting UMI-tagged aligned samples. These all features together empower users to harness the potential of UMI-tagged NGS data for deeper insights. A case study demonstrating application of these UMI-based features in Strand NGS for low frequency variant calling in cfDNA sample will be presented.

UMI-tagged NGS libraries allow, ultra-sensitive detection of low frequency variants from liquid biopsy samples using DNA-Seq and accurate quantification of transcript-level expression using RNA-Seq. The recent release of Strand NGS v3.1, is equipped with the necessary features to efficiently analyse UMI-tagged NGS data helping researchers and labs involved in rare variant calling like in cfDNA based cancer diagnostics, and accurate transcript quantification with RNA-Seq.

Webinar Details:

Session 1: 13 Dec 2017, 2:30 PM IST
Session 2: 13 Dec 2017, 9:30 PM IST

Register here: http://www.strand-ngs.com/webinar_registration

Address of the bookmark: http://www.sthda.com/english/wiki/rna-seq-differential-expression-work-flow-using-deseq2

What Are Kallisto and Salmon?

At their core, both Kallisto and Salmon are tools for quantifying transcript abundance from RNA-Seq reads. They bypass traditional alignment-based methods, replacing them with pseudoalignment or quasi-mapping, which drastically speeds up the process.

• Kallisto was developed by Lior Pachter’s lab and introduced the concept of pseudoalignment using a de Bruijn graph.
• Salmon, developed by Rob Patro’s group, builds on this idea with quasi-mapping and offers additional features like advanced bias correction.

Head-to-Head Comparison

1. Algorithm

• Kallisto uses pseudoalignment, focusing on matching k-mers from reads to a transcriptome index.
• Salmon uses quasi-mapping, which adds more flexibility and can also work with aligned reads (BAM files).

2. Input and Flexibility

• Kallisto works with raw FASTQ reads and requires a custom transcriptome index.
• Salmon accepts FASTQ or pre-aligned BAM files, giving you more workflow options.

3. Bias Correction

One of Salmon’s major advantages is its sophisticated bias correction system. It corrects for:

• Sequence-specific bias
• Positional bias
• GC-content bias

Kallisto offers basic sequence bias correction but lacks the comprehensive models found in Salmon.

4. Speed and Resources

• Kallisto is blazing fast and slightly more memory-efficient.
• Salmon is still very fast, but the added features can come at a small computational cost.

5. Output and Downstream Analysis

• Both tools provide transcript-level quantifications and support bootstrapping for variance estimation.
• Salmon can also summarize counts at the gene level if provided with a mapping file (--geneMap).
• Kallisto integrates seamlessly with Sleuth for differential expression analysis.
• Salmon works well with tximport, DESeq2, edgeR, and other Bioconductor tools.

Choosing the Right Tool

Example Command Lines

Kallisto (paired-end):

kallisto quant -i transcriptome.idx -o output -b 100 sample_R1.fastq sample_R2.fastq

Salmon (paired-end, bias correction):

salmon quant -i salmon_index -l A -1 sample_R1.fastq -2 sample_R2.fastq \
  -p 8 --validateMappings --seqBias --gcBias -o output

Conclusion

Both Kallisto and Salmon are exceptional tools that have transformed RNA-Seq analysis. Your choice largely depends on your priorities—whether it's speed, accuracy, flexibility, or compatibility with downstream tools.

For many users, Salmon offers a more complete and flexible solution, especially when bias correction and gene-level outputs are essential. However, Kallisto remains a favorite for quick, accurate quantification, especially when paired with the Sleuth pipeline.

Address of the bookmark: http://hibberdlab.com/transrate/index.html

Source: Life technologies

Address of the bookmark: http://www.lifetechnologies.com/global/en/home/communities-social/blog/blogs/sequencing-solutions-to-world-health.html?cid=social_blogseries_20130829_11098264

Following are the weblink for different available browsers:

http://www.ensembl.org/index.html

http://ensemblgenomes.org/

http://genome.ucsc.edu/

http://www.ncbi.nlm.nih.gov/genome

http://www.ebi.ac.uk/genomes/

http://flybase.org/

http://cmr.jcvi.org/tigr-scripts/CMR/CmrHomePage.cgi

http://www.sanger.ac.uk/resources/databases/