You are here


SWIF1 and SWIF2 have essentially the same command line interface. However, SWIF2 has different status information output from what SWIF1 produces status output. For example, in SWIF2, swif status adds several fields, such as finer details about status of dispatched attempts, and removes a few such as individual error type counts. The status output can be in the following formats: simple text format, XML, and JSON. For those who parse the status output programmatically, please consult the command reference for output details. In addition, the options --project and --track in SWIF1 --add-job are replaced by --account and --partition in SWIF2 --add-job. The valid accounts can be found at Slurm Accounts and patition information can be found from the Jlab Slurm Information Page. Finally, in order to maintain consistency of running a project workflow from different users, SWIF2 does not pass through any environment variables from the user's submission shell.  Instead, the job envirronment is initialized in a manner similar to the way it is initialized when you login to an interactive farm node.  This differs from the default behavior of SLURM and, consequently, the current behavior of Auger (note that swif1 has always launched user code with a limited environment). The user's job script must therefore construct an appropriate runtime environment, if necessary, by use of facilities such as the 'module' command or sourcing of project-specific setup scripts.