metar_compare(1)

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