You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a task that depends on files generated by a dependent job, e.g. job A generates A.out and job B needs A.out in the current working directory. The applications expect to see them in the current working directory, so I think I need to copy them over. However, is there a WDL variable that stores the execution directory so I can copy those files over? Or is there another way to achieve this?
Regards,
The text was updated successfully, but these errors were encountered:
For the input files for a job: can you use the glob notation (*), as there could be hundreds of files that are required for a task, and likewise for a job that generates files? e.g. images*.png
I have a task that depends on files generated by a dependent job, e.g. job A generates A.out and job B needs A.out in the current working directory. The applications expect to see them in the current working directory, so I think I need to copy them over. However, is there a WDL variable that stores the execution directory so I can copy those files over? Or is there another way to achieve this?
Regards,
The text was updated successfully, but these errors were encountered: