Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR: Output file output_dir/ does not appear to exist. #5

Open
wdecoster opened this issue Sep 2, 2021 · 1 comment
Open

ERROR: Output file output_dir/ does not appear to exist. #5

wdecoster opened this issue Sep 2, 2021 · 1 comment
Assignees
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@wdecoster
Copy link

Hi,

Hi, I am trying to run a bunch of fastq files in parallel, but I get:
ERROR: Output file output_dir/superstr_<my_identifier>/ does not appear to exist.

My command is:

cat fastq_paths.fofn | parallel -j4 --bar 'superstr --mode=fastq -o output_dir/superstr_{/}/ -t 0.56 {}_R1.fastq.gz {}_R2.fastq.gz'

Which results in e.g.

superstr --mode=fastq -o output_dir/superstr_<my_identifier> -t 0.56 /path/<my_identifier>_R1.fastq.gz /path/<my_identifier>_R2.fastq.gz

(of course with path and being reasonable names)

I also tried variations, without the trailing slash to use it as a prefix rather than a directory, but none seem to work.

I tried creating output_dir first - but that doesn't help.
I now hacked around it by doing:

cat fastq_paths.fofn | parallel -j4 --bar 'mkdir output_dir/superstr_{/}  && superstr --mode=fastq -o output_dir/superstr_{/}/ -t 0.56 {}_R1.fastq.gz {}_R2.fastq.gz'

That seems to run. But I would call that rather counterintuitive and unpractical.

So it does seem to me that -o expects an existing directory, and not like the documentation seems to suggest Note: The -o flag is an output prefix rather than a file path; "per_read.txt.gz" is appended to the prefix. Could superstr create directories if these don't exist?

Cheers,
Wouter

@lfearnley
Copy link
Contributor

Thanks for picking up on this, and I appreciate the detailed report! I'll update the documentation on this shortly - there is a fix in the works too.

@lfearnley lfearnley self-assigned this Sep 2, 2021
@lfearnley lfearnley added bug Something isn't working documentation Improvements or additions to documentation labels Sep 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants