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

Execution directory variable name #7254

Open
wadudmiah opened this issue Nov 15, 2023 · 1 comment
Open

Execution directory variable name #7254

wadudmiah opened this issue Nov 15, 2023 · 1 comment

Comments

@wadudmiah
Copy link

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,

@wadudmiah
Copy link
Author

wadudmiah commented Nov 15, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant