Opened 4 years ago
Closed 4 years ago
#2626 closed Bug (fixed)
typo bug in sea ice with large consequences (from revision 4.0.4)
Reported by: | clem | Owned by: | systeam |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | SI3 | Version: | v4.0.* |
Severity: | critical | Keywords: | |
Cc: |
Description (last modified by nicolasmartin)
Context
I introduced a nasty bug between release 4.0.3 and 4.0.4
It's a typo that changed drastically the distribution of solar and non-solar fluxes over ice covered areas. As a consequence, the ice cover and volume increased and some processes had wrong seasonality. In particular the lateral melting.
Since this bug has been introduced while correcting other bugs, and given the importance of it on the ice simulations, I feel uncomfortable keeping the last revision 4.0.5 untouched. Fortunately the official announcement of this revision has not yet been done.
So, I wonder if I could erase the current 4.0.5 and redo it. I know it is not the way we should work but I do not want people to use this version and not be aware of that. What say you?
Besides documentation, here are the only changes in 4.0-HEAD vs 4.0.5:
NEMO/releases/r4.0/r4.0-HEAD@14359:14435
It concerns a bug fix in iceberg module (ticket #2581) and a small incompatibility oasis-agrif (ticket #2621)
Fix
in iceupdate.F90, replace this line:
qns(ji,jj) = qt_oce_ai(ji,jj) - zqsr
by this one:
qns(ji,jj) = qt_oce_ai(ji,jj) - qsr(ji,jj)
Commit History (3)
Changeset | Author | Time | ChangeLog |
---|---|---|---|
14472 | jpalmier | 2021-02-16T18:31:13+01:00 | include clem's iceupdate fix (ticket #2626) |
14470 | clem | 2021-02-16T15:35:53+01:00 | trunk: trivial but very important bug fix in sea ice as described in ticket #2626 |
14469 | clem | 2021-02-16T15:34:07+01:00 | 4.0-HEAD: trivial but very important bug fix in sea ice as described in ticket #2626 |
Change History (6)
comment:1 Changed 4 years ago by nicolasmartin
- Description modified (diff)
comment:2 Changed 4 years ago by nicolasmartin
comment:3 Changed 4 years ago by clem
In 14469:
comment:4 Changed 4 years ago by clem
In 14470:
comment:5 Changed 4 years ago by jpalmier
In 14472:
comment:6 Changed 4 years ago by clem
- Resolution set to fixed
- Status changed from new to closed
Well, I'm not in the best position to decide what should be done but this kind of situation is going to reproduce quite often as we have speed up our release timeline.
Diff r4.0.5/r4.0-HEAD
Diff r4.0.4/r4.0.5
As you wrote, the changes are so small but so significant that we can consider replacing the current version of r4.0.5 release.