Ciop-simjob¶

• Table of contents
• Ciop-simjob
  • NAME
  • SYNOPSIS
  • DESCRIPTION
  • OPTIONS
  • EXIT STATUS
  • EXAMPLES
    • Example 1. Get the workflow node IDs
    • Example 2. First run of a given workflow node
    • Example 3. Following runs of a given workflow node (deletes the results of a previous run)
  • SEE ALSO
  • AUTHOR

NAME¶

ciop-simjob - runs individually a node of the sample workflow of the application

SYNOPSIS¶

/usr/bin/ciop-simjob {node} [option...]

DESCRIPTION¶

ciop-simjob runs individually a node of the sample workflow of the application. This is useful to test unitarily a job.

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 STATUS¶

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¶

ciop-simwf

AUTHOR¶

Terradue Srl