[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[NOAAPORT #UFV-857333]: pqact.conf at mistral

Hi Yixin,

re: mistral status
> Does it mean that mistral is not operational?

Not doing any local processing of products on a NOAAPort receiver is
the norm for NOAAPort receivers.  Being operational for an intester has
nothing to do with local processing.  Now, if the NOAAPort data was being
ingested, but nothing was being done with it (meaning that it was not
being sent to one or more downstream LDMs), then it would most certainly
not be operational.

> Is it still missing a lot of data?

Yes.  To convince yourself of this, compare the total volume of data being
ingested on/by mistral and that of other NOAAPort ingest machines that are
feeding into the IDD:






The volumes of data being ingested by chico.unidata.ucar.edu, 
np1.ssec.wisc.edu and np2.ssec.wisc.edu are in very good agreement with each 
The volume of data being ingested by mistral is close to being zero.  For 

Cumulative Volume Summaries:

Data Volume Summary for mistral.srcc.lsu.edu

Maximum hourly volume      5.857 M bytes/hour
Average hourly volume      5.153 M bytes/hour

Average products per hour      17740 prods/hour

Feed                           Average             Maximum     Products
                     (M byte/hour)            (M byte/hour)   number/hour
IDS|DDPLUS                3.205    [ 62.191%]        3.758    13972.818
NEXRAD3                   1.581    [ 30.679%]        1.756     2968.068
HDS                       0.276    [  5.351%]        0.438      606.477
NGRID                     0.092    [  1.778%]        0.324      192.295

Data Volume Summary for leno.unidata.ucar.edu

Maximum hourly volume  11989.519 M bytes/hour
Average hourly volume   8444.583 M bytes/hour

Average products per hour     210477 prods/hour

Feed                           Average             Maximum     Products
                     (M byte/hour)            (M byte/hour)   number/hour
NGRID                  4931.447    [ 58.398%]     8069.360    34076.773
NEXRAD3                2689.483    [ 31.849%]     3192.746   111347.318
HDS                     359.134    [  4.253%]      675.443    19682.091
NOTHER                  244.851    [  2.899%]      797.069     1176.182
NIMAGE                  156.854    [  1.857%]      265.824      200.091
IDS|DDPLUS               62.814    [  0.744%]       76.459    43994.909

> If not, can we make it work?

If you recall, the quality of data ingest on mistral became MUCH worse
after mistral and the coax cable run from the LSU/SRCC NOAAPort dish were
relocated.  It seemed to me then, and it still seems to me now that the
coax signal cable now has some sort of a problem (split, bad connector(s),
etc.), or the cable is running across the source of noise that is being
picked up.  I think that the first step in returning mistral to being
a useful NOAAPort ingest machine is to figure out what exactly is causing
the noise/errors and then figure out how that situation may be fixed.

Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
Unidata HomePage                       http://www.unidata.ucar.edu

Ticket Details
Ticket ID: UFV-857333
Department: Support NOAAPORT
Priority: Normal
Status: Closed

NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.