Command usage:

SyQADA expects the directory in which it is invoked to be the working directory of a project, not the bin directory in which the executable sits. Exceptions to this are syqada –help, syqada –version, and syqada manual, which will bring up the manual in a browser regardless of your current working directory.

SyQADA is constructed as a collection of modules called by a single driver. The following sub-commands may be used as the first argument to the syqada command. This first list of sub-commands does not require a batch directory as an argument.

  • syqada auto: Examine the project and run it if there are no errors.
  • syqada status: Examine the project and report its status.
  • –version: Report syqada version
  • –help: Print help. –help –help opens the manual.

The sub-commands in the second list require the name of a batch directory as the second argument.

  • syqada batch: Build a task directory, write the job scripts, and run them.
  • syqada manage: Examine a task directory
  • syqada fix: Examine a task directory and correct mishandled jobs and logs.
  • syqada reset: Clean up a task directory so that it is ready to initialize from metadata.
  • syqada purge: Altogether remove a task directory so that it can be entirely recreated.
  • syqada repend: Move failed jobs to PENDING and clean up their logs from the LOGS directory.
  • syqada errors: Report errors on a task directory.
  • syqada stderr: Report a standard error output for jobs in a task directory.
  • syqada stdout: Report a standard output for jobs in a task directory.

In both lists, each subcommand takes additional parameters identified by two leading dashes. Distinct prefixes of the parameter names are acceptable, for example:

syqada batch 01-step-one --step initialize


syqada batch 01-step-one --step init

have identical effect.