Dear CESM community,
I am currently setting up CESM2.2.2 for a new machine (Imperial College HPC). The cluster uses pbs, but the job queue is not specified at submit time. Instead, the queue is chosen based on the job's requirements (and specific queue selection by users appears to be discouraged). I have managed to get by thus far with no more than the usual light-touch setting in ~/.cime/config_*.xml (where * in this case is compilers, machines, and batch). However, I have found that I am unable to submit jobs because a queue is always specified. Is there a straightforward way to indicate in ~/.cime/config_batch.xml that the -j $JOB_QUEUE directive, default to the pbs batch system described in the central cime batch configuration, should be skipped for this machine? The alternative is to simply delete the relevant line (<arg flag="-q" name="$JOB_QUEUE"/>) in env_batch.xml every time I create a new test case but if there's a cleaner way of running that would be preferable. Thank you!
Regards,
Seb
I am currently setting up CESM2.2.2 for a new machine (Imperial College HPC). The cluster uses pbs, but the job queue is not specified at submit time. Instead, the queue is chosen based on the job's requirements (and specific queue selection by users appears to be discouraged). I have managed to get by thus far with no more than the usual light-touch setting in ~/.cime/config_*.xml (where * in this case is compilers, machines, and batch). However, I have found that I am unable to submit jobs because a queue is always specified. Is there a straightforward way to indicate in ~/.cime/config_batch.xml that the -j $JOB_QUEUE directive, default to the pbs batch system described in the central cime batch configuration, should be skipped for this machine? The alternative is to simply delete the relevant line (<arg flag="-q" name="$JOB_QUEUE"/>) in env_batch.xml every time I create a new test case but if there's a cleaner way of running that would be preferable. Thank you!
Regards,
Seb