Output files in the input directory
1
0
Entering edit mode
6.4 years ago
thomas.e ▴ 110

Hello,

I'm using snver which creates its output next to the input files, not in the directory where the program is running. There are no options to control this. I've been racking my brain for 1.5 days to figure out how can I can gather that output. The only thing I've found is a vague post suggesting that this is not supported by CWL.

Thanks, Evan.

CWL • 1.8k views
ADD COMMENT
0
Entering edit mode

This is a question about cwl and has been correctly tagged.

ADD REPLY
0
Entering edit mode

Thanks - although I did tag it as CWL when I submitted it.

ADD REPLY
0
Entering edit mode

You did the right thing. People overlook cwl tag and may start providing suggestions outside of cwl so I added that explicit note.

ADD REPLY
1
Entering edit mode
6.3 years ago

Hello thomas.e,

This is very much supported by CWL!

See http://www.commonwl.org/user_guide/15-staging/ to learn how to stage your input files into the working directory.

Cheers,

ADD COMMENT
1
Entering edit mode

Perfect, thanks! (Ensure this value has at least 20 characters (it has 16).

ADD REPLY
0
Entering edit mode

Yes, I can stage input files into the working directory and write output files to the working directory. But, is it possible to stage a directory with input files in it and be able to write the output files to that directory? When I try to write to staged directory, I get:

cannot create regular file '...': Read-only file system

Thanks, Ngoc

ADD REPLY
0
Entering edit mode

Hello @ngoc.nguyen, I just saw your comment.

Yes, you'll need to set writable: true when using InitialWorkDirRequirement

We haven't written the user guide entry for that yet, if you would like to see that then a comment or a 👍 on https://github.com/common-workflow-language/user_guide/issues/36 will help us prioritize that.

ADD REPLY

Login before adding your answer.

Traffic: 1983 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

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

Powered by the version 2.3.6