[IDD #KSB-345648]: LDM Glider data. (notifyme)

Hi Chuan-Yuan,

re:
> What I know is the all glider data is passing to IOOS Glider DAC and then 
> broadcasting
> through GTS in BUFR format.

OK.

re:
> And it also looks like the IOOS Glider DAC is (relevant) related to noaa.gov. 
>  Thus, I
> believe the NOAAport broadcast Network should contains the glider data.

Your reasoning is sound, but there is still the underlying assumption that
the Weather Service has decided that those data are needed for operational
forecasting and so have been added to NOAAPort.

re:
> However, could you tell me where can I check whether the NOAAport broadcast 
> it?

Good question.  I don't know specifically, but I would send an email to
Becky Cosgrove and the Dataflow team to see if they can answer your quetion:

Rebecca Cosgrove - NOAA Federal <address@hidden>
Dataflow Team <address@hidden>

re:
> Meanwhile, I still not quite understand the notifyme and pqact.conf.

OK.

re:
> Saying that I can when I use notifyme, I do find
> 
> notifyme -vl- -f HDS -h idd.unidata.ucar.edu -o 8640000 -p '^IO.* '
> Aug 23 22:01:58 notifyme[17398] NOTE: Starting Up: idd.unidata.ucar.edu: 
> 20170515220158.020 TS_ENDT {{HDS,  "^IO.* "}}
> Aug 23 22:01:58 notifyme[17398] NOTE: LDM-5 desired product-class: 
> 20170515220158.020 TS_ENDT {{HDS,  "^IO.* "}}
> Aug 23 22:01:58 notifyme[17398] INFO: Resolving idd.unidata.ucar.edu to 
> 128.117.140.3 took 0.001277 seconds
> Aug 23 22:01:58 notifyme[17398] NOTE: NOTIFYME(idd.unidata.ucar.edu): OK
> Aug 23 22:02:03 notifyme[17398] INFO:      212 20170823202529.339     HDS 
> 27940141  IOBF08 KWNB 232000
> Aug 23 22:02:03 notifyme[17398] INFO:      233 20170823202529.339     HDS 
> 27940142  IOBF08 KWNB 232000 RRC
> Aug 23 22:02:03 notifyme[17398] INFO:      216 20170823202529.339     HDS 
> 27940143  IOBF08 KWNB 232000 RRB
> Aug 23 22:02:03 notifyme[17398] INFO:      216 20170823202529.339     HDS 
> 27940144  IOBF08 KWNB 232000 RRA
> Aug 23 22:02:03 notifyme[17398] INFO:      205 20170823202535.348     HDS 
> 27940196  IOBF08 KWNB 232000 RRE
> Aug 23 22:02:03 notifyme[17398] INFO:      216 20170823202535.373     HDS 
> 27940197  IOBF08 KWNB 232000 RRD
> Aug 23 22:02:03 notifyme[17398] INFO:      216 20170823202537.339     HDS 
> 27940198  IOBF08 KWNB 232000 RRG

OK< this says that idd.unidata.ucar.edu is receiving products whose Product IDs 
start
with 'IOBF'.  The next question is if your machine is receiving those same 
products.
You would check this by removing the '-h idd.unidata.ucar.edu' from your 
'notifyme'
invocation:

notifyme -vl- -f HDS -o 8640000 -p '^IO'

NB:

Two things changed: I removed '-h idd.unidata.ucar.edu' and I simplified the
pattern field from -p '^IO.* ' to -p '^IO' as the ".*' after the '^IO' is
not needed.

re:
> In this case, I should be able to obtain the IOBFii data via the modification 
> of
> pqact.conf, shouldn’t I?

Yes, IF your machine is receiving the products.

Question:

- what are the REQUEST line(s) in your LDM configuration file?

  The simplest way to answer this is send the output of:

  <as 'ldm'>
  cd ~ldm
  grep -i ^request etc/ldmd.conf

re:
> HDS   ^IO.... KWNB (..)(..)
> FILE  -close   -overwrite data/ldm/bufr2/(\1:yy)(\1:mm)\1\2.bufr

This action looks like it should work IF you are receiving the products to
be matched in your action.

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: KSB-345648
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.