Ciop-simjob » History » Revision 5
« Previous |
Revision 5/6
(diff)
| Next »
Herve Caumont, 2013-09-21 00:26
ciop-simjob CLI reference¶
- Table of contents
- ciop-simjob CLI reference
Name¶
ciop-simjob -- runs a specified node of the application workflow. This is useful to perform unit test for a job.
Synopsis¶
ciop-simjob {node} [option]
Options¶
node
This must be the id of the node registered in the workflow "sample" in the file ${_CIOP_APPLICATION_PATH}/application.xml
-i input
directory name or file name containing the input to map to the executable via stdin. This path must be relative to share path ${_CIOP_SHARE_PATH}.
By default the value is setup to find the best input for your job (more info in the documentation)
-o output
directory name where to put the output file with the stdout of the execution This directory must not exist (or use -f) and must be relative to share path ${_CIOP_SHARE_PATH}
By default the value is setup to find the best output dir for next job (more info in the documentation)
-f
delete existing output directory if it exists (default: no)
-n
list the node ids of the workflow
-p name value
define a processing parameter for the simulation. If a default value is defined in the application.xml, it will be overwritten (not yet implemented)
Exit codes¶
ciop-simjob
command exits 0 on success, and >0 if an error occurs.
Examples¶
Example 1. Get the workflow node IDs¶
ciop-simjob -n
Example 2. First run of a given workflow node¶
ciop-simjob node_name
Example 3. Following runs of a given workflow node (deletes the results of a previous run)¶
ciop-simjob -f node_name
See also¶
Updated by Herve Caumont about 11 years ago · 5 revisions