.. _syqada_enqueue:

###################
syqada enqueue
###################

  >>> syqada enqueue --script scriptname
  >>> syqada enqueue --bash_script scriptname
  >>> syqada enqueue -c command with arbitrary arguments
  >>> syqada enqueue --command command with arbitrary arguments

Using either *scriptname* or *command with arbitrary arguments*, build
and a cluster-compatible jobscript and submit it to the cluster unless
--nosubmit is specified. SyQADA parameter expansion will be performed
on any {parameters_with_braces} in the script or arbitrary arguments
(these will need to be quoted on the command line when using -c or --command).

With --payload filename, write the jobscript to file *filename*.

The numerous SyQADA parameters used to expand parameters scripts from config,
task, and protocol files can be specified as command options. They
include::

     --queue
     --gb_memory
     --processors
     --walltime 
     --project 
     --inputdir
     --tmpdir
     --outputdir
     --log_prefix
     --split

These arguments have special meaning::

     --cwd The directory in which the job should be run
     --interface The queueing interface to use
     --verbose Whether to print additional information during construction and submission.
     --local [SERVER | WORKSTATION | LAPTOP | LSFHEADNODE | PBSHEADNODE ] Which local queueing to use (sort of pointless, but there it is -- you can perfectly well specify --interface LOCAL)

The special argument options can be used to specify template
parameters that are populated in the same way the parameters in
config, task, and protocol files are, potentially allowing one-time
use of existing SyQADA templates, or prototyping of new templates::

     --options parameter1=value1 parameter2=value2 ...