Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • yaximik
    Senior Member
    • Apr 2011
    • 199

    help with GNU parallel

    Hi,

    I want to run Deconseq on a huge file using GNU parallel. Deconseq input is like this:
    Code:
    deconseq -i [% identity] -c [% coverage] -out_dir [output dir] -id [optional file id] -f [iput fasta/fastq file] -dbs [database to screen against]
    I tried configuring command like that;
    Code:
    cat /home/yaximik/input.fq | parallel --block 100M -k --pipe --recstart @M01227 --recend '\n' deconseq -i 94 -c 70 -out_dir /home/yaximik/outdir -id TESThg19 -f {} -dbs hg19
    However, deconseq exits with an error as {} is not substituted with iput.fq for -f, and {} does not work with -dbs. Is anything wrong here or can I do this differently?
  • mdobeson
    Junior Member
    • Jan 2012
    • 6

    #2
    try using the --dry-run flag to see what command parallel is attempting to run. I assume you've got some escape characters getting muddled up. Most of my my parallel commands end up chock full of backslashes

    Comment

    • tange
      Junior Member
      • Feb 2013
      • 7

      #3
      Originally posted by yaximik View Post
      Hi,

      I tried configuring command like that;
      Code:
      cat /home/yaximik/input.fq | parallel --block 100M -k --pipe --recstart @M01227 --recend '\n' deconseq -i 94 -c 70 -out_dir /home/yaximik/outdir -id TESThg19 -f {} -dbs hg19
      It is extremely rarely that --pipe and {} make sense together. You need to remember that GNU Parallel passes the input on stdin and not as a file when you use --pipe.

      So if deconseq can read from stdin you can use that. Often programs will accept '-' as file for stdin: deconseq ... -f -

      If you run GNU Linux you probably can do: deconseq ... -f /dev/stdin

      If that does not work, you first need to save stdin to a file: cat > {#}; deconseq ... -f {#}

      With the git version of GNU Parallel you can get rid of the ugly --recstart @M01227 and instead use -L4 (each record is 4 lines long).

      If #ilovefs remember to cite: parallel --bibtex
      Last edited by tange; 02-14-2013, 04:36 PM.

      Comment

      Latest Articles

      Collapse

      • GATTACAT
        Reply to Nine Things a Sample Prep Scientist Thinks About Before Sequencing
        by GATTACAT
        Love this - good data definitely starts from good input, and poor input can only give relatively poor data. I particularly like the mention of Nanodrop/absorbance based methods for quantification. It's such a toss up if you'll get an accurate reading or what amounts to a randomly generated number, and a lot of library/sequencing related issues can be traced back to poor quant.
        07-01-2026, 11:43 AM
      • 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...
        06-18-2026, 07:11 AM

      ad_right_rmr

      Collapse

      News

      Collapse

      Topics Statistics Last Post
      Started by SEQadmin2, 07-02-2026, 11:08 AM
      0 responses
      7 views
      0 reactions
      Last Post SEQadmin2  
      Started by SEQadmin2, 06-30-2026, 05:37 AM
      0 responses
      12 views
      0 reactions
      Last Post SEQadmin2  
      Started by SEQadmin2, 06-26-2026, 11:10 AM
      0 responses
      20 views
      0 reactions
      Last Post SEQadmin2  
      Started by SEQadmin2, 06-17-2026, 06:09 AM
      0 responses
      54 views
      0 reactions
      Last Post SEQadmin2  
      Working...