Is there a way to prevent SRW v2.1.0 from writing 'qos=None' in the SBATCH directives? #517
Replies: 1 comment 1 reply
|
Hi Paddy. If you are using rocoto to run the workflow, I think you may need to look in ufs-srweather-app/parm/FV3LAM_wflow.xml on lines 140-152. You should remove the <queue>.....</queue> sections from each line. If you are using the wrapper scripts, you can just comment out the qos line in ufs-srweather-app/ush/wrappers/sq_job.sh script. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi-
I'm trying to transition from a develop branch deployment of SRW (from Aug/Sept 2022) to using v2.1.0. I'm running on an HPC at Boise State University, so there's no pre-configuration. I've created all the necessary wflow_host.lua, build_host_intel.lua, and machine/host.yaml files. Now that I've switched to v2.1.0, I'm not able to get the model to run because of errors like this one:
12/13/22 20:24:58 GMT :: FV3LAM_wflow.xml :: Submission of make_grid failed! sbatch: error: Batch job submission failed: Invalid qos specificationThe submission looks like this (from log.launch_FV3LAM_wflow):
The problem is that this cluster doesn't accept
--qos=somethingdirectives because there are no queues configured.Is there a way to write '--qos=' or better yet, to leave the directive off altogether? I can't seem to get SRW to submit jobs with anything other than '--qos=something' or '--qos=None'.
Thank you, -Paddy McCarthy.
All reactions