1BUFR_COMPARE(1)                  User Commands                 BUFR_COMPARE(1)
2
3
4

NAME

6       bufr_compare - manual page for bufr_compare
7

DESCRIPTION

9       NAME    bufr_compare
10
11       DESCRIPTION
12
13              Compare  BUFR  messages contained in two files.  If some differ‐
14              ences are found  it  fails  returning  an  error  code.   Float‐
15              ing-point values are compared exactly by default, different tol‐
16              erances can be defined (see -A -R).  Default behaviour: absolute
17              error=0, bit-by-bit compare, same order in files.
18
19       USAGE
20
21              bufr_compare [options] bufr_file1 bufr_file2
22
23       OPTIONS
24
25       -b key,key,...
26
27              All  the  keys  in  this  list  are  skipped  in the comparison.
28              Bit-by-bit compare on.
29
30       -d     Write different messages on files.
31
32       -2     Enable two-way comparison.
33
34       -c key[:i|d|s|n],key[:i|d|s|n],...
35
36              Only the listed keys or namespaces (:n) are  compared.  The  op‐
37              tional  letter  after the colon is used to force the type in the
38              comparison: i->integer, d->float, s->string, n->namespace.   See
39              -a option. Incompatible with -H option.
40
41       -S start
42              First field to be processed.
43
44       -E end Last field to be processed.
45
46       -a       -c option modifier. The keys listed with the option -c will be
47              added to the list of keys compared without -c.
48
49       -H     Compare only message headers. Bit-by-bit compare on.  Incompati‐
50              ble with -c option.
51
52       -R key1=relative_error1,key2=relative_error2,...
53
54              Compare floating-point values using the relative error as toler‐
55              ance.  key1=relative_error1 will compare key1 using relative_er‐
56              ror1.   all=relative_error  will  compare all the floating-point
57              keys using relative_error. Default all=0.
58
59       -A absolute error
60
61              Compare floating-point values using the absolute error as toler‐
62              ance.  Default is absolute error=0
63
64       -t factor
65              Compare  data  values  using  factor multiplied by the tolerance
66              specified in options -R -A.
67
68       -w key[:{s|d|i}]{=|!=}value,key[:{s|d|i}]{=|!=}value,...
69
70              Where clause.  Messages are processed only if they match all the
71              key/value  constraints.  A valid constraint is of type key=value
72              or key!=value.  For each key a string (key:s), a double  (key:d)
73              or  an  integer  (key:i)  type can be specified. Default type is
74              string.  In the value you can also use the forward-slash charac‐
75              ter  '/' to specify an OR condition (i.e. a logical disjunction)
76              Note: only one -w clause is allowed.
77
78       -f     Force. Force the execution not to fail on error.
79
80       -V     Version.
81
82       -7     Does not fail when the message has wrong length
83
84       -v     Verbose.
85
86       SEE ALSO
87
88              Full   documentation   and   examples    at:    <https://conflu
89              ence.ecmwf.int/display/ECC/bufr_compare>
90
91       NAME    bufr_compare
92
93       DESCRIPTION
94
95              Compare  BUFR  messages contained in two files.  If some differ‐
96              ences are found  it  fails  returning  an  error  code.   Float‐
97              ing-point values are compared exactly by default, different tol‐
98              erances can be defined (see -A -R).  Default behaviour: absolute
99              error=0, bit-by-bit compare, same order in files.
100
101       USAGE
102
103              bufr_compare [options] bufr_file1 bufr_file2
104
105       OPTIONS
106
107       -b key,key,...
108
109              All  the  keys  in  this  list  are  skipped  in the comparison.
110              Bit-by-bit compare on.
111
112       -d     Write different messages on files.
113
114       -2     Enable two-way comparison.
115
116       -c key[:i|d|s|n],key[:i|d|s|n],...
117
118              Only the listed keys or namespaces (:n) are  compared.  The  op‐
119              tional  letter  after the colon is used to force the type in the
120              comparison: i->integer, d->float, s->string, n->namespace.   See
121              -a option. Incompatible with -H option.
122
123       -S start
124              First field to be processed.
125
126       -E end Last field to be processed.
127
128       -a       -c option modifier. The keys listed with the option -c will be
129              added to the list of keys compared without -c.
130
131       -H     Compare only message headers. Bit-by-bit compare on.  Incompati‐
132              ble with -c option.
133
134       -R key1=relative_error1,key2=relative_error2,...
135
136              Compare floating-point values using the relative error as toler‐
137              ance.  key1=relative_error1 will compare key1 using relative_er‐
138              ror1.   all=relative_error  will  compare all the floating-point
139              keys using relative_error. Default all=0.
140
141       -A absolute error
142
143              Compare floating-point values using the absolute error as toler‐
144              ance.  Default is absolute error=0
145
146       -t factor
147              Compare  data  values  using  factor multiplied by the tolerance
148              specified in options -R -A.
149
150       -w key[:{s|d|i}]{=|!=}value,key[:{s|d|i}]{=|!=}value,...
151
152              Where clause.  Messages are processed only if they match all the
153              key/value  constraints.  A valid constraint is of type key=value
154              or key!=value.  For each key a string (key:s), a double  (key:d)
155              or  an  integer  (key:i)  type can be specified. Default type is
156              string.  In the value you can also use the forward-slash charac‐
157              ter  '/' to specify an OR condition (i.e. a logical disjunction)
158              Note: only one -w clause is allowed.
159
160       -f     Force. Force the execution not to fail on error.
161
162       -V     Version.
163
164       -7     Does not fail when the message has wrong length
165
166       -v     Verbose.
167
168       SEE ALSO
169
170              Full   documentation   and   examples    at:    <https://conflu
171              ence.ecmwf.int/display/ECC/bufr_compare>
172
173
174
175bufr_compare                     November 2023                 BUFR_COMPARE(1)
Impressum