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

NAME

6       metar_compare - manual page for metar_compare
7

DESCRIPTION

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