Opened 13 years ago
Closed 13 years ago
#768 closed Bug (fixed)
warning at run time step when using old TKE scheme due to the namelist parameter rn_bshear associated the the default TKE scheme
| Reported by: | ctlod | Owned by: | cetlod |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | OCE | Version: | v3.2 |
| Severity: | Keywords: | ||
| Cc: |
Description
The rn_bshear parameter of namzdf_tke namelist is only used in the default TKE scheme.
When using the old TKE scheme (key_zdftke_old) it doesn't appear as a parameter of the TKE namelist and cause a warning.
One solution could be:
- add this parameter into the NAMELIST/namzdf_tke/ of the zdftke_old.F90 module.
- add its declaration at the beginning of the zdftke_old.F90 module
"REAL(wp) :: rn_bshear = 1.e-20 ! background shear (>0) "
Commit History (1)
| Changeset | Author | Time | ChangeLog |
|---|---|---|---|
| 2492 | cetlod | 2010-12-20T11:17:05+01:00 | v3.2:correction of some inconsistencies of zdftke_old with namelist, see ticket #768 |
Attachments (1)
Change History (6)
comment:1 Changed 13 years ago by ctlod
- Summary changed from Running warning when using old TKE scheme due to the namelist parameter rn_bshear associated the the default TKE scheme to warning at run time step when using old TKE scheme due to the namelist parameter rn_bshear associated the the default TKE scheme
comment:2 Changed 13 years ago by gm
- Owner changed from NEMO team to cetlod
compatibility of tke_old and tke namelists effectively requires to add some declaration in zdftke_old and to transform old tke namelist parameter into hard coded values defined in the header of the zdftke_old module.
The modified zdftke_old module is provided in attachment.
Action: Christian, please, can you update the v3.2
Gurvan
comment:3 Changed 13 years ago by cetlod
- Resolution set to fixed
- Status changed from new to closed
comment:4 Changed 13 years ago by cetlod
- Resolution fixed deleted
- Status changed from closed to reopened
comment:5 Changed 13 years ago by cetlod
- Resolution set to fixed
- Status changed from reopened to closed
Done in v3.2 for consolidation, see changeset:2492
parameters rn_addhft & rn_sclhft are also concerned and should be respectibvely declared and added into the namelist namzdf_tke