#1295 closed Bug (wontfix)
rdtmax mis-assigned in domain.F90
| Reported by: | nswart | Owned by: | gm |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | OCE | Version: | v3.4 |
| Severity: | Keywords: | ||
| Cc: |
Description
On line 235 to 236 of /NEMOGCM/NEMO/OPA_SRC/DOM/domain.F90, rdtmin and rdtmax are both set to rn_rdtmin, which seems to be a bug, i.e.:
rdtmin = rn_rdtmin
rdtmax = rn_rdtmin
Tracer acceleration doesn't work with this code. If I change it so that
rdtmax = rn_rdtmax
then acceleration seems to work as I expect.
-Neil
Commit History (0)
(No commits)
Change History (3)
comment:1 Changed 10 years ago by clevy
- Owner changed from NEMO team to gm
comment:2 Changed 10 years ago by gm
- Resolution set to wontfix
- Status changed from new to closed
comment:3 Changed 8 years ago by nicolasmartin
- Keywords acceleration removed
Note: See
TracTickets for help on using
tickets.
Hi,
Thanks for your interest in NEMO.
This was deliberately made.
Indeed, with the use of a vertical variation of the tracer time step the model loose its integrity: the tracer content is no more preserved. See the discussion in the documentation (§14.4).
In order to prevent users of doing crazy things, we force rdtmax = rn_rdtmin. It was a quick fix done years ago.
The proper solution is to remove the vertical dependency of rdttra. This is one of the item of "system simplification" (see 2014WP/2014_SystemSimplification_v2). It will be done in 2014 or 2015.
Gurvan