quality filtering error usearch
Entering edit mode
5.9 years ago
ieie ▴ 10

Hi, after trimming bad quality ends and the primers with cutadapt I am using usearch to do some quality filltering with this little script:

for fq in out_trimmed/*_trimmed_primers2.fastq
    usearch9 -fastq_filter $fq -fastq_maxee 1 -fastq_minlen 200 -fastaout "${fq%.fastq}.fa"

but I get this error:

e../fastqfilter.cpp(132) assert failed: Qual != 0

someone knows the meaning?

could it have something to do with the steps that I take in cutadapt? thanks a lot for any help

next-gen • 1.6k views
Entering edit mode

Could you point out where is this fastqfilter.cpp, that will be helpful to locate your problem.

BTW, fastp may help you to do the trimming and filtering. fastp is a ultra-fast open-source FASTQ preprocessing tool developed in C++, with following features:

  1. filter out bad reads (too low quality, too short, or too many N...)
  2. cut low quality bases for per read in its 5' and 3' by evaluating the mean quality from a sliding window (like Trimmomatic but faster).
  3. trim all reads in front and tail
  4. cut adapters. Adapter sequences can be automatically detected,which means you don't have to input the adapter sequences to trim them.
  5. correct mismatched base pairs in overlapped regions of paired end reads, if one base is with high quality while the other is with ultra low quality
  6. preprocess unique molecular identifer (UMI) enabled data, shift UMI to sequence name.
  7. report JSON format result for further interpreting.
  8. visualize quality control and filtering results on a single HTML page (like FASTQC but faster and more informative).
  9. split the output to multiple files (0001.R1.gz, 0002.R1.gz...) to support parallel processing. Two modes can be used, limiting the total split file number, or limitting the lines of each split file.
  10. support long reads (data from PacBio / Nanopore devices). ...

The project is at:https://github.com/OpenGene/fastp

Entering edit mode
5.7 years ago
Tm ★ 1.1k

Suggest you to check the fastq statistics after using cutadapt.

If in case, whole sequence gets trimmed due to presence of adapter sequence, cutadapt does not remove the header, instead it leaves header with an empty sequence line. So it is always advisable to run cutadapt with minimum length criteria.


Login before adding your answer.

Traffic: 2186 users visited in the last hour
Help About
Access RSS

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6