You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In trying to move my nightly tests to SLES15, something interesting was found. Namely, the remap_upper.py and remap_catchANDcn.py scripts create SLURM jobs and submit them. But remap_lake_landice_saltwater.py does not. Rather, it just runs on the node where you are running.
Now, perhaps these jobs are small enough that even at very-high resolution this doesn't matter hardware-wise, but my nightly tests were used to regrid.pl where everything was done in SLURM if you weren't on compute nodes.
My "solution" for now is I load g5_modules in my testing scripts but this is not ideal as eventually these jobs will run on discover-cron which isn't exactly a big node usually as it just manages cron.
The text was updated successfully, but these errors were encountered:
In trying to move my nightly tests to SLES15, something interesting was found. Namely, the
remap_upper.py
andremap_catchANDcn.py
scripts create SLURM jobs and submit them. Butremap_lake_landice_saltwater.py
does not. Rather, it just runs on the node where you are running.Now, perhaps these jobs are small enough that even at very-high resolution this doesn't matter hardware-wise, but my nightly tests were used to
regrid.pl
where everything was done in SLURM if you weren't on compute nodes.My "solution" for now is I load
g5_modules
in my testing scripts but this is not ideal as eventually these jobs will run ondiscover-cron
which isn't exactly a big node usually as it just manages cron.The text was updated successfully, but these errors were encountered: