-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Fix mechred arithmetic abort #167
Comments
Try uncommenting lines 563, 564 in icedrv_step.F90. I never understood why we didn't get errors with this commented out. Then I forgot about it. |
As an aside, there are lots of these messages written to the log file. Can we modify that or turn it off? (ridge_ice)Repeat ridging, niter = 1 The logic is in subroutine ridge_ice,
|
Please do. It shouldn’t be writing unless niter is bigger than 1.
e
|
Just looking at the code, it must be iterating twice and writes that on the first iteration to log that it's going to a second iteration. It does not write when it has converged. Not sure if that is expected. Do you want any of that information to the log file? If so, what could be different? |
Unless it's a problem for space or computing time on travis, let's leave the 'Repeat ridging' warning alone for now. In my gx1 run, in only appears a few times. We could change it so that it only writes if niter > 1; that rarely happens unless there's a serious problem and the code crashes. The opening/closing data set is probably stressing the code a bit (which is good), and it's also not consistent with the other forcing. We can change this behavior later if it becomes too annoying. Or we can change it now if it's needed for travis. |
@eclare108213 I'm happy with that approach. |
Auto validate qc
see #163
The text was updated successfully, but these errors were encountered: