Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • zillur
    Senior Member
    • Sep 2014
    • 106

    Filtering fastq file using prinseq, output problem

    Sir,
    I wanted to use prinseq to filter my fastq files. After running this command it seemed everything going perfect but when loading completed 100% there was output. What I am missing??
    [zillur@workstation01 Strain_GI]$ perl /home/zillur/Desktop/zillur/Tools/prinseq-lite-0.20.4/prinseq-lite.pl -verbose -fastq SRR901607_1.fastq -fastq2 SRR901607_2.fastq -min_qual_score 36 -ns_max_n 0 -noniupac -derep 124 -out_good GI_qual_fltr -out_bad null


    This gave me the following output but no filtered fastq files.

    [zillur@workstation01 Strain_GI]$ perl /home/zillur/Desktop/zillur/Tools/prinseq-lite-0.20.4/prinseq-lite.pl -verbose -fastq SRR901607_1.fastq -fastq2 SRR901607_2.fastq -min_qual_score 36 -ns_max_n 0 -noniupac -derep 124 -out_good GI_qual_fltr -out_bad null
    perl: warning: Setting locale failed.
    perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_CTYPE = "UTF-8",
    LANG = "en_US.UTF-8"
    are supported and installed on your system.
    perl: warning: Falling back to the standard locale ("C").
    perl: warning: Setting locale failed.
    perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_CTYPE = "UTF-8",
    LANG = "en_US.UTF-8"
    are supported and installed on your system.
    perl: warning: Falling back to the standard locale ("C").
    perl: warning: Setting locale failed.
    perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_CTYPE = "UTF-8",
    LANG = "en_US.UTF-8"
    are supported and installed on your system.
    perl: warning: Falling back to the standard locale ("C").
    perl: warning: Setting locale failed.
    perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_CTYPE = "UTF-8",
    LANG = "en_US.UTF-8"
    are supported and installed on your system.
    perl: warning: Falling back to the standard locale ("C").
    Estimate size of input data for status report (this might take a while for large files)
    perl: warning: Setting locale failed.
    perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_CTYPE = "UTF-8",
    LANG = "en_US.UTF-8"
    are supported and installed on your system.
    perl: warning: Falling back to the standard locale ("C").
    perl: warning: Setting locale failed.
    perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_CTYPE = "UTF-8",
    LANG = "en_US.UTF-8"
    are supported and installed on your system.
    perl: warning: Falling back to the standard locale ("C").
    done
    Parse and process input data
    status: 0 %perl: warning: Setting locale failed.
    perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_CTYPE = "UTF-8",
    LANG = "en_US.UTF-8"
    are supported and installed on your system.
    perl: warning: Falling back to the standard locale ("C").
    perl: warning: Setting locale failed.
    perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_CTYPE = "UTF-8",
    LANG = "en_US.UTF-8"
    are supported and installed on your system.
    perl: warning: Falling back to the standard locale ("C").
    done
    Clean up empty files
    Use of uninitialized value $fhmappings in unlink at /home/zillur/Desktop/zillur/Tools/prinseq-lite-0.20.4/prinseq-lite.pl line 1833.
    perl: warning: Setting locale failed.
    perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_CTYPE = "UTF-8",
    LANG = "en_US.UTF-8"
    are supported and installed on your system.
    perl: warning: Falling back to the standard locale ("C").
    perl: warning: Setting locale failed.
    perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_CTYPE = "UTF-8",
    LANG = "en_US.UTF-8"
    are supported and installed on your system.
    perl: warning: Falling back to the standard locale ("C").
    perl: warning: Setting locale failed.
    perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_CTYPE = "UTF-8",
    LANG = "en_US.UTF-8"
    are supported and installed on your system.
    perl: warning: Falling back to the standard locale ("C").
    done
    Input and filter stats:
    Input sequences (file 1): 26,419,950
    Input bases (file 1): 2,668,414,950
    Input mean length (file 1): 101.00
    Input sequences (file 2): 26,419,950
    Input bases (file 2): 2,668,414,950
    Input mean length (file 2): 101.00
    Good sequences (pairs): 0
    Good sequences (singletons file 1): 0 (0.00%)
    Good sequences (singletons file 2): 0 (0.00%)
    Bad sequences (file 1): 26,419,950 (100.00%)
    Bad bases (file 1): 2,668,414,950
    Bad mean length (file 1): 101.00
    Bad sequences (file 2): 0 (0.00%)
    Sequences filtered by specified parameters:
    min_qual_score: 52839900
    [zillur@workstation01 Strain_GI]$ ls
    SRR901607_1.fastq SRR901607_2.fastq
  • dpryan
    Devon Ryan
    • Jul 2011
    • 3478

    #2
    I imagine the minimum quality score setting is causing at least part of the problem. Try a more reasonable setting, like 5.

    Comment

    • zillur
      Senior Member
      • Sep 2014
      • 106

      #3
      Thank you very much for your kind suggestions. It seemed fine. After filtering I was trying to map the filtered fastq files using bowtie2. Mapping seems good, but when I was trying to generate variant calls in vcc format, smalls is giving me the following error message. What should I do now.

      [zillur@workstation01 Strain_NaN_Hs_2011]$ nohup samtools mpileup -uf /home/zillur/Desktop/zillur/phd/Apecomplexan/B_microti/Reference/B_microti.fasta Nan_qual_trm.sorted.bam | bcftools view -O u- > Nan_qual_trm.bcf
      nohup: ignoring input and redirecting stderr to stdout
      Failed to open -: unknown file type
      [zillur@workstation01 Strain_NaN_Hs_2011]$

      ** which file is unknown? The sorted bam?

      Comment

      • dpryan
        Devon Ryan
        • Jul 2011
        • 3478

        #4
        It's complaining about the pipe. Note that nohup mentions that it's redirecting stderr to stdout, which could seriously break things. Just don't use nohup and that alone may fix things.

        Comment

        Latest Articles

        Collapse

        • SEQadmin2
          Nine Things a Sample Prep Scientist Thinks About Before Sequencing
          by SEQadmin2


          I’m not a sequencing expert. I’m a purification scientist who uses NGS to evaluate workflows my group develops. With this perspective, we think about the sample first and the NGS workflow second. The sequencer is an exceptionally honest reporter, but it can only report on what you give it, so whether you get clean, interpretable data from an NGS workflow is largely determined before you begin.


          Here are nine questions we think about, in roughly the order they matter, before...
          Yesterday, 07:11 AM
        • SEQadmin2
          From Collection to Sequencing: Why Sample Preparation and Preservation Define Sequencing Data
          by SEQadmin2


          Data variability is still an issue in sequencing technologies despite the advances in reproducibility and accuracy of these platforms. But the problem does not originate in the sequencing itself, but in the previous steps, before the sample reaches the sequencer.


          The first step is collection, followed by preservation and sample preparation for analysis. Most scientists overlook those steps, but not being careful might just be skewing the experiment’s results.
          ...
          06-02-2026, 10:05 AM
        • SEQadmin2
          Single-Cell Sequencing at an Inflection Point: Early Impacts of New Platforms and Emerging Trends
          by SEQadmin2


          With the launch of new single-cell sequencing platforms in 2026, the field stands at an exciting inflection point. This article surveys the most impactful advances in the field and discusses how they’re reshaping research in cancer, immunology, and beyond.


          Introduction

          Single-cell sequencing technologies have undergone remarkable advances over the past decade, transitioning from low-throughput experimental approaches to highly scalable platforms capable of...
          05-22-2026, 06:42 AM

        ad_right_rmr

        Collapse

        News

        Collapse

        Topics Statistics Last Post
        Started by SEQadmin2, 06-17-2026, 06:09 AM
        0 responses
        20 views
        0 reactions
        Last Post SEQadmin2  
        Started by SEQadmin2, 06-09-2026, 11:58 AM
        0 responses
        38 views
        0 reactions
        Last Post SEQadmin2  
        Started by SEQadmin2, 06-05-2026, 10:09 AM
        0 responses
        44 views
        0 reactions
        Last Post SEQadmin2  
        Started by SEQadmin2, 06-04-2026, 08:59 AM
        0 responses
        49 views
        0 reactions
        Last Post SEQadmin2  
        Working...