Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

job queue derecho

xiulingao

Xiulin Gao
New Member
Please fill in all relevant information below, deleting the red text after you have read it.

Before submitting a help request, please check to see if your question is already answered:
- Search the forums for similar issues
- Check the CIME troubleshooting guide to see if any suggestions there solve your problem
- Check any other relevant CESM documentation



What version of the code are you using?
- CESM staff members will mainly provide answers for supported model versions, as outlined in the CESM support policy, and can only provide limited help for versions that are no longer supported. You may ask questions about unsupported versions, but may need to rely on community answers.
- For CESM2.1.2 onwards run the script ./describe_version from the top level of your CESM clone to find the version
- From older model versions, provide the output from running the following commands from the top level of your CESM clone
> git describe
> ./manage_externals/checkout_externals --status --verbose



Have you made any changes to files in the source tree?
- Describe any changes (code, xml files, etc.)


Describe every step you took leading up to the problem:
- Describe every step you took, starting with the create_newcase command and including any changes you made to xml files, user_nl files, etc. Please try to reproduce the problem first using your own instructions.


If this is a port to a new machine: Please attach any files you added or changed for the machine port (e.g., config_compilers.xml, config_machines.xml, and config_batch.xml) and tell us the compiler version you are using on this machine.
Please attach any log files showing error messages or other useful information.

- If the error occurs during the build, please attach the appropriate build log file showing the compilation error message.
- If the error occurs during the run, please attach all log files from the run (cpl.log, cesm.log and all component log files).



Describe your problem or question:
 

xiulingao

Xiulin Gao
New Member
Sorry, I accidently created a blank post... So here is my question.

I'm running CLM-FATES on Derecho with CTSM 5.1 dev 157. But I cannot change my job queue by ./xmlchange job_queue = regular or job_priority = regular. The only queue I can use is develop, which is limited to max. wall time of 6 hours. Any tips for how should I change the job queue? Thanks!
 

xiulingao

Xiulin Gao
New Member
ok I think I know now that this might be a CIME version issue. But is it possible that with an older version of cime, I can still use the regular queue instead of being restricted to only develop queue?
 

slevis

Moderator
Staff member
@xiulingao
./xmlchange offers a good way to change entries in your case's .xml files.
./xmlquery is also a good way to see existing settings. For example...
./xmlquery job_queue # in one of my cases returns ERROR: No results for job_queue (same for job_priority), while
./xmlquery JOB_QUEUE # returns

Results in group case.run
JOB_QUEUE: main

Results in group case.st_archive
JOB_QUEUE: develop


./xmlquery JOB_PRIORITY # returns
JOB_PRIORITY: regular

...so I think the answer to your question is that you need to set JOB_QUEUE to main and JOB_PRIORITY to regular.

NOW, considering that there are two instances of JOB_QUEUE in env_workflow.xml (which I discovered by typing grep JOB_QUEUE *.xml), I recommend updating this setting by opening the .xml file with an editor, because I do not know whether ./xmlchange will do the correct thing for you.
 
Top