Page History

DESCRIPTION

Compare grib BUFR messages contained in two files. If some differences are found it fails returning an error code. Floating-point values are compared exactly by default, different tolerance can be defined see -P -A -R. Default behaviour: absolute error=0, bit-by-bit compare, same order in files.

USAGE

bufr_compare [options] file file bufr_file1 bufr_file2

OPTIONS

...

Compare files in which the messages are not in the same order. This option is time expensive.

...

All the keys in this list are skipped in the comparison. Bit-by-bit compare on.

...

Write different messages on files.

...

Enable two-way comparison.

...

Only the listed keys or namespaces (:n) are compared. The optional letter after the colon is used to force the type in the comparison: li->integer, d->float, s->string, n->namespace. See -a option. Incompatible with -H option.

...

Compare only message headers. Bit-by-bit compare on. Incompatible with -c option.

...

Compare floating-point values using the relative error as tolerance. key1=relative_error error1 will compare key1 using relative_error1. all=relative_error will compare all the floating-point keys using relative_error. Default all=0.

...

Compare floating-point values using the absolute error as tolerance. Default is absolute error=0

...

Compare data values using the packing error as tolerance.

...

Compare data values using factor multiplied by the tolerance specified in options -P -R -A.

...

Where clause. Grib messages Messages are processed only if they match all the key/value constraints. A valid constraint is of type key=value or key!=value. For each key a string (key:s) or , a double (key:d) or a long an integer (key:li) type can be specified. Default type is string. In the value you can also use the forward-slash character '/' to specify an OR condition (i.e. a logical disjunction) Note: only one -w clause is allowed.

...

Force. Force the execution not to fail on error.

...