Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remap_restarts should use SLURM for lake/landice/saltwater #85

Open
mathomp4 opened this issue Jul 19, 2024 · 0 comments
Open

remap_restarts should use SLURM for lake/landice/saltwater #85

mathomp4 opened this issue Jul 19, 2024 · 0 comments
Assignees

Comments

@mathomp4
Copy link
Member

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.

@mathomp4 mathomp4 transferred this issue from GEOS-ESM/GMAO_Shared Jul 19, 2024
sdrabenh added a commit that referenced this issue Sep 13, 2024
remap_restarts uses SLURM for lake/landice/saltwater (Resolution for issue #85)
mathomp4 added a commit that referenced this issue Sep 13, 2024
…mify

Revert "remap_restarts uses SLURM for lake/landice/saltwater (Resolution for issue #85)"
mathomp4 added a commit that referenced this issue Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants