#1055 closed Bug (fixed)
dom_vvl_2 with vvl and s-coordinates
Reported by: | jchanut | Owned by: | jchanut |
---|---|---|---|
Priority: | low | Milestone: | |
Component: | OCE | Version: | v3.4 |
Severity: | Keywords: | OPA VVL s_sigma v3.4 | |
Cc: |
Description
This bug may concern people using both key_vvl and sigma coordinate. The problem is in dom_vvl_2 routine (module domvvl.F90) that sets "before" vertical scale factors at velocity points from time filtered vertical scale factors at T-points. The surface weighted update between adjacent T-points conflict with bathymetry definition at velocity points (unweighted calculation in that case). As a result, the vertical integral of fse3u_b/fse3v_b does not match hu_0+sshu_b / hv_0+sshv_b.
This problem can be detected in AMM12 configuration, but in the meridional direction only (the grid is regular otherwise). The (time invariant) maximum error on the actual bathymetry used at before time step is less than 1 meter in that case. Certainly not a big deal, except if like me, you try to find out why the total depth you get is not what you should have...
As a remedy I suggest whether:
- to initialize scale factors at velocity points (in domzgr.F90) thanks to surface weighted averages.
- or change what is done in dom_vvl_2 in the form: fse3u_b(:,:,:) = fse3u_0(:,:,:)*(1+sshu_b(:,:)*muu(:,:,:))
where sshu_b holds the right sea level.
Jérôme
Commit History (1)
Changeset | Author | Time | ChangeLog |
---|---|---|---|
3958 | cbricaud | 2013-07-08T12:01:29+02:00 | Bug with vvl and sco, see ticket #1055 |
Change History (10)
comment:1 Changed 11 years ago by clevy
- Owner changed from NEMO team to jchanut
comment:2 Changed 11 years ago by jchanut
comment:3 Changed 11 years ago by jchanut
- Resolution set to fixed
- Status changed from new to closed
comment:4 Changed 11 years ago by detraceyb
This revision also included a fix to a non-minor error on line 204.
comment:5 Changed 8 years ago by nicolasmartin
- Keywords VVL added; vvl removed
comment:6 Changed 8 years ago by nicolasmartin
- Keywords nemo_v3_4* added
comment:7 Changed 8 years ago by nicolasmartin
- Keywords s_sigma added; sigma removed
comment:8 Changed 6 years ago by nemo
- Keywords release-3.4* added; nemo_v3_4* removed
comment:9 Changed 6 years ago by nemo
- Keywords release-3.4* removed
comment:10 Changed 2 years ago by nemo
- Keywords OPA v3.4 added
To fix this, I finally suggest to work on thickness "anomalies" in dom_vvl_2 such that lines below:
could be replaced by: