Hi Gilbert, et. al.,
This a quick note to clarify something that Gilbert said in his
email earlier today.
re:
>Put these two tabs side by side in IE8/Firefox 3.63:
>
>http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_vol_nc?NEXRAD3+noaaport.admin.niu.edu
>
>http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_vol_nc?NEXRAD3+noaaport.unidata.ucar.edu
>
>Note: the dropouts I had over the past few days was to install a new
>kernel and do other maintenance on the server. But as of 13Z, UNIDATA is
>clearly losing data. College of Dupage's VBER on their receiver actually
>went to1 x 10 ^ -5, now they're back to 1 x 10 ^ -2 and getting virtually
>nothing.
>
>When a 3.8 meter dish certified by the NWS is losing data, something is
>wrong. Who can I pass this information along to so they can correct it?
What Gilbert was not aware of was we were working on the configuration
of noaaport.unidata.ucar.edu (aka desi.unidata.ucar.edu), so the
dropouts seen in its NEXRAD3 volume plot were/are not a result of
low/bad signal, but, rather, of our upgrade work.
We are not concerned by the data missed on noaaport.unidata.ucar.edu
because we operate two other NOAAPort ingest systems here at UCAR
(burns.unidata.ucar.edu and jackie.unidata.ucar.edu) and they are all
getting their signal off of the same 3.8m dish. Also, since there are
several machines at UCAR and at user sites feeding data redundantly
into the IDD, the chance for chance that products will be missed
because of a problem on one machine is minimized.
A good way to compare NEXRAD3 (or any other NOAAPort-based feed) is to
look at any/all of the ingest machines at UCAR, and the same feed on
either of the aggregation machines for the toplevel IDD relay node that
we maintain, idd.unidata.ucar.edu:
burns.unidata.ucar.edu:
http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_vol_nc?NEXRAD3+burns.unidata.ucar.edu
jackie.unidata.ucar.edu:
http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_vol_nc?NEXRAD3+jackie.unidata.ucar.edu
noaaport.unidata.ucar.edu (aka desi.unidata.ucar.edu):
http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_vol_nc?NEXRAD3+noaaport.unidata.ucar.edu
oliver.unidata.ucar.edu (IDD relay cluster accumulator front end):
http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_vol_nc?NEXRAD3+oliver.unidata.ucar.edu
emo.unidata.ucar.edu (IDD relay cluster accumulator front end):
http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_vol_nc?NEXRAD3+emo.unidata.ucar.edu
As to reception quality on our NOAAPort ingest machines, here is a S75_TEST
listing from one of our ingest machines:
Device Firmware Ver 3, Rev. 1 --- RF Firmware Codes 0x506
--------------------------------------------------------------------------
Symbol Rate 6.349000 Msps Frequency 1193.500000
The viterbi Bit Error Rate is 0.0000e+00 Viterbi Rate 7
LNB Power On, Polarization = 1, Band = 1
Signal Strength: 73, Signal Lock: 1, Data Lock: 1, Uncorrectables: 0
The indicated signal strength (73), locked frequency (1193.5) and
viterbi Bit Error Rate (0.0000e+00) have not changed on this machine in
the past 3 days. We may be lucky that the changes to broadcast signal
strength have not effected our ingest quality.
Cheers,
Tom
Tom Yoksas
Unidata User Support
--
********************************************************************** <
Unidata User Support UCAR Unidata Program <
(303)497-8643 P.O. Box 3000 <
support@xxxxxxxxxxxxxxxx Boulder, CO 80307 <
---------------------------------------------------------------------- <
Unidata Web Support http://www.unidata.ucar.edu/support <
---------------------------------------------------------------------- <
