<?xml version='1.0'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:atom="http://www.w3.org/2005/Atom" >
<channel>
	<title><![CDATA[BOL: Related items]]></title>
	<link>https://bioinformaticsonline.com/related/36630?offset=80</link>
	<atom:link href="https://bioinformaticsonline.com/related/36630?offset=80" rel="self" type="application/rss+xml" />
	<description><![CDATA[]]></description>
	
	<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/blog/view/44758/the-ifs-and-buts-of-ngs-quality-control-and-trimming</guid>
	<pubDate>Thu, 02 Jan 2025 20:11:07 -0600</pubDate>
	<link>https://bioinformaticsonline.com/blog/view/44758/the-ifs-and-buts-of-ngs-quality-control-and-trimming</link>
	<title><![CDATA[The &quot;Ifs&quot; and &quot;Buts&quot; of NGS Quality Control and Trimming]]></title>
	<description><![CDATA[<p>Next-Generation Sequencing (NGS) has revolutionized biological research, providing vast amounts of data for a wide range of applications. However, the reliability of NGS analyses heavily depends on the quality of raw sequencing data. Quality control (QC) and trimming are critical preprocessing steps that can make or break your downstream analyses. In this blog, we explore the "ifs" (why you should perform QC and trimming) and the "buts" (challenges or considerations) of this vital step in NGS workflows.</p><h3><strong>The "Ifs" of NGS QC and Trimming</strong></h3><ol>
<li>
<p><strong>Ensures Data Integrity</strong><br />If you want to minimize errors in downstream analyses, QC and trimming remove low-quality reads and bases, ensuring high-confidence data. This step is essential for reliable variant calling, assembly, and other applications.</p>
</li>
<li>
<p><strong>Removes Contaminants</strong><br />If adapter sequences or contaminants are present in the raw reads, trimming can eliminate them. This prevents issues like misalignment or incorrect biological interpretations, ensuring cleaner data for analysis.</p>
</li>
<li>
<p><strong>Improves Mapping and Assembly</strong><br />If your goal is better alignment to a reference genome or improved de novo assembly, trimming low-quality bases and adapters is critical. High-quality reads map more efficiently and generate more accurate assemblies.</p>
</li>
<li>
<p><strong>Reduces Computational Load</strong><br />If you want to save computational resources, trimming reduces the dataset size, which speeds up processing and analysis. Clean datasets mean less computational time spent on processing low-quality data.</p>
</li>
<li>
<p><strong>Prepares for Standardized Analyses</strong><br />If your project involves multiple datasets, QC and trimming ensure uniformity across them. This standardization makes comparisons valid and reproducible, particularly in large collaborative studies.</p>
</li>
</ol><h3><strong>The "Buts" of NGS QC and Trimming</strong></h3><ol>
<li>
<p><strong>Risk of Over-Trimming</strong><br />But excessive trimming can lead to the loss of informative sequences, reducing read depth and potentially discarding biologically relevant data. This is especially critical in studies with limited sequencing depth.</p>
</li>
<li>
<p><strong>Bias Introduction</strong><br />But trimming algorithms might introduce biases, especially if they inadvertently remove sequences with specific biological patterns. This can skew results and compromise biological insights.</p>
</li>
<li>
<p><strong>Loss of Context in Paired-End Reads</strong><br />But trimming one read in a pair more than the other can lead to loss of pairing information. This complicates downstream analyses that rely on paired-end data, such as structural variant detection.</p>
</li>
<li>
<p><strong>Time and Resource Intensive</strong><br />But running QC and trimming for large datasets can be computationally expensive and time-consuming. As sequencing depth increases, preprocessing becomes a bottleneck in the analysis pipeline.</p>
</li>
<li>
<p><strong>Variable Standards</strong><br />But the criteria for trimming (e.g., quality threshold, minimum read length) can vary between tools and datasets. This variability may affect reproducibility and comparability of results across studies.</p>
</li>
</ol><h3><strong>Balancing the "Ifs" and "Buts"</strong></h3><p>To maximize the benefits of QC and trimming while mitigating the challenges, consider the following best practices:</p><ul>
<li>
<p><strong>Use QC Tools Wisely:</strong> Start with tools like <strong>FastQC</strong> to identify quality issues in your raw data. Visualizing quality metrics helps tailor your trimming parameters.</p>
</li>
<li>
<p><strong>Choose Reliable Trimming Tools:</strong> Tools like <strong>Trimmomatic</strong>, <strong>Cutadapt</strong>, and <strong>BBduk</strong> offer adaptive and customizable trimming options. Select one that aligns with your dataset and project goals.</p>
</li>
<li>
<p><strong>Set Reasonable Parameters:</strong> Avoid over-trimming by setting quality thresholds and minimum read lengths that balance data retention and quality improvement.</p>
</li>
<li>
<p><strong>Test Downstream Effects:</strong> Validate the impact of QC and trimming on downstream analyses, such as alignment efficiency, variant calling accuracy, or assembly quality.</p>
</li>
<li>
<p><strong>Document Your Workflow:</strong> Maintain detailed records of the parameters and tools used for QC and trimming. This ensures reproducibility and enables better troubleshooting.</p>
</li>
</ul><h3><strong>Conclusion</strong></h3><p>NGS quality control and trimming are essential steps to ensure reliable and accurate data for analysis. While the "ifs" highlight the clear benefits of these steps, the "buts" remind us of the potential pitfalls. By adopting best practices and carefully balancing these considerations, you can optimize your preprocessing workflow and unlock the full potential of your sequencing data.</p>]]></description>
	<dc:creator>BioStar</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/38176/asciigenome-genome-browser-based-on-command-line-interface-and-designed-for-running-from-console-terminals</guid>
	<pubDate>Fri, 09 Nov 2018 13:50:04 -0600</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/38176/asciigenome-genome-browser-based-on-command-line-interface-and-designed-for-running-from-console-terminals</link>
	<title><![CDATA[ASCIIGenome: genome browser based on command line interface and designed for running from console terminals.]]></title>
	<description><![CDATA[<p><code>ASCIIGenome</code>&nbsp;is a genome browser based on command line interface and designed for running from console terminals.</p>
<p>Since&nbsp;<code>ASCIIGenome</code>&nbsp;does not require a graphical interface it is particularly useful for quickly visualizing genomic data on remote servers while offering flexibility similar to popular GUI viewers like&nbsp;<a href="https://www.broadinstitute.org/igv/">IGV</a>.</p>
<p><span>Documentation</span>&nbsp;is at&nbsp;<a href="http://asciigenome.readthedocs.io/en/latest/">readthedocs/asciigenome</a>.</p>
<p>&nbsp;</p><p>Address of the bookmark: <a href="https://github.com/dariober/ASCIIGenome" rel="nofollow">https://github.com/dariober/ASCIIGenome</a></p>]]></description>
	<dc:creator>Neel</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/pages/view/42275/frequent-parameters-for-bioinformatics-tools</guid>
	<pubDate>Tue, 27 Oct 2020 19:42:32 -0500</pubDate>
	<link>https://bioinformaticsonline.com/pages/view/42275/frequent-parameters-for-bioinformatics-tools</link>
	<title><![CDATA[Frequent parameters for bioinformatics tools !]]></title>
	<description><![CDATA[<div><div>Third party executable parameters and options.</div><div>&nbsp;</div><div>Trimmomatic</div><div>&nbsp;</div><div>&ldquo;ILLUMINACLIP:...:2:30:10&rdquo;</div><div>&ldquo;LEADING:15&rdquo;</div><div>&ldquo;TRAILING:15&rdquo;</div><div>&ldquo;SLIDINGWINDOW:4:20&rdquo;</div><div>&ldquo;MINLEN:20&rdquo;</div><div>&ldquo;TOPHRED33&rdquo;</div><div>&nbsp;</div><div>Filtlong</div><div>--min_length 500</div><div>--min_mean_q 85</div><div>--min_window_q 65</div><div>&nbsp;</div><div>FastQ Screen</div><div>--aligner bowtie2' (bwa for PacBio)</div><div>--subset 1000 (for PacBio)</div><div>&nbsp;</div><div>SPAdes</div><div>--careful</div><div>--disable-gzip-output</div><div>--cov-cutoff auto</div><div>--phred-offset 33</div><div>&nbsp;</div><div>HGAP</div><div>Pbalign.task_options.min_accuracy: 70</div><div>Pbalign.task_options.no_split_subreads: false</div><div>Genomic_consensus.task_options.min_confidence: 40</div><div>falcon_ns.task_options.HGAP_GenomeLength_str:</div><div>6000000</div><div>Pbcoretools.task_options.read_length: 0</div><div>Genomic_consensus.task_options.use_score: 0</div><div>Pbalign.task_options.min_length: 50</div><div>Pbalign.task_options.algorithm_options: --minMatch 12</div><div>--bestn 10 --minPctSimilarity 70.0</div><div>Pbalign.task_options.hit_policy: randombest</div><div>Pbcoretools.task_options.other_filters: rq &gt;= 0.7</div><div>Pbalign.task_options.concordant: false</div><div>Genomic_consensus.task_options.min_coverage: 5</div><div>falcon_ns.task_options.HGAP_SeedCoverage_str: 30</div><div>falcon_ns.task_options.HGAP_AggressiveAsm_bool: false</div><div>Genomic_consensus.task_options.algorithm: best</div><div>falcon_ns.task_options.HGAP_SeedLengthCutoff_str: -1</div><div>Genomic_consensus.task_options.diploid: false</div><div>&nbsp;</div><div>MeDuSa</div><div>-random 100</div><div>&nbsp;</div><div>Prokka</div><div>--usegenus</div><div>--force</div><div>--addgenes</div><div>--rfam</div><div>--rawproduct</div><div>&nbsp;</div><div>cmsearch (taxonomy, 16S)</div><div>--rfam</div><div>--noali</div><div>&nbsp;</div><div>blastn (taxonomy, 16S)</div><div>-evalue 1E-10</div><div>&nbsp;</div><div>blastn (MLST)</div><div>-ungapped</div></div><div><div>-dust no</div><div>-evalue 1E-20</div><div>-word_size 32</div><div>-culling_limit 2</div><div>-perc_identity 95</div><div>&nbsp;</div><div>blastp (VF)</div><div>-culling_limit 2</div><div>&nbsp;</div><div>RGI (ABR)</div><div>--input_type contig</div><div>&nbsp;</div><div>bowtie2 (mapping)</div><div>--sensitive</div><div>&nbsp;</div><div>minimap2 (mapping)</div><div>-a</div><div>-x map-ont</div><div>&nbsp;</div><div>samtools mpileup (SNP&nbsp;detection)</div><div>-uRI</div><div>&nbsp;</div><div>bcftools call (SNP detection)</div><div>--variants-only</div><div>--skip-variants indels</div><div>--output-type v</div><div>--ploidy 1</div><div>-c</div><div>&nbsp;</div><div>SNPsift filter (SNP detection)</div><div>"( QUAL &gt;= 30 ) &amp; (( na FILTER ) | (FILTER = 'PASS')) &amp;</div><div>( DP &gt;= 20 ) &amp; ( MQ &gt;= 20 )"</div><div>&nbsp;</div><div>SNPeff ann (SNP detection)</div><div>-nodownload</div><div>-no-intron</div><div>-no-downstream</div><div>-no SPLICE_SITE_REGION</div><div>-upDownStreamLen 250</div><div>&nbsp;</div><div>bcftools consensus</div><div>(phylogenetic tree)</div><div>--haplotype 1</div><div>&nbsp;</div><div>fasttreemp</div><div>-nt</div><div>-boot 100</div><div>&nbsp;</div><div>roary</div><div>-e</div><div>-n</div><div>-cd 100</div><div>-g 100000</div></div>]]></description>
	<dc:creator>BioStar</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/36508/mitobim-mitochondrial-baiting-and-iterative-mapping</guid>
	<pubDate>Tue, 08 May 2018 04:15:25 -0500</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/36508/mitobim-mitochondrial-baiting-and-iterative-mapping</link>
	<title><![CDATA[MITObim - mitochondrial baiting and iterative mapping]]></title>
	<description><![CDATA[<p>This document contains instructions on how to use the MITObim pipeline described in Hahn et al. 2013. The full article can be found&nbsp;<a href="http://nar.oxfordjournals.org/content/41/13/e129" title="MITObim full article at NAR">here</a>. Kindly cite the article if you are using MITObim in your work. The pipeline was originally developed for&nbsp;<span>Illumina</span>&nbsp;data, but thanks to the versatility of the MIRA assembler, MITObim supports in principle also data from the&nbsp;<span>Iontorrent</span>,&nbsp;<span>454</span>&nbsp;and&nbsp;<span>PacBio</span>&nbsp;sequencing platforms.</p>
<p>Below you can find a few basic tutorials for how to run MITObim and I encorage you to give them a try with the testdata that comes with this Repo, just to make sure everything is running smoothly on your system. It'll only take a few minutes and will potentially safe you a lot of time down the line.</p>
<p>I provide further examples&nbsp;<a href="https://github.com/chrishah/MITObim/tree/master/examples">here</a>&nbsp;as Jupyter notebooks. Get in touch if you feel like sharing your particular MITObim solution and I'd be happy to put it up here, too!</p><p>Address of the bookmark: <a href="https://github.com/chrishah/MITObim" rel="nofollow">https://github.com/chrishah/MITObim</a></p>]]></description>
	<dc:creator>Rahul Nayak</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/37800/heatmapper-web-enabled-heat-mapping-for-all</guid>
	<pubDate>Mon, 01 Oct 2018 08:34:41 -0500</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/37800/heatmapper-web-enabled-heat-mapping-for-all</link>
	<title><![CDATA[Heatmapper: web-enabled heat mapping for all]]></title>
	<description><![CDATA[<p><span>Heatmapper is a freely available web server that allows users to interactively visualize their data in the form of heat maps through an easy-to-use graphical interface. Heatmapper is a versatile tool that allows users to easily create a wide variety of heat maps for many different data types and applications. Heatmapper allows users to generate, cluster and visualize: </span></p>
<p><span>1)&nbsp;</span><span>expression-based heat maps</span><span>&nbsp;from transcriptomic, proteomic and metabolomic experiments; 2)&nbsp;</span><span>pairwise distance maps</span><span>; </span></p>
<p><span>3)&nbsp;</span><span>correlation maps</span><span>; </span></p>
<p><span>4)&nbsp;</span><span>image overlay heat maps</span><span>; </span></p>
<p><span>5)&nbsp;</span><span>latitude and longitude heat maps</span><span>&nbsp;and </span></p>
<p><span>6)&nbsp;</span><span>geopolitical (choropleth) heat maps</span><span>. </span></p>
<p><span>Heatmapper offers a number of simple and intuitive customization options for easy adjustments to each heat map&rsquo;s appearance and plotting parameters. Heatmapper also allows users to interactively explore their numeric data values by hovering their cursor over each heat map, or by using a searchable/sortable data table view.</span></p>
<p><span>Ref&nbsp;https://www.ncbi.nlm.nih.gov/pubmed/27190236</span></p><p>Address of the bookmark: <a href="http://www2.heatmapper.ca/" rel="nofollow">http://www2.heatmapper.ca/</a></p>]]></description>
	<dc:creator>Jit</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/news/view/11144/scientists-map-17294-proteins-produced-in-human-body</guid>
	<pubDate>Thu, 29 May 2014 01:57:55 -0500</pubDate>
	<link>https://bioinformaticsonline.com/news/view/11144/scientists-map-17294-proteins-produced-in-human-body</link>
	<title><![CDATA[Scientists map 17,294 proteins produced in human body]]></title>
	<description><![CDATA[<p>Indian scientists missed the genomic profiling bus, but they've more than made up for it by creating the first human proteome map which is an extension of the genomic study. Till now, here is no direct equivalent for the human proteome. But recently two groups present mass spectrometry-based analysis of human tissues, body fluids and cells mapping the large majority of the human proteome.</p><p>The Indian scientists working in Bangalore, along with their American counterparts, have mapped more than 17,000 proteins in 30 organs of the human body. Just like the human genome was sequenced around the turn of the millennium, this is an equivalent mapping of the human proteome.<br /><br />The researcher estimated there are around 20,500 proteins in the human body. These scientists have profiled around 17,294, which account for around 84% of the total proteins. Apart from this, the team also traced around 2,500 of 3,000 proteins that had been categorised as "missing proteins".</p><p>The work, done by group of Indian scientists, and Johns Hopkins University, published in the renowned journal Nature ( http://www.nature.com/nature/journal/v509/n7502/full/nature13302.html ). Of the 72 people who worked on the project, 46 are Indians.</p><p>Reference:</p><p>http://www.nature.com/nature/journal/v509/n7502/full/nature13302.html</p><p>http://www.proteinatlas.org/ -The antibody-based Human Protein Atlas programme</p><p>http://www.humanproteomemap.org/ -Proteogenomic analysis by identifying translated proteins from annotated pseudogenes, non-coding RNAs and untranslated regions.</p><p>https://www.proteomicsdb.org/ -Assembled protein evidence for 18,097 genes in ProteomicsDB</p><p>&nbsp;</p>]]></description>
	<dc:creator>Jit</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/37545/ncbi-magic-blast</guid>
	<pubDate>Tue, 14 Aug 2018 18:11:11 -0500</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/37545/ncbi-magic-blast</link>
	<title><![CDATA[NCBI Magic-BLAST]]></title>
	<description><![CDATA[<p>Magic-BLAST is a tool for mapping large next-generation RNA or DNA sequencing runs against a whole genome or transcriptome. Each alignment optimizes a composite score, taking into account simultaneously the two reads of a pair, and in case of RNA-seq, locating the candidate introns and adding up the score of all exons. This is very different from other versions of BLAST, where each exon is scored as a separate hit and read-pairing is ignored.</p>
<p>Magic-BLAST incorporates within the NCBI BLAST code framework ideas developed in the NCBI Magic pipeline, in particular hit extensions by local walk and jump&nbsp;<a href="http://www.ncbi.nlm.nih.gov/pubmed/26109056">(http://www.ncbi.nlm.nih.gov/pubmed/26109056)</a>, and recursive clipping of mismatches near the edges of the reads, which avoids accumulating artefactual mismatches near splice sites and is needed to distinguish short indels from substitutions near the edges.</p>
<p>&nbsp;</p><p>Address of the bookmark: <a href="https://ncbi.github.io/magicblast/" rel="nofollow">https://ncbi.github.io/magicblast/</a></p>]]></description>
	<dc:creator>Jit</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/34528/cope-an-accurate-k-mer-based-pair-end-reads-connection-tool-to-facilitate-genome-assembly</guid>
	<pubDate>Wed, 06 Dec 2017 02:08:14 -0600</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/34528/cope-an-accurate-k-mer-based-pair-end-reads-connection-tool-to-facilitate-genome-assembly</link>
	<title><![CDATA[COPE: an accurate k-mer-based pair-end reads connection tool to facilitate genome assembly]]></title>
	<description><![CDATA[<p><span>An efficient tool called Connecting Overlapped Pair-End (COPE) reads, to connect overlapping pair-end reads using k-mer frequencies. We evaluated our tool on 30&times; simulated pair-end reads from Arabidopsis thaliana with 1% base error. COPE connected over 99% of reads with 98.8% accuracy, which is, respectively, 10 and 2% higher than the recently published tool FLASH. When COPE is applied to real reads for genome assembly, the resulting contigs are found to have fewer errors and give a 14-fold improvement in the N50 measurement when compared with the contigs produced using unconnected reads.</span></p><p>Address of the bookmark: <a href="ftp://ftp.genomics.org.cn/pub/cope" rel="nofollow">ftp://ftp.genomics.org.cn/pub/cope</a></p>]]></description>
	<dc:creator>Jit</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/36456/alpaca-a-hybrid-strategy-for-assembly-of-genomic-dna-shotgun-sequencing-reads</guid>
	<pubDate>Mon, 30 Apr 2018 04:38:40 -0500</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/36456/alpaca-a-hybrid-strategy-for-assembly-of-genomic-dna-shotgun-sequencing-reads</link>
	<title><![CDATA[ALPACA: A hybrid strategy for assembly of genomic DNA shotgun sequencing reads.]]></title>
	<description><![CDATA[<p><span>ALPACA requires Celera Assembler 8.3 or later. It is recommended to build Celera Assembler from source. (Why? The pre-built binaries CA_8.3rc1 and CA8.3rc2 will work for any large data set.&nbsp;</span></p>
<p><span>Detail paper at&nbsp;https://bmcgenomics.biomedcentral.com/articles/10.1186/s12864-017-3927-8</span></p><p>Address of the bookmark: <a href="https://github.com/VicugnaPacos/ALPACA" rel="nofollow">https://github.com/VicugnaPacos/ALPACA</a></p>]]></description>
	<dc:creator>Seema Singh</dc:creator>
</item>
<item>
	<guid isPermaLink="true">https://bioinformaticsonline.com/bookmarks/view/36635/circlator-automated-circularization-of-genome-assemblies-using-long-sequencing-reads</guid>
	<pubDate>Tue, 15 May 2018 09:42:32 -0500</pubDate>
	<link>https://bioinformaticsonline.com/bookmarks/view/36635/circlator-automated-circularization-of-genome-assemblies-using-long-sequencing-reads</link>
	<title><![CDATA[Circlator: automated circularization of genome assemblies using long sequencing reads]]></title>
	<description><![CDATA[A tool to circularize genome assemblies. The algorithm and benchmarks are described in the Genome Biology manuscript. 

Citation: "Circlator: automated circularization of genome assemblies using long sequencing reads", Hunt et al, Genome Biology 2015 Dec 29;16(1):294. doi: 10.1186/s13059-015-0849-0. PMID: 26714481.<p>Address of the bookmark: <a href="http://sanger-pathogens.github.io/circlator/" rel="nofollow">http://sanger-pathogens.github.io/circlator/</a></p>]]></description>
	<dc:creator>Poonam Mahapatra</dc:creator>
</item>

</channel>
</rss>