CWL Workflow removing input files
1
0
Entering edit mode
5.8 years ago
Tom ▴ 540

I want use deepbinner as the first step of a workflow. Deepbinner scans fast5 files for barcodes and then moves them to different folders accordingly. My problem is that files are sorted into a temp directory created by cwltool and disappear from their original location. The temporary files are then processed further and i get my desired output. However, all my raw data is lost.

Is there a way to prevent this behavior? I would like for the workflow to not alter the input directory at all, but i don't know how to make sure deepbinner only gets a copy of the directory.

cwl Deepbinner • 1.4k views
ADD COMMENT
1
Entering edit mode

Hello Tom,

Which CWL runner are you using, and which version is it?

Do your CWL descriptions use the DockerRequirement?

Can you share a link to view your CWL descriptions?

ADD REPLY
0
Entering edit mode

I'm using cwltool version is 1.0.20181217162649 I am still struggling with getting my stuff to work with docker, so for now there is no DockerRequirement.

I added the relevant code to a repository: *edit: repository made private again.

Thank you for taking the time to help.

ADD REPLY
1
Entering edit mode

In case it is of interest: When running the tool in Docker it fails because it cannot move the input files out of their directories.

Using InitialWorkDirRequirement with writable: true solves the problem.

ADD REPLY
1
Entering edit mode
5.8 years ago
Tom ▴ 540

Using InitialWorkDirRequirement with a writable: field set to true solves the problem. CWLtool seems to copy all files into a temporary directory and deepbinner is then able to move them out of there.

requirements:
  InlineJavascriptRequirement: {}
  InitialWorkDirRequirement:
    listing:
      - entry: $(inputs.reads_directory)
        writable: true
ADD COMMENT

Login before adding your answer.

Traffic: 2332 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