Lines Matching +full:signal +full:- +full:to +full:- +full:noise
9 -------
14 In 2001, we added an XML API to the JUNOS operating system, which is
17 FreeBSD utilities to emit XML, typically via a "-X" switch. The
19 and carrying it were non-trivial, and contributed to our expense (and
26 to the underlying FreeBSD code as a means of reducing the expense and
27 delay in tracking HEAD. JUNOS is structured to have system components
29 human-readable text. This allows the API to use the same plumbing as
34 libxo is an effort to mix the best aspects of the JUNOS strategy into
35 FreeBSD in a seemless way, allowing commands to make printf-like
44 which is feed to the CLI, where data from the ODL files tell is
45 how to render that XML into text. ODL might had a set of tags
48 tag docsis-state {
53 tag docsis-mode {
58 tag docsis-upstream-speed {
63 tag downstream-scanning {
73 tag signal-to-noise-ratio {
74 help "Signal to noise ratio for all channels";
79 help "Operational power of the signal on all channels";
83 format docsis-status-format {
87 Signal to noise ratio: @
91 field docsis-state;
92 field docsis-mode;
93 field docsis-upstream-speed;
94 field downstream-scanning;
96 field signal-to-noise-ratio;
107 In moving these ideas to bsd, two things had to happen: the
108 formatting had to happen at the source since BSD won't have
109 a JUNOS-like CLI to do the rendering, and we can't depend on
111 sell to the BSD community.
113 The results were that the xo_emit strings are used to encode the
123 .. _good-field-names:
128 To make useful, consistent field names, follow these guidelines:
132 to avoid scenarios where the differences between "XPath" and
137 flag can be used to generate underscores in JSON, if desired.
142 not widely used. Use "data-size", not "dsz" or "dsize". Use
143 "interface" instead of "ifname", "if-name", "iface", "if", or "intf".
145 Use <verb>-<units>
146 Using the form <verb>-<units> or <verb>-<classifier>-<units> helps in
148 uses "sent-packet" and another "packets-sent" and another
149 "packets-we-have-sent". The <units> can be dropped when it is
151 Use "receive-after-window-packets" instead of
152 "received-packets-of-data-after-window".
158 $src2/proc-table/proc-list
159 /prc-entry[prcss-id == $pid]/proc-name) {
169 In the previous example, all the names are prefixed with "proc-",
174 contain clear and useful data. You may need to augment the display
176 fields (:ref:`encoding-modifier`) to make the data useful.
179 What does "errors2" mean? No one will know. "errors-after-restart"
188 application's programmer to move between without the need to
197 After using `xolint` to find errors in your field descriptors, use
198 "`xolint -V`" to spell check your field names and to help you detect
199 different names for the same data. "dropped-short" and
200 "dropped-too-short" are both reasonable names, but using them both
201 will lead users to ask the difference between the two fields. If
203 a difference, change the names to make that difference more obvious.
211 xolint-errors.rst