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

[IDD #TVO-907725]: UNIWISC ingest stopped working

Hi,

re:
> Thanks Tom,
> 
> We were receiving all the MCIDAS actions I forwarded last time.

OK, good.  This indicates two things:

- you are receiving the UNIWISC feed

- the actions that matched the old products are still working
  for the remaining old products in the UNIWISC feed

re:
> I just tested this pattern action for the GOES-17 CONUS 0.64um Visible
> Sector and  didn’t work.
> 
> UNIWISC ^pnga2area Q. (M2C02) (.*) (.*)_IMG (.*)um (.*) (........) (......)
> FILE    -close  
> /usr/local/ldm/data/gempak/images/sat/\3/Mesoscale-2/\5/\4/\6/\4_\6_\7

Two comments:

- this pattern will _not_ match any CONUS image

  'M2' in the '(M2C02)' will match Mesoscale-2 images

  Replacing 'M2' with "CN" in the extended regular expression should do
  what you want as it will match the CONUS images.

- I don't know if your action entry is properly formatted

re:
> Since MCIDAS entries were working, I can I assume we are setup to receive
> UNIWISC feed?

Yes.  There is no way that they would work if you were NOT receiving the
UNIWISC feed.  The fact that they are still working shows that you ARE
receiving the feed, and that, in turn, means that the machine that you
are REQUESTing the feed from has ALLOWed you to REQUEST the feed.

Comment:

The LDM utility 'notifyme' is one of the most useful commands available
to you: it can tell you if you are receiving products, if you are ALLOWed
by an upstream to REQUEST products, and, in this case most importantly,
to test extended regular expressions to see if they do what you want
then to do.

Example test of the modified extended regular expression that would result
from the change I suggest above:

<as 'ldm'>
notifyme -vl- -f UNIWISC -h <upstream feed host> -p "pnga2area Q. (CNC02) (.*) 
(.*)_IMG (.*)um (.*) (........) (......)"

All you need to do to use this example is replace:

<upstream feed host>

with the fully qualified machine name of the machine that
you are already REQUESTing the UNIWISC (aka MCIDAS) feed
from.  When you do, you will see that the pattern matches
both GOES-16 and GOES-17 CONUS images.

The final thing to do in troubleshooting the new pattern-action
file action that you add/will add is:

-- add/modify an action in the pattern-action file

-- run:

ldmadmin pqactcheck

If this shows no errors, run:

ldmadmin pqactHUP

'ldmadmin pqactcheck' does a gross syntax check on all pattern-action
files that you are using via 'EXEC' lines for 'pqact' in your LDM
configuration file, ~ldm/etc/ldmd.conf.  'ldmamdin pqactHUP' sends
a HUP signal to the lead LDM process, and it, in turn, sends a HUP
signal to each 'pqact' invocation telling it/them to reread their
pattern-action file(s) actions.  When adding new or modifying existing
actions to a pattern-action file that is actively being used, you
do not have to stop and restart the LDM for the new/modified action(s)
to take effect.  This is different from when changes are made to the
LDM configuration file as those changes will only take effect upon
stopping and restarting the LDM.

> Thanks,
> Bereket
> 
> 
> -----Original Message-----
> From: Unidata IDD Support <address@hidden>
> Sent: Thursday, March 12, 2020 8:09 AM
> To: Habtezion, Bereket <address@hidden>
> Cc: address@hidden
> Subject: [IDD #TVO-907725]: UNIWISC ingest stopped working
> 
> *****CAUTION: This email was sent from an EXTERNAL source. Think before 
> clicking links or opening attachments.*****
> 
> Hi,
> 
> re:
> > Thanks Tom!
> > Do I need any REQUEST in the ldm.conf if I we want to get it via noaaport?
> 
> The UNIWISC (aka MCIDAS) IDD feed is _not_ in the NOAAPort SBN, it is a 
> datastream that we create here in Unidata.  I figured that you knew this 
> since the actions you sent along previously are for the MCIDAS (more properly 
> named UNIWISC) IDD feed.  Assuming you are receiving the UNIWISC feed, all 
> you need to do is make sure that you are receiving all of the feed and update 
> your LDM pattern-action file to include the actions needed to process the new 
> GOES-16/17 imagery.
> 
> Cheers,
> 
> Tom
> --
> ****************************************************************************
> Unidata User Support                                    UCAR Unidata Program
> (303) 497-8642                                                 P.O. Box 3000
> address@hidden                                   Boulder, CO 80307
> ----------------------------------------------------------------------------
> Unidata HomePage
> ****************************************************************************
> 
> 
> Ticket Details
> ===================
> Ticket ID: TVO-907725
> 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.
> 
> 
> 

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: TVO-907725
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.