#534 closed task (fixed)
Use --no-ranchk consistently (two dashes in front) [1 h]
| Reported by: | Ian Culverwell | Owned by: | Ian Culverwell |
|---|---|---|---|
| Priority: | normal | Milestone: | ROPP9.1 carry over |
| Component: | ropp_1dvar | Version: | 9.0 |
| Keywords: | Cc: |
Description
https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_1dvar/tools/ropp_1dvar_bangle.f90 https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_1dvar/tools/ropp_1dvar_refrac.f90
Original changeset:
Use --no-ranchk consistently (two dashes in front): https://trac.romsaf.org/ropp/changeset/4926
Change history (5)
comment:1 by , 6 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 6 years ago
| Component: | ROPP(all) → ropp_1dvar |
|---|
comment:3 by , 5 years ago
comment:4 by , 5 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Range checking is by default on, and because switching it off is really only for expert users, it was decided long ago that the --no-ranchk option should not be documented in the man pages or the user guides. This decision could be revisited, but for now, I'm closing the ticket.
comment:5 by , 5 years ago
(While we're here, update ropp_fm_bg2ro_2d.f90 to use --no-ranchk consistently at r5899.)
Note:
See TracTickets
for help on using tickets.
1dvar routines, including add_error tools, amended to use
-no-ranchkconsistently at r5885. The help information on the latter has also been tidied up a bit.