3.1 Job Submission Methods
Nitro enables system administrators to choose what level of detail users need to know in order to submit Nitro jobs.
Nitro provides these options for users when submitting Nitro Jobs:
- User-customized job scripts (high level of detail, static jobs only)
- nitrosub command (minimal level of detail; static or dynamic jobs)
This topic provides information on the different options.
In this topic:
3.1.1 User-Customized Job Script
The User-customized job script methodology is only available for static jobs.
With the initial release of Nitro, system administrators copied a sample job script packaged with Nitro and then customized it for their system. The system administrations then gave a copy of the customized sample script to the user, who would then make a copy of it and further customize it when submitting a job for the task file.
Nitro is now packaged with a nitro_job.sh and a worker_job.sh script. For static jobs, only the nitro_job.sh script is applicable.
The nitro_job.sh script can be customized by the system administrators for their systems. The system administrators can then have the user copy that script and make further customizations (such as configuring environment variables) that affect the respective launch_nitro.sh script. Users will then use the resource manager's job submission command (for example, qsub for Torque) to execute the user's customized nitro_job.sh script.
See 5.4 Job Scripts for more information.
The nitrosub command is only available for systems that use a shared file system.
The nitrosub command lets users submit Nitro jobs without having to copy and customize the nitro_job.sh script for their task file.
The user only needs to specify the user's task file path, a resource quantity, and a wall-time limit when they submit a Nitro job for the task file. The nitrosub command will then execute the system's nitro_job.sh script and the worker_job.sh script (as needed for dynamic jobs).
See 5.1 nitrosub Command for more information.