-
Notifications
You must be signed in to change notification settings - Fork 383
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
Adds support for Lawrencium #390
Conversation
Hey @jnjohnsonlbl, The *.run script created for Lawrencium is quite strange and I probably have an incorrect setting for Lawrencium. If you get a chance next week, could you take a look at it? Thanks. You can use the following commands to create a case.
|
Anything specific you're concerned about in the .run script? |
It is quite an odd looking run script or it might be that I'm just unfamiliar with *.run after CIME migration. |
I think a lot of miscellaneous stuff was changed after CIME went through. There are a couple things you can do to convince yourself that this isn't completely wacky:
|
In CIME, the .run script is perl instead of csh so don't expect it to look anything like the pre-cime script. .submit is also perl and .build has just enough csh to call a perl script. |
Hey @bishtgautam, I understand you may or may not be satisfied with the new .run script, but there is still an outstanding library loading issue related to NetCDF on Lawrencium, correct? I know there's a lot of stuff in flight at the moment. Do you want to leave this PR for now and wait for things to settle down? |
It turns on that @rljacob was correct. Post *.cime run script is completely different and one needs to use *.submit script to submit the job. So, I'm satisfied with the run script. I believe the netCDF lib is still an issue. I will close the PR and open an issue. |
This is not ready, but using this space to have a discussion.