common-workflow-language / common-workflow-language/cwltool
Use original file paths
Open
- Dominant language
- Python
- Stars
- 376
- Forks
- 255
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 12
Description
Is there any way within the existing cwltool to tell it to just perform a cwl job with the original file paths it contains rather than creating and linking to temp directories? My use case involves executing cwltool in a remote environment that contains consistently mounted remote filesystems, and it is complicated by cwltool's changing of file paths to ones generated at runtime.
Contributor guide
Assessment
This issue has not been assessed yet.