6.3 “queue_commands.py” file in $MAST_ROOT/submit/platforms/NEWPLATFORM is different from the one in $MAST_ROOT/submit
Here’s my suggestion on how to create queue_commands.py for your platform:
First, queue_commands.py depends mainly on your batch system. We already provide working queue_commands.py for three batch systems: 1) Torque (under Bardeen), SGE (under Turnbull), and Slurm (under ACI/Stampede). If your cluster also uses one of the three systems, simply copy the queue_commands.py file from the corresponding folder under $MAST_ROOT/submit/platforms/.
Second, modify the corresponding python functions in $MAST_ROOT/submit/platforms/queue_commands.py so that it can parse job id (the extract_submitted_jobid function), a summary of your current submitted jobs, which we call “queue snapshot” (the queue_snap_command function), and decide the status of a specific job that you have submitted (the queue_status_from_text).
6.3 “queue_commands.py” file in $MAST_ROOT/submit/platforms/NEWPLATFORM is different from the one in $MAST_ROOT/submit
Here’s my suggestion on how to create queue_commands.py for your platform:
First, queue_commands.py depends mainly on your batch system. We already provide working queue_commands.py for three batch systems: 1) Torque (under Bardeen), SGE (under Turnbull), and Slurm (under ACI/Stampede). If your cluster also uses one of the three systems, simply copy the queue_commands.py file from the corresponding folder under $MAST_ROOT/submit/platforms/.
Second, modify the corresponding python functions in $MAST_ROOT/submit/platforms/queue_commands.py so that it can parse job id (the extract_submitted_jobid function), a summary of your current submitted jobs, which we call “queue snapshot” (the queue_snap_command function), and decide the status of a specific job that you have submitted (the queue_status_from_text).