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

[IDD #LDE-365303]: Duplicate(?) /pNCRVAX in IDD feed?



Hi Daryl,

re:
> Thanks for the response. 

I just verified that both of our "operational" NOAAPort ingest machines
are inserting two NCR products from VAX every 5 minutes.  Here is a snippit
of a 'notifyme -vl- -f NEXRAD3 -o 3600 -p NCRVAX' invocation I just ran
on one of the ingest machines:

~: notifyme -vl- -f NEXRAD3 -p NCRVAX -o 3600
Aug 19 14:06:54 notifyme[4945] NOTE: Starting Up: localhost: 20150819130654.491 
TS_ENDT {{NEXRAD3, "NCRVAX"}}
Aug 19 14:06:54 notifyme[4945] NOTE: LDM-5 desired product-class: 
20150819130654.491 TS_ENDT {{NEXRAD3, "NCRVAX"}}
Aug 19 14:06:54 notifyme[4945] INFO: Resolving localhost to 127.0.0.1 took 
0.000566 seconds
Aug 19 14:06:54 notifyme[4945] NOTE: NOTIFYME(localhost): OK
Aug 19 14:06:55 notifyme[4945] INFO:       9342 20150819130947.996 NEXRAD3 
495994825  SDUS52 KJAX 191304 /pNCRVAX
Aug 19 14:06:55 notifyme[4945] INFO:       9343 20150819130948.020 NEXRAD3 
495994836  SDUS52 KJAX 191304 /pNCRVAX
Aug 19 14:06:55 notifyme[4945] INFO:       9136 20150819131438.212 NEXRAD3 
496005522  SDUS52 KJAX 191309 /pNCRVAX
Aug 19 14:06:55 notifyme[4945] INFO:       9136 20150819131439.952 NEXRAD3 
496005536  SDUS52 KJAX 191309 /pNCRVAX
Aug 19 14:06:55 notifyme[4945] INFO:       8823 20150819131928.968 NEXRAD3 
496016860  SDUS52 KJAX 191314 /pNCRVAX
Aug 19 14:06:55 notifyme[4945] INFO:       8823 20150819131928.971 NEXRAD3 
496016866  SDUS52 KJAX 191314 /pNCRVAX
Aug 19 14:06:55 notifyme[4945] INFO:       8681 20150819132419.521 NEXRAD3 
496027516  SDUS52 KJAX 191319 /pNCRVAX
Aug 19 14:06:55 notifyme[4945] INFO:       8680 20150819132419.547 NEXRAD3 
496027519  SDUS52 KJAX 191319 /pNCRVAX

The output from our other NOAAPort ingest machine (which is feeding from a
different NOVRA S300n) is identical to this.

Things to note:

- the time stamp difference between the images in a pair range
  from a handful of milliseconds (e.g., 4 ms for the one that is
  8823 in size) to over a second (e.g., 1.74 s for the one that
  is 9136 bytes in size)

- the size of the duplicate product can differ from the first
  processed, but not by much

It seems to me that a time difference of over 1 s indicates that
duplicate products are being produced at the radar itself and
is, therefore, not some sort of an artifact of the ingest processing.

re:
> Would it help if I sent a complete list of
> RADARs with this issue?  There are a 10-20 of them, I estimate.

Perhaps.  We would pass this list along to NWS folks for their
review and possible action.  There is not much we can do at the
ingest since the products pass the duplicate MD5 signature test.

Cheers,

Tom
--
****************************************************************************
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: LDE-365303
Department: Support IDD
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.