[IDD #YYT-234815]: Ship and Synoptic obs not received after 06-07Z every day since 9/1

Hi Greg,

re: typos in pattern-actions: \2:mm should be \1:mm
> Interesting observations. Things do seem to be working better today
> after correcting the typo in the pqact file. I do see synoptic and
> ship files for all times today.

Excellent!

re:
> I'm not sure I follow what you are saying here. The filenames themselves
> look ok to me. Are you saying the contents of these files don't make
> sense when compared to the filenames?

I guess that what I really meant is that I would not expect what are
presumably real-time observations to be received today (Sept 8) when
the observations are for late August.

re: the day and time in one of the bulletins saved from today
> This seems very odd as I thought LDM would parse the fist line of
> your example and convert the 280600 into the correct filename even
> if the ob arrived on the wrong date.

The LDM's pqact utility does not read the contents of a product
to determine patterns which are to be matched. It compares the
Product ID with the pattern(s) that a user specifies.  The Product
ID for a product is created when the product is first put into an
LDM queue; in this case, it would be done by our NOAAPort ingest package,
which uses the WMO header for a product to create the Product ID.

re:
> I notice I also have a large number of files for dates and times that
> don't physically exist or haven't happened yet. (90% of these are ship
> and synoptic obs)

Even after correcting the \2:mm reference?

I don't see this on my workstation.  In fact, I only see two files whose times 
are
in the future, and that is only by a fraction of an hour:

/local/ldm/data/dynamo% date -u
Thu Sep  8 21:09:17 UTC 2011

/local/ldm/data/dynamo% ls -1 | sort
2011082718.SYN
2011082800.SYN
 ...
2011090822.SHP
2011090822.SYN

/local/ldm/data/weather/ddp% ls -1 | sort
2011082718.SYN
2011082800.SYN
 ...
2011090822.SHP
2011090822.SYN

re:
> Is this a typically amount of error to be seeing (26 files for the 3 types)?

I am unsure of what you are asking.  I see two files that have hour portions of 
their
file names that are "in the future" -- meaning for 22Z when it was 21:09Z.

re: did you implement the fix I suggested in yesterday afternoon's email (\2:mm 
-> \1:mm)?
> Looks like that was my main problem. Too much cutting and pasting.

Been there; done that :-)

re:
> Where can I find documentation that describes the \1:yyyy and \1:mm 
> functionality in LDM?

Unidata HomePage
http://www.unidata.ucar.edu

  Software
  http://www.unidata.ucar.edu/software

    Local Data Manager
    http://www.unidata.ucar.edu/software/ldm/

      Documentation and Training
      http://www.unidata.ucar.edu/software/ldm/#documentation

        LDM documentation page
        http://www.unidata.ucar.edu/software/ldm/ldm-current/

LDM Reference
http://www.unidata.ucar.edu/software/ldm/ldm-current/basics/index.html

  Configuration Files

  The pqact Configuration-File, pqact.conf
  http://www.unidata.ucar.edu/software/ldm/ldm-current/basics/pqact.conf.html

Look in 'String Substitution in Action-Arguments' for 'Temporal Subexpression 
Replacement'.
The text is not explicit in warning the user that the field that needs to be
matched against is the day, but the example does show what to do.


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: YYT-234815
Department: Support IDD
Priority: Normal
Status: Closed