-
Notifications
You must be signed in to change notification settings - Fork 25
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
Support for NUOPC driver #199
Conversation
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 @matsbn ,
I should probably have a better grasp of NUOPC to make a full review of this PR, but at least I don't see anything obvious that looks strange to me.
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.
Looks fine to me, although I can't really say much more than this.
Thanks for approving, @TomasTorsvik and @JorgSchwinger . This is a change that the BLOM devs have been informed about, and I thought it as useful to inform the iHAMOCC devs through a review request since it changes the folder structure under |
Support for NUOPC driver
BLOM can now be coupled to CESM using the NUOPC driver. Also, wave forcing fields have been declared and wave-ocean coupling is supported when using the NUOPC driver.
Technical functioning of the NUOPC interface has been verified with cesm2_3_alpha08a. There is no change of results in BLOM standalone configurations or when the MCT driver is used.