-
Notifications
You must be signed in to change notification settings - Fork 12
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
Oifs48r1 standalone #1091
Oifs48r1 standalone #1091
Conversation
…pt still fails on loading binary files
Nice work! I think this will be a good guide for installing on other platforms, e.g. HLRN etc. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice work! I have no immediate plans to use this on HLRN soon, but it seems pretty straightforward to follow @JanStreffing work.
Intel did not work on either juwels or levante. It compiles but runtime crashes with some library relinking error. Nothing fundamental I think, but I though it was not prio 1 to solve at that stage. I ended up copying the environments from DestinE project where they use GNU on levante. They also have the same error when they try intel. I agree, life for the coupled setup will be easier once intel works. I tried to clean up a bit. Right now, I am replacing the juwels compiler_mpi for all versions. That's not good. I want to do that only for 48r1. I tried:
But I just get the default from levante.yaml. Another case of early resolve issue? |
…k it should work. Also some cleanup und unneeded thvars
the latest commit 0e47c09 breaks the selection of iolibraries: system_gnu_libs for levante. We need to get some form of this to work, because it's not okay to just change the iolibraries variable for all oifs versions. |
@@ -284,7 +282,7 @@ supercooled_liquid_could_fix: 0 | |||
# with random numbers generated using CDO | |||
# We use ensemble_id as seed, so this number must be unique for each member | |||
# i.e. ensemble_id = N for r1iNp1 | |||
perturb: 1 | |||
perturb: 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I changed the default behavior here, not by accident. I think we want testability and reproducibility from the standalone case. Perturbation experiments can be made, but are not the default.
Changes reported by CI tests look ok to me. Ready for review |
Strange, I though we already solved the issue of further_reading not being evaluated by adding it to the early vars. In fact I'm positive I ran a test with that. Yet now I get the same behaviour again of not oifs48.env.yaml evaluation.. |
I merge the polished fix for the further_reading that passed all the tests. |
@mandresm: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @JanStreffing,
Nice PR! The append_daily_icml_file is doing quite some nice magic. I think we hitted this wall once in DestinE, I guess you know about that. I hope this is now solved there too.
Other than that just some suggestions. I'll be adding a test for standalone OpenIFS-48r1 tomorrow.
I'm having an issue during compilation:
|
Not an error I remember seeing. We did a good job on making sure no one can access OpenIFS code. So I can't look into your folder at your logfiles. :) |
#approve-changes |
#bump |
#bump #minor |
#bump #minor |
Compiles and runs a one day long TCO95L91 standalone OpenIFS 48r1 simulation starting at 19900101. Caveats: For me! On levante! It's not beautiful.. Feedback on style welcome.