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

[IDD #HOP-467993]: ensg past 180 hours missing?

Hi Art,

re: look at the manifest file that is sent in the CONDUIT
 
> I'm not sure what the "manifest" files are...  I looked in our "status"
> tree under
> afs/.nwstg.nws.noaa.gov/ftp/SL.us008001/ST.opnl/MT.ensg_CY.00/RD.20060605/PT.grid_DF.gr1_RE.high
> and see status files going out to 180 hours but not beyond.  I also looked
> in status/data/nccf/com/gfs/prod (which mimicks the ftpprd.ncep.noaa.gov
> site location for the ensemble data since the transition) but only see
> spotty status files there through May 10.

I believe that Chiz answered the part about the forecasts not extending out
past 180 hours.  The existence of the manifest (catalog) of products is
discussed in the CONDUIT section of our data pages:

Unidata HomePage
http://www.unidata.ucar.edu
  Data
  http://www.unidata.ucar.edu/data/
     CONDUIT
     http://www.unidata.ucar.edu/data/conduit_data_2.html

     What is CONDUIT?
     http://www.unidata.ucar.edu/data/conduit/index.html

       CONDUIT
       http://www.unidata.ucar.edu/data/conduit/ldm_idd/index.html

The last page contains the following comment:

Since the data is injected as individual products, a status file consisting of 
the
injection time, original file size and data file name is inserted at the end of 
the
product sequence, with the name:

.status.ncep_file_name end_sequence

The status file will include a contain a catalog of each individual LDM product 
identifier
within the original data file, as well as the insertion status code returned by 
the LDM.

> The data seem to be showing up okay on NCEP's ftpprd.ncep.noaa.gov's ftp
> site, so that would lead me to believe there's some "plumbing" issue with
> getting the data out to the LDM, whatever that issue is.  I know you folks
> are busy, but I'm wondering if you can give me any estimate of when these
> data might starting flowing again via IDD...?

Apparently, Chiz was not injecting the forecasts past 180 hours.

re: were you in either the first Unidata training workshops?

> I don't recall being in the early workshops, but I was involved in the
> Implementation Working Group (IWG) back in the late 80's which brings back
> some fond memories.  I did check the pennant list to make sure Penn State
> was there... couldn't imagine not being there... John Dutton (our former
> department head and college dean) was involved in the initial formation of
> Unidata and I would have guessed he would have hand-carried a pennant for
> posting on the wall...  or I might have even done it but don't remember!
> That's getting to be long time ago now :)

I agree, it is getting to be a LONG time ago now.  I have been at Unidata for
18 years!

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: HOP-467993
Department: Support Datastream
Priority: Normal
Status: Closed