-
Notifications
You must be signed in to change notification settings - Fork 132
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
Optionally rotate wind/stress from to computational grid (from true north) #473
Conversation
How much testing has been done? Are we confident it's all bit-for-bit? |
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.
This is much easier to understand at a glance, thank you.
@apcraig w.r.t. bit-for-bit. Depending on rotate_wind option (true/false) it will skip the rotation of wind/stress. So it assumes, that the provided forcing is rotated correctly and exactly like the default inline rotation. |
@mhrib I understand what the code is supposed to do. I just want to confirm that you have compiled and run this code, and that the default setting produces bit-for-bit results. That information was not included in the PR information yet. Thanks. |
@apcraig Sorry, I did not perform the test (which I always should do!). Now tested with intel compiler on GX3 grid (4x4) running for one day (24 steps) using the same ice_in file without rotate_wind defined (ie. set to default value = .true.): md5sum's on restart-files are equal. |
Thanks @mhrib, I also ran a full test suite last night and everything looks good. https://github.com/CICE-Consortium/Test-Results/wiki/cice_by_hash#3fedc78b1b012f8bd6c0fde7c1b41e79b9db63a9 |
For detailed information about submitting Pull Requests (PRs) to the CICE-Consortium,
please refer to: https://github.com/CICE-Consortium/About-Us/wiki/Resource-Index#information-for-developers
PR checklist
Optional rotate wind vectors to computational grid (default)
Mads Hvid Ribergaard, DMI
Able to merge. These branches can be automatically merged.
A completely other change within this pull request: