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 had a quick look at the work directory of that task, and in the .qsub file
all the data files are always substitued with complete full path to the task's work
directory. Is that really necessary? The entire point of writing a task is to encapsulate
the processing locally in the work directory, to make things relocatable even accross
clusters. Full paths defeat this completely. Couldn't all operations be performed
with relative paths instead? e.g. instead of
As noticed by @prioux:
I had a quick look at the work directory of that task, and in the .qsub file
all the data files are always substitued with complete full path to the task's work
directory. Is that really necessary? The entire point of writing a task is to encapsulate
the processing locally in the work directory, to make things relocatable even accross
clusters. Full paths defeat this completely. Couldn't all operations be performed
with relative paths instead? e.g. instead of
why not :
Also, the bash commands could be split on multiple lines to make things prettier. And no need to repeat the file name in the comment
The text was updated successfully, but these errors were encountered: