Opened 15 years ago
Closed 15 years ago
#182 closed enhancement (fixed)
rangecheck command line option — at Version 1
| Reported by: | Huw Lewis | Owned by: | Huw Lewis |
|---|---|---|---|
| Priority: | normal | Milestone: | 4.0 |
| Component: | ROPP (all) | Version: | 3.0 |
| Keywords: | Cc: |
Description (last modified by )
Axel suggests including a '-no_ranchk' command-line option for tools such as ropp_fm_bg2ro_1d to switch off rangechecking on writing output (see attached).
Axel writes:
I think this is very important, in particular when you work with large data sets (as I do). I regularly concatenate them into one archive per day or month, and this is not possible when the number of levels changes. So I suggest to include this in an updated ROPP version.
This could be implemented in a similar way in other stand-alone tools.
Change history (2)
by , 15 years ago
| Attachment: | ropp_fm_bg2ro_1d_AXEL0109.f90 added |
|---|
comment:1 by , 15 years ago
| Description: | modified (diff) |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Added '-no_ranchk' command line option to all ropp_pp, ropp_fm and ropp_1dvar tools to suppress rangechecking on data input and output as suggested. This option is not available for ropp_io tools since we want to be more restrictive on when/where rangechecking is appropriate (e.g. thinner etc). See e.g. [2282].
The '-no_ranchk' option is (purposely) not fully documented in the User Guide, but is documented in the 'usage' output provided with each tool and available mainly for 'super-users' such as Axel.
Ticket closed as fixed.