Changes between Initial version and Version 3 of Ticket #215


Ignore:
Timestamp:
2010-07-12T10:42:31Z (14 years ago)
Author:
Dave Offiler
Comment:

In ropp2bufr.f90/ConvertROPPtoBUFR, added a section before L1b, L2a & L2b are converted to test for the whole profile key parameters set missing (except height coordinates), viz:

L1b : BA_L1, BA_L2 and BA
L2a : N
L2b : P, T, and q

If count of missing samples is equal to ..%Npoints, reset ..%Npoints to zero, thus skipping the conversion for that Level using the existing code tests. A (diagnostic) message is written if this happens.

Tested on Rune's netCDF file, and correctly skips the L2b dummy profile generated by the LOG-247 thinner, generating an identical number of BUFR octets (12594) as produced by the v3.0 and v4.0 encoders.

Run t_ropp2bufr in ropp_io/tests - FAIL. Reference datasets (notably ropp_test.bfr) regenerated to reflect reverted Local Data Sub-Category value (see BUFR header item (2) above). Re-run t_ropp2bufr - PASS.

Changeset [2564]. Will provide Rune with updated f90 & bfr files for him to confirm expected outputs.

NB original issue of 'default' ARH is yet to be explained, so this Ticket remains open for now.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #215

    • Property Status newaccepted
  • Ticket #215 – Description

    initial v3  
    11Rune has been testing the DRI Candidate Release v4.1 and reports
    2 an anomoly in the v4.1 ropp2bufr tool wrt the currently operational v3.0 version:
     2an anomaly in the v4.1 ropp2bufr tool wrt the currently operational v3.0 version:
    33
    44{{{
    5 I've run the GRAS SAF production on a days occulatations using
     5I've run the GRAS SAF production on a days occulations using
    66ROPP-3 and ROPP-4.1 . The are some differences in the output netcdf
    77files that I guess is due to going from float to doubles. I've