<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[qiime trim truncate]]></title><description><![CDATA[<p dir="auto"><a href="https://forum.qiime2.org/t/nomenclature-issue-trimming-vs-truncation/21101/11" rel="nofollow ugc">https://forum.qiime2.org/t/nomenclature-issue-trimming-vs-truncation/21101/11</a></p>
<p dir="auto">Trimming: The number of base pairs that will be removed from either the 3' or the 5' end. In QIIME 2, you'll most commonly see trim-left (which will trim off the requested number of base pairs from the 5' end), but in qiime feature-classifier extract-reads, there is also a trim-right parameter, which refers to the 3' end.</p>
<p dir="auto">Truncating: The position at which reads will be truncated (counting from the 5' end). Reads that are shorter than the value provided will be discarded. The command you'll see this action represented by within QIIME 2 is trunc-len. Something to note is that in the denoising pipelines within the QIIME 2 core framework, <strong>truncation occurs before trimming.</strong></p>
]]></description><link>http://an.forum.genostack.com/topic/908/qiime-trim-truncate</link><generator>RSS for Node</generator><lastBuildDate>Sat, 13 Jun 2026 10:43:37 GMT</lastBuildDate><atom:link href="http://an.forum.genostack.com/topic/908.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 29 May 2023 09:07:24 GMT</pubDate><ttl>60</ttl></channel></rss>