#126 closed enhancement (fixed)
Thinner version ID
Reported by: | Dave Offiler | Owned by: | Dave Offiler |
---|---|---|---|
Priority: | normal | Milestone: | 1.1 |
Component: | ROPP (all) | Version: | 1.0 |
Keywords: | Thinner, version ID | Cc: |
Description
Kent suggests adding a separate version ID for the ROPP thinner code to the ropp_io version ID so as to be able to know which thinner is being used by DMI vs EUM (or whoever) for compariosn/validation purposes.
The simplest solution would appear to be to add a version ID to the new (v1.1) thin_method string in the ROPP structure which is also saved as a global attribute in the netCDF file.
Change history (3)
comment:1 by , 17 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:3 by , 16 years ago
Milestone: | → 1.1 |
---|
Note:
See TracTickets
for help on using tickets.
a) Extended thin_method string in ROPP main structure in ropp_io_types.f90 from 60 to 80 characters.
b) Added software ID string parameter definition to ropp_io_thin() [ "v1.1" ] and added this to rodata%thin_method string after the method ID & title.
c) Re-compiled (ifort) and tested by running (in ropp_io/data):
Actually, something is wrong here: there are 319 BA, Ref & TqP samples in the input file, and the command should sample to <=100 - which it hasn't done, and even says its hasn't. This needs separate investigation'''
And further:
d) Re-generated test files in ropp_io/data using gentestfiles.sh
e) Committed as [1307]