Fovus CLI Arguments
usage: fovus [-h] [--create-job-with-upload] [--delete-job] [--download-job-files] [--live-tail-file LIVE_TAIL_FILE] [--open-config-folder] [--get-job-current-status] [--silence] [--upload-files]
[--login] [--gov] [--logout] [--user] [--mount-storage] [--windows-drive {A,B,C,D,E,F,G,H,I,J,K,L,M,N,O,P,Q,R,S,T,U,V,W,X,Y,Z}] [--mount-storage-path MOUNT_STORAGE_PATH]
[--unmount-storage] [--job-config-file-path JOB_CONFIG_FILE_PATH] [--job-file-root-directory JOB_FILE_ROOT_DIRECTORY] [--local-path LOCAL_PATH] [--fovus-path FOVUS_PATH]
[--debug-mode] [--auto-delete-days AUTO_DELETE_DAYS] [--exclude-input EXCLUDE_INPUT [EXCLUDE_INPUT ...]] [--exclude-output EXCLUDE_OUTPUT [EXCLUDE_OUTPUT ...]]
[--include-input INCLUDE_INPUT [INCLUDE_INPUT ...]] [--include-output INCLUDE_OUTPUT [INCLUDE_OUTPUT ...]] [--benchmarking-profile-name BENCHMARKING_PROFILE_NAME]
[--computing-device {cpu,cpu+gpu}] [--job-name JOB_NAME] [--job-id JOB_ID] [--sync-job-files] [--job-id-list JOB_ID_LIST [JOB_ID_LIST ...]]
[--is-single-threaded-task IS_SINGLE_THREADED_TASK] [--license-timeout-hours LICENSE_TIMEOUT_HOURS] [--monolithic-override VENDOR_NAME SOFTWARE_NAME LICENSE_FEATURE NEW_LICENSE_COUNT]
[--min-gpu MIN_GPU] [--max-gpu MAX_GPU] [--min-gpu-mem-gib MIN_GPU_MEM_GIB] [--min-vcpu MIN_VCPU] [--job-max-cluster-size-vcpu JOB_MAX_CLUSTER_SIZE_VCPU] [--max-vcpu MAX_VCPU]
[--min-vcpu-mem-gib MIN_VCPU_MEM_GIB] [--output-file-list OUTPUT_FILE [OUTPUT_FILE ...]] [--output-file-option {include,exclude}]
[--remote-inputs-for-all-tasks REMOTE_INPUTS_FOR_ALL_TASK [REMOTE_INPUTS_FOR_ALL_TASK ...]] [--parallelism-config-files PARALLELISM_CONFIG_FILE [PARALLELISM_CONFIG_FILE ...]]
[--parallelism-optimization {true,false}] [--run-command RUN_COMMAND] [--scalable-parallelism {true,false}] [--scheduled-at SCHEDULED_AT] [--storage-gib STORAGE_GIB]
[--is-subject-to-available-resources {true,false}] [--allow-preemptible {true,false}] [--is-resumable-workload {true,false}] [--enable-hyperthreading {true,false}]
[--supported-cpu-architectures SUPPORTED_CPU_ARCHITECTURE [SUPPORTED_CPU_ARCHITECTURE ...]] [--time-to-cost-priority-ratio TIME_TO_COST_PRIORITY_RATIO]
[--license-consuption-profile LICENSE_CONSUMPTION_PROFILE] [--walltime-hours WALLTIME_HOURS] [--post-processing-walltime-hours POST_PROCESSING_WALLTIME_HOURS]
[--post-processing-storage-gib POST_PROCESSING_STORAGE_GI_B] [--post-processing-run-command POST_PROCESSING_RUN_COMMAND] [--post-processing-task-name POST_PROCESSING_TASK_NAME]
[--list-projects] [--project-name PROJECT_NAME] [--skip-create-job-info-folder]
Named Arguments
- --create-job-with-upload, --createJobWithUpload, -cjwu
Upload files to Fovus and create a new job. Creates .fovus folder inside the provided job file root directory, which contains data about the job and enables checking job status and downloading job files using the job file root directory. Required additional parameters: (’–job-config-file-path’, ‘–jobConfigFilePath’, ‘-jcfp’), (’–job-file-root-directory’, ‘–jobFileRootDirectory’, ‘-jfrd’).
Default: False
- --delete-job, --deleteJob, -dj
Delete job records and job files from Fovus for a job or list of jobs. Requires one of the following parameter: (’–job-id’, ‘–jobId’, ‘-jid’), (’–job-id-list’, ‘–jobIdList’, ‘-jidl’).
Default: False
- --download-job-files, --downloadJobFiles, -djf
Download job files from Fovus storage for a specified job. In case the job is running, job files will be first synced to Fovus storage and then downloaded. Requires one of the following parameters: (’–job-id’, ‘–jobId’, ‘-jid’), (’–job-file-root-directory’, ‘–jobFileRootDirectory’, ‘-jfrd’)(Note: If the job file directory is provided, the directory must contain a .fovus folder, which is automatically generated when a job is created with the Fovus CLI. If both a job file directory and job ID are provided, the job ID will be used.)
Default: False
- --live-tail-file, --liveTailFile, -ltf
Live tail a text file of a running task for a given job. Please specify the path of the file you want to monitor that start from the task. For example, taskName/path/to/file. Requires one of the following parameters: (’–job-id’, ‘–jobId’, ‘-jid’).
- --open-config-folder, --openConfigFolder, -ocf
Open the Fovus CLI config folder, located at ~/.fovus. Also adds Fovus-provided config file templates and examples to the folder for reference.
Default: False
- --get-job-current-status, --getJobCurrentStatus, -gjcs
Get job status. Requires one of the following parameters: (’–job-id’, ‘–jobId’, ‘-jid’), (’–job-file-root-directory’, ‘–jobFileRootDirectory’, ‘-jfrd’). (Note: If the job file directory is provided, the directory must contain a .fovus folder, which is automatically generated when a job is created with the Fovus CLI. If both a job file directory and job ID are provided, the job ID will be used.)
Default: False
- --silence, -s
Disable interactive CLI prompts and automatically dismiss warnings.
Default: False
- --upload-files, --uploadFiles, -uf
Upload a file or folder to Fovus Storage (My Files). Requires the following parameters: (’–local-path’, ‘–localPath’, ‘-lp’).
Default: False
- --login, -l
Login to the Fovus CLI.
Default: False
- --gov, -g
An option to add to –login when login to Fovus Gov CLI.
Default: False
- --logout, -lo
Logout the current user.
Default: False
- --user, -u
View the current user’s information.
Default: False
- --mount-storage, --mountStorage, -ms
Mount Fovus storage on your local computer under the path of /fovus-storage/ (for Linux) or <WindowsDrive>:\fovus-storage\ (for Windows) as a network file system. Job files are read-only. The mounted network file system is optimized for high throughput read to large files by multiple clients in parallel and sequential write to new files by one client at a time subject to your network speed. Supported operating systems include Windows, Ubuntu, CentOS, and Redhat. On Windows operating systems, by default, Fovus storage will be mounted to the M: drive, however, you can add the –windows-drive option to specify a different drive to mount to instead. (e.g, fovus –mount-storage –windows-drive Z). On both Linux and Windows operating systems, you can add the –mount-storage-path option to specify a custom path to mount Fovus storage to instead of the default path.
Default: False
- --windows-drive, --windowsDrive, -wd
Possible choices: A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z
For Windows operating systems only. Specify the drive to which to mount Fovus storage. Default value is “M”.
- --mount-storage-path, --mountStoragePath, -msp
Optional. Specify the path to mount Fovus storage to. The default path is /fovus-storage/. The specified path can be non-existing or an empty folder. For example, an user specified path of “/path/to/your/directory” or “/path/to/your/directory/” will mount Fovus storage to the path of /path/to/your/directory/ in the case of Linux operating systems or <WindowsDrive>:\path\to\your\directory\ in the case of Windows operating systems.
- --unmount-storage, --unmountStorage, -us
Unmount Fovus storage from your local computer.
Default: False
- --job-config-file-path, --jobConfigFilePath, -jcfp
Absolute file path to a Fovus job config JSON. Values given in this file will be used unless they are overridden by CLI input. The job config JSON must follow the structure given in the provided job config templates, which are generated when the –open-config-folder command is used and will be located in ~/.fovus/job_configs.
- --job-file-root-directory, --jobFileRootDirectory, -jfrd
Root directory of job folder. A job folder contains one or multiple task folders. Each folder uploaded under the job folder will be considered a task of the job. Each task folder is a self-contained folder containing the necessary input files and scripts to run the task. For a job that has N tasks (e.g. a DOE job with N simulation tasks), N task folders must exist under the job folder and be uploaded.
- --local-path, --localPath, -lp
Relative path with respect to the working directory or absolute path to a local file or folder to be uploaded to Fovus Storage.
- --fovus-path, --fovusPath, -fp
Relative path to the Fovus Storage directory into which the local file or folder is to be uploaded. The relative path is with respect to the root directory of My Files. This argument is optional. If not specified, the file or folder will be uploaded to the root directory of My Files
- --debug-mode, --debugMode, -dm
Enabling debug mode will keep compute nodes alive after each task execution until the task walltimeHours is reached to allow additional time for interactive debugging via SSH.
Default: False
- --auto-delete-days, --autoDeleteDays, -add
Used with create job to set the auto-delete timer. The timer starts to tick upon job completion or termination. The job will be permanently deleted when this timer expires.
Default: 0
- --exclude-input, --excludeInput, -ei
Used with create job for uploading job files.Exclude input file or folder path(s) (relative to the job root directory) that match the expression. If a file or folder path matches any expression, it will not be uploaded. Wildcard characters (, ?) can be used to specify file and directory patterns (e.g., out?/.txt specifies all .txt files in out1, out2, and out3 folders under the working directory of each task). Supported wildcards: * (matches any number of characters), ? (matches any single character). Note: if a wildcard is used in an input, the input must be surrounded by quotes (e.g., “folder?/input*”). Any number of space-separated values can be provided.
- --exclude-output, --excludeOutput, -eo
Used with download job files. Exclude output file or folder path(s) (relative to the job root directory) that match the expression. If a file or folder path matches any expression, it will not be downloaded. Wildcard characters (, ?) can be used to specify file and directory patterns (e.g., out?/.txt specifies all .txt files in out1, out2, and out3 folders under the working directory of each task). Supported wildcards: * (matches any number of characters), ? (matches any single character). Note: if a wildcard is used in an input, the input must be surrounded by quotes (e.g., “folder?/input*”). Any number of space-separated values can be provided.
- --include-input, --includeInput, -ii
Used with create job for uploading job files. Include input file or folder path(s) (relative to the job root directory) that match the expression. If a file or folder path does not match any expression, it will not be uploaded. Wildcard characters (, ?) can be used to specify file and directory patterns (e.g., out?/.txt specifies all .txt files in out1, out2, and out3 folders under the working directory of each task). Supported wildcards: * (matches any number of characters), ? (matches any single character). Note: if a wildcard is used in an input, the input must be surrounded by quotes (e.g., “folder?/input*”). Any number of space-separated values can be provided.
- --include-output, --includeOutput, -io
Used with download job files. Include output file or folder path(s) (relative to the job root directory) that match the expression. If a file or folder path does not match any expression, it will not be downloaded. Wildcard characters (, ?) can be used to specify file and directory patterns (e.g., out?/.txt specifies all .txt files in out1, out2, and out3 folders under the working directory of each task). Supported wildcards: * (matches any number of characters), ? (matches any single character). Note: if a wildcard is used in an input, the input must be surrounded by quotes (e.g., “folder?/input*”). Any number of space-separated values can be provided.
- --benchmarking-profile-name, --benchmarkingProfileName, -bpn
Fovus will optimize the cloud strategies for your job execution, including determining the optimal choices of virtual HPC infrastructure and computation parallelism, if applicable, based upon the selected benchmarking profile. For the best optimization results, select the benchmarking profile whose characteristics best resemble the workload under submission. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --computing-device, --computingDevice, -cd
Possible choices: cpu, cpu+gpu
The target computing device(s) for running your workload. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --job-name, --jobName, -jn
Job name. If not provided, a job name will be automatically generated using the current timestamp. If a job name is not provided, the job ID will be used.
- --job-id, --jobId, -jid
Job ID. Used for checking job status and downloading job files if the root file directory is not provided.
- --sync-job-files, --syncJobFiles, -sjf
Sync the current job files of a running job to Fovus storage. This can be only applied to a job in running status. Requires one of the following parameters: (’–job-id’, ‘–jobId’, ‘-jid’)
Default: False
- --job-id-list, --jobIdList, -jidl
A list of Job IDs. Used for deleting jobs in batch.
- --is-single-threaded-task, --isSingleThreadedTask, -istt
Possible choices: true, false
Set true if and only if each task uses only a single CPU thread (vCPU) at a maximum. Setting it true allows multiple tasks to be deployed onto the same compute node to maximize the task-level parallelism and the utilization of all CPU threads (vCPUs).
- --license-timeout-hours, --licenseTimeoutHours, -lth
For license-required jobs, the maximum time the job is allowed to be waiting in a queue for deployment when no license is available. A job will be terminated once the timeout timer expires. Not applicable to license-free jobs. Format: Real (e.g., 1.5). Range: ≥1. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --monolithic-override, --monolithicOverride, -mo
Override a monolithic software environment. All four values are required to reference a monolithic software and its license usage constraint. Currently, the only supported override for a monolithic software environment is the license count, and as a result, only the license count is overridden. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
Default: []
- --min-gpu, --minGpu
The minimum number of GPUs required to parallelize the execution of each task. Only values supported by the selected BP are allowed. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --max-gpu, --maxGpu
The maximum number of GPUs allowed to parallelize the execution of each task. Only values supported by the selected BP are allowed. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --min-gpu-mem-gib, --minGpuMemGiB, -mgpuMemGiB
The minimum total size of GPU memory required to support the execution of each task, summing the required memory size for each GPU. Format: Real (e.g., 10.5). Only values supported by the selected BP are allowed. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --min-vcpu, --minvCpu, --min-cpu
The minimum number of vCPUs required to parallelize the execution of each task (or multiple single-threaded tasks on each compute node if isSingleThreadedTask is true). A vCPU refers to a thread of a CPU core. Only values supported by the selected BP are allowed. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --job-max-cluster-size-vcpu, --jobMaxClusterSizevCpu, -jmcs
The maximum cluster size in terms of the total number of vCPUs allowed for parallelizing task runs in the job, which only takes into effect when isSingleThreadedTask is true. A default value of 0 means no limit.
- --max-vcpu, --maxvCpu, --max-cpu
The maximum number of vCPUs allowed to parallelize the execution of each task (or multiple single-threaded tasks on each compute node if isSingleThreadedTask is true). A vCPU refers to a thread of a CPU core. Only values supported by the selected BP are allowed. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --min-vcpu-mem-gib, --minvCpuMemGiB, -mvcpuMemGiB
The minimum total size of system memory required to support the execution of each task (or multiple single-threaded tasks on each compute node if isSingleThreadedTask is true), summing the required memory size for each vCPU. Format: Real (e.g., 10.5). Only values supported by the selected BP are allowed. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --output-file-list, --outputFileList, -ofl
Specify the output files to include or exclude from transferring back to the cloud storage using relative paths from the working directory of each task. Wildcard characters (, ?) can be used to specify file and directory patterns (e.g., out?/.txt specifies all .txt files in out1, out2, and out3 folders under the working directory of each task). Supported wildcards: * (matches any number of characters), ? (matches any single character). Note: if a wildcard is used in an input, the input must be surrounded by quotes (e.g., “folder?/input*”). Any number of space-separated values can be provided. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --output-file-option, --outputFileOption, -ofo
Possible choices: include, exclude
Specify whether the output files in outputFileList should be included or excluded from transferring back to the cloud storage after the job is completed. See outputFileList for more information. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --remote-inputs-for-all-tasks, --remoteInputsForAllTasks, --remote-inputs, -ri
Provide the URL of or path to any file or folder in Fovus storage. The files and folders specified will be included under the working directory of each task as inputs for all tasks and will be excluded from syncing back to Fovus storage as job files. If the file or folder is from My Files of Fovus Storage, a short relative path works the same as the URL. The path to a folder must end with “/”. Any number of space-separated values can be provided. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)Examples:”folderName/fileName.txt” works the same as “https://app.fovus.co/files?path=folderName/fileName.txt””folderName/” works the same as “https://app.fovus.co/folders?path=folderName””
- --parallelism-config-files, --parallelismConfigFiles, -pcf
Specify the configuration files that contain Fovus Environment Tokens, if any, using relative paths from the working directory of each task. All Fovus Environment Tokens in the configuration files specified will be resolved to values prior to task execution. Wildcard characters (, ?) can be used to specify file and directory patterns (e.g., out?/.txt specifies all .txt files in out1, out2, and out3 folders under the working directory of each task). Supported wildcards: * (matches any number of characters), ? (matches any single character). Note: if a wildcard is used in an input, the input must be surrounded by quotes (e.g., “folder?/input*”). Any number of space-separated values can be provided. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --parallelism-optimization, --parallelismOptimization, -po
Possible choices: true, false
If enabled, Fovus will determine the optimal parallelism for parallelizing the computation of each task to minimize the total runtime and cost based on the time-to-cost priority ratio (TCPR) specified. To pass in the optimal parallelism to your software program, you can directly use the Fovus environment tokens, e.g., $FovusOptVcpu, $FovusOptGpu, in your command lines or or in the input configuration files specified by the parallelismConfigFiles job config field. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --run-command, --runCommand, -rc
Specify the command lines to launch each task. The same command lines will be executed under the working directory of each task. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --scalable-parallelism, --scalableParallelism, -sp
Possible choices: true, false
A software program exhibits scalable parallelism if it can make use of more computing devices (e.g., vCPUs and/or GPUs) to parallelize a larger computation task. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --scheduled-at, --scheduledAt, -sa
The time at which the job is scheduled to be submitted. The default time zone is your local time zone. Acceptable formats include the following. 1) ISO 8601 format: “YYYY-MM-DDThh:mm:ss[.mmm]TZD” (e.g., “2020-01-01T18:30:00-05:00”). 2) Date only (defaults to upcoming 12AM your local time zone): “YYYY-MM-DD” (e.g., “2020-01-01”). 3) Time only (defaults to next upcoming time your local time zone): “hh:mmTZD” or “hh:mm” or “hh:mm AM/PM/am/pm” (e.g., “18:30-05:00” or “18:30” or “6:30 PM”). 4) Natural language time: “DD month YYYY HH:MM AM/PM/am/pm timezone” (e.g., “21 July 2013 10:15 pm PDT”).
- --storage-gib, --storageGiB, -sgib
The total size of local SSD storage required to support the execution of each task (or multiple single-threaded tasks on each compute node if isSingleThreadedTask is true). No need to include any storage space for the operating system. This is only for task storage. Format: Integer. Range: [1, 65536]. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --is-subject-to-available-resources, --isSubjectToAvailableResources, -istar
Possible choices: true, false
If true, the cloud strategy optimization will be performed subject to only the cloud resources that are currently available for provisioning, so does the optimal time-cost tradeoff resulting from the optimization. If false, the cloud strategy optimization will be performed regardless of the current availability of cloud resources. If case the optimal virtual HPC infrastructure is unavailable at the time, infrastructure provisioning will be attempted until it becomes available. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --allow-preemptible, --allowPreemptible, -ap
Possible choices: true, false
Enabling preemptible resources will restrict the maximum task Walltime allowed to 6 hours if the workload under submission is resumable, otherwise, 3 hours if not resumable. Preemptible resources are subject to reclaim by cloud service providers, resulting in the possibility of interruption to task run. Enabling preemptible resources will allow cloud strategy optimization to estimate, based on the interruption probability, the expected cost saving that can be statistically achieved by leveraging preemptible resources. In case the expected saving is meaningful, preemptible resources will be prioritized for use during the infrastructure provisioning. Any interrupted tasks due to the reclaim of preemptible resources will be re-queued for re-execution to ensure job completion. PLEASE NOTE that the expected cost saving is estimated in the statistical sense. So there is a chance that such savings may not be realized at the individual task or job level. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --is-resumable-workload, --isResumableWorkload, -irw
Possible choices: true, false
To indicate if the workload under submission supports saving work in progress and reloading the saved session to resume running from where it left off. The cloud strategy optimization will take into account if the workload is resumable to more accurately analyze the expected runtime and cost for the cloud strategies leveraging preemptible resources.(Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --enable-hyperthreading, --enableHyperthreading, --hyperthreading, -ht
Possible choices: true, false
For the CPUs that support hyperthreading, enabling hyperthreading allows two threads (vCPUs) to run concurrently on a single CPU core. For HPC workloads, disabling hyperthreading may potentially result in performance benifits with respect to the same CPU cores (e.g., 32 threads - 32 cores with hyperthreading disabled v.s. 64 threads - 32 cores with hyperthreading enabled), whereas enabling hyperthreading may potentially result in cost benifits with respect to the same parallelism (e.g., 64 threads - 32 cores with hyperthreading enabled v.s. 64 threads - 64 cores with hyperthreading disabled). (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --supported-cpu-architectures, --supportedCpuArchitectures, -sca
The CPU architecture(s) compatible with your workload. Running your workload on an incompatible CPU architecture may result in a failed job. Any number of space-separated values can be provided. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --time-to-cost-priority-ratio, --timeToCostPriorityRatio, -tcpr
Fovus will optimize the cloud strategies for your job execution to minimize the total runtime and cost based on the time-to-cost priority ratio (TCPR) specified below. TCPR defines the weights (amount of importance) to be placed on time minimization over cost minimization on a relative scale. In particular, a ratio of 1/0 or 0/1 will enforce cloud strategies to pursue the minimum achievable runtime or cost without consideration of cost or runtime, respectively. Format must be “num1/num2” where num1 + num2 = 1, 0 <= num1 <= 1, and 0 <= num2 <= 1. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --license-consuption-profile, --licenseConsumptionProfile, -lcp
licenseConsumptionProfile defines the pattern of license draw based on running conditions, such as vCPU or GPU parallelism. When an LCP is specified, the license consumption constraints for queue and auto-scaling will be automatically extracted based on the running conditions defined by the optimal cloud strategy. licenseConsumptionProfile has a higher precedence than licenseCountPerTask.(Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --walltime-hours, --walltimeHours, -wh
The maximum time each task is allowed to run. A task will be terminated without a condition once the walltime timer expires. Format: Real (e.g., 1.5). Range: >0. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --post-processing-walltime-hours, --postProcessingWalltimeHours, -ppwh
The maximum time each task is allowed to run Post Processing Task. A task will be terminated without a condition once the walltime timer expires. Format: Real (e.g., 1.5). Range: >0. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --post-processing-storage-gib, --postProcessingStorageGiB, -ppsgib
The total size of local SSD storage required to support the execution of post processing task. No need to include any storage space for the operating system. This is only for task storage. Format: Integer. Range: [1, 65536]. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --post-processing-run-command, --postProcessingRunCommand, -pprc
Specify the command lines to launch post processing task. The same command lines will be executed under the working directory of post processing task. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --post-processing-task-name, --postProcessingTaskName, -pptn
Specify the folder name of post processing task. (Note: Used for overriding job config values. If this value is provided in the job config file, this argument is optional.)
- --list-projects, --listProjects, -lpr
List all valid project names of your cost center.
Default: False
- --project-name, --projectName, -pn
The project name associated with your job. If omitted, the default project will be used. Use ‘None’ to specify no project.
- --skip-create-job-info-folder, --skipCreateJobInfoFolder, -scjif
Skip creating the job info folder. For development use only.
Default: False