#2163 closed Bug (fixed)
depth[tuvw]_bounds initialised to wrong values in iom_init
Reported by: | davestorkey | Owned by: | davestorkey |
---|---|---|---|
Priority: | low | Milestone: | 2018 release-4.0 |
Component: | IOM | Version: | trunk |
Severity: | minor | Keywords: | v4.0 |
Cc: |
Description
BE CAREFUL !!! Due to dynamic behaviour of this ticket creation page, it is highly recommend to set first all other fields before writing the ticket description below.
If you have lost your draft after an unwanted reload, you can click on the link 'Restore Form' in the contextual menu upper right to recover it.
Remove these lines after reading.
Context
The depth[tuvw]_bounds arrays for the diagnostics files are set incorrectly in iom_init. gdept_1d is used to set the depth[tuv] bounds and gdepw_1d is used to set the depthw_bounds but it should be the other way round.
Analysis
...
Fix
...
Commit History (1)
Changeset | Author | Time | ChangeLog |
---|---|---|---|
10361 | davestorkey | 2018-11-30T09:33:05+01:00 | Bug fix for depth_bounds initialisation in iom_init. Ticket #2163. |
Change History (3)
comment:1 Changed 5 years ago by davestorkey
comment:2 Changed 5 years ago by davestorkey
- Resolution set to fixed
- Status changed from new to closed
Bug fix doesn't change SETTE results and sanity checked by Daley Calvert. Committed at rev 10361.
comment:3 Changed 22 months ago by nemo
- Keywords v4.0 added
In 10361: