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       NAME    bufr_compare
87
88       DESCRIPTION
89
90              Compare BUFR messages contained in two files.  If  some  differ‐
91              ences  are  found  it  fails  returning  an  error code.  Float‐
92              ing-point values are compared exactly by default, different tol‐
93              erances can be defined (see -A -R).  Default behaviour: absolute
94              error=0, bit-by-bit compare, same order in files.
95
96       USAGE
97
98              bufr_compare [options] bufr_file1 bufr_file2
99
100       OPTIONS
101
102       -b key,key,...
103
104              All the keys  in  this  list  are  skipped  in  the  comparison.
105              Bit-by-bit compare on.
106
107       -d     Write different messages on files.
108
109       -2     Enable two-way comparison.
110
111       -c key[:i|d|s|n],key[:i|d|s|n],...
112
113              Only  the  listed  keys or namespaces (:n) are compared. The op‐
114              tional letter after the colon is used to force the type  in  the
115              comparison:  i->integer, d->float, s->string, n->namespace.  See
116              -a option. Incompatible with -H option.
117
118       -S start
119              First field to be processed.
120
121       -E end Last field to be processed.
122
123       -a      -c option modifier. The keys listed with the option -c will  be
124              added to the list of keys compared without -c.
125
126       -H     Compare  only message headers. Bit-by-bit compare on. Incompati‐
127              ble with -c option.
128
129       -R key1=relative_error1,key2=relative_error2,...
130
131              Compare floating-point values using the relative error as toler‐
132              ance.  key1=relative_error1 will compare key1 using relative_er‐
133              ror1.  all=relative_error will compare  all  the  floating-point
134              keys using relative_error. Default all=0.
135
136       -A absolute error
137
138              Compare floating-point values using the absolute error as toler‐
139              ance.  Default is absolute error=0
140
141       -t factor
142              Compare data values using factor  multiplied  by  the  tolerance
143              specified in options -R -A.
144
145       -w key[:{s|d|i}]{=|!=}value,key[:{s|d|i}]{=|!=}value,...
146
147              Where clause.  Messages are processed only if they match all the
148              key/value constraints.  A valid constraint is of type  key=value
149              or  key!=value.  For each key a string (key:s), a double (key:d)
150              or an integer (key:i) type can be  specified.  Default  type  is
151              string.  In the value you can also use the forward-slash charac‐
152              ter '/' to specify an OR condition (i.e. a logical  disjunction)
153              Note: only one -w clause is allowed.
154
155       -f     Force. Force the execution not to fail on error.
156
157       -V     Version.
158
159       -7     Does not fail when the message has wrong length
160
161       -v     Verbose.
162
163
164
165bufr_compare                     December 2022                 BUFR_COMPARE(1)