Task parameters

Note

One can load, modify, and export the input file by using our effective web-based tool DP-GUI online or hosted using the command line interface dpdisp gui. All parameters below can be set in DP-GUI. By clicking “SAVE JSON”, one can download the input file.

task:

type: dict

argument path: task

command:

type: str

argument path: task/command

Shell command executed for this task. A zero exit code is treated as success. If the real application may fail before useful artifacts are synchronized, consider wrapping it and saving diagnostics to files that are listed in backward_files.

task_work_path:

type: str

argument path: task/task_work_path

Working directory of this task, specified as a relative path inside submission.work_base. Absolute paths are not supported and may break staging or remote execution. For the smallest local example, use ‘.’. If you use a subdirectory such as ‘task1/’, the command runs inside that subdirectory.

forward_files:

type: typing.List[str], optional, default: []

argument path: task/forward_files

Files to upload for this task before execution. Paths are resolved relative to this task’s task_work_path. Put per-task inputs here; files shared by all tasks belong in submission.forward_common_files.

backward_files:

type: typing.List[str], optional, default: []

argument path: task/backward_files

Files to download for this task after execution. Paths are collected from this task’s task_work_path on the execution side and synchronized back to the same relative task directory under the local staging root (typically machine.local_root/work_base).

outlog:

type: str | NoneType, optional, default: log

argument path: task/outlog

Filename used to redirect stdout inside task_work_path while the task runs. If this file is downloaded or synchronized back, it typically appears under the same relative task directory on the local side.

errlog:

type: str | NoneType, optional, default: err

argument path: task/errlog

Filename used to redirect stderr inside task_work_path while the task runs. If this file is downloaded or synchronized back, it typically appears under the same relative task directory on the local side.