Opened 12 years ago
Closed 12 years ago
#999 closed Bug (fixed)
Bug in TOP/trcsbc.F90 module : the mass flux associated with runoff should not be included in surface boundary condition when coupling online with dynamics
| Reported by: | cetlod | Owned by: | cetlod |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | TOP | Version: | v3.4 |
| Severity: | Keywords: | ||
| Cc: |
Description (last modified by cetlod)
The mass/volume addition due to the river runoff is, at each relevant depth level, added to the horizontal divergence (hdivn) in the subroutine sbc rnf div (called from divcur.F90).
The hdivn terms are used in the tracer advection modules to force vertical velocities.
So, when coupling online with dynamics, the surface boundary condition - routine trcsbc - should only consider the concentration/dilution effect due to evaporation minus precipitation + freezing/melting of sea-ice
Coupling in offline, hdivn is computed from ocean horizontal velocities only ; the runoff are not included : emps in dynamical files contains (emps - rnf)
In trcsbc.F90 one should write :
IF( .NOT. lk_offline .AND. lk_vvl ) ! coupling online + vvl zemps(:,:) = emps(:,:) - emp(:,:) ELSE ! no vvl or coupling offline zemps(:,:) = emps(:,:) ENDIF
Commit History (1)
| Changeset | Author | Time | ChangeLog |
|---|---|---|---|
| 3580 | cetlod | 2012-11-16T15:49:18+01:00 | Correction of surface boundary condition on passive tracers : see ticket #999 |
Change History (3)
comment:1 Changed 12 years ago by cetlod
- Summary changed from Bug in TOP/trcsbc.F90 module : the mass flux associated with runoff should not be included in surface boundary condition to Bug in TOP/trcsbc.F90 module : the mass flux associated with runoff should not be included in surface boundary condition when coupling online with dynamics
comment:2 Changed 12 years ago by vichi
- Owner changed from NEMO team to cetlod
comment:3 Changed 12 years ago by cetlod
- Description modified (diff)
- Resolution set to fixed
- Status changed from new to closed
