Back to All

Redirecting stderr

What is the best way to redirect stderr in SBG? I see the option for stdout that adds a '>' to the command line, but what about when we want to add '2>'?

Right now, I have the '2>' added as my last argument, but I get the error...

This task ran into a problem during execution and did not finish.

Command perl miRDeep2.pl /sbgenomics/Projects/5311483a-0df2-41d1-ba6e-361dc84bc31c/sample.reads.fa /sbgenomics/Projects/5311483a-0df2-41d1-ba6e-361dc84bc31c/hg19_bowtie.fa /sbgenomics/Projects/5311483a-0df2-41d1-ba6e-361dc84bc31c/sample.reads_vs_genome.arf /sbgenomics/Projects/5311483a-0df2-41d1-ba6e-361dc84bc31c/mature.fa none /sbgenomics/Projects/5311483a-0df2-41d1-ba6e-361dc84bc31c/hairpin.fa -P -t Human 2> report.log failed with exit code 2.

...and no error log, so I'm guessing that something is angry at my redirection. Is the shell bash? And if it is not, how do I log my stderr?

Also, here is the documentation for the tool: https://www.mdc-berlin.de/36105849/en/research/research_teams/systems_biology_of_gene_regulatory_elements/projects/miRDeep/documentation#mirdeep2