JULES model batch

Hi everyone,
I have been in touch for the last weeks trying to update my suite (u-ds632) and make it run again on JASMIN, after the updates on the system. My suite now manages to start the spin-up runs but is failing, possibly because I am not requesting the right resources, not including all the requested details, or both. It initially failed, asking me to add an account to the petition, so I followed the most updated and original suite at ode.metoffice.gov.uk/trac/roses-u/browser/c/c/6/6/9/trunk?rev=319740. First, I tried just copying this suite.rc, but because I don’t know where I should specify things like “JASMIN_QOS”, my model failed.

So, I decided to make only a few changes:
suite.rc in d/s/6/3/2/trunk/location/JASMIN – roses-u

But still, my model is failing, although with a new error:

Perhaps you can identify the variable being wrongly specified and guide me on how to write a better batch from here. I would really appreciate any suggestions.

Best wishes,

Maria Paula

I don’t have access to jasmin at the moment….

But you have a file c/c/6/6/9/trunk/location/JASMIN/suite.rc

so I would start there and adjust the slurm settings to fit the new jasmin set up

here is the documentation about queues. High qos , standard partition is a good thing to try

Also if you want to try changing the slurm settings without rerunning cylc, you can also find the job file in cylc which didn’t submit, and edit it and try sbatch job. This is a temporary stage but useful to debug things

Hi David,
Thanks, my model is already running. I think the error was because of the “partition” variable.

I would like to know more about the way of debugging that you mentioned. I can see commented instructions to the batch here run3/log/job/20010101T0000Z/spinup_01/01/job, but for instance, I can’t find the word partition in the entire document more than here, so how would I change it here?.

Thanks again for your help.

Maria Paula