# trim.seqs problem?

**URL:** https://forum.mothur.org/t/trim-seqs-problem/447
**Category:** Commands in mothur
**Created:** [January 12, 2011, 6:59pm UTC](https://forum.mothur.org/t/trim-seqs-problem/447 "2011-01-12T18:59:12Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![wichne](https://avatars.discourse-cdn.com/v4/letter/w/8c91f0/32.png) [@wichne](https://forum.mothur.org/u/wichne)
#### Post date: [January 12, 2011, 6:59pm UTC](https://forum.mothur.org/t/trim-seqs-problem/447/1 "2011-01-12T18:59:12Z")

</div>

Hi,  
I’m trying to run trim.seqs on ~440K titanium reads as follows:  
mothur \> trim.seqs(fasta=S1\_S2.fna, qfile=S1\_S2.fna.qual, qaverage=25, qthreshold=25, qtrim=T, processors=4)

It’s been running for about 80 minutes and has only generated temp files for the first four sequences despite maxing out the four assigned processors.

Is it working, or have I done something wrong?

thanks,  
Bill

---

<div class="post-metadata">

### Author: ![westcott](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.mothur.org/westcott/32/18_2.png) [@westcott](https://forum.mothur.org/u/westcott)
#### Post date: [January 14, 2011, 2:06pm UTC](https://forum.mothur.org/t/trim-seqs-problem/447/2 "2011-01-14T14:06:59Z")

</div>

In version 1.15.0, we made some changes to the internal workings of the trim.seqs command and unfortunately added and indexing error when qtrim=T, :oops: . This caused all sequences to be scrapped. The fix will be part of 1.16.0.