[McIDAS #FKB-492129]: noaapxcd point data

Hi Randy,

re:
> It was my bone headed mistake yesterday. I deleted the
> remaining MD files and everything is fine today. New
> files were populated.

Very good.

> I just discovered however, that the nexrad data is no
> longer beind decoded. DMNEXR is running:
> ldm       4248  4239  1 Dec19 ?        00:24:54 DMGRID
> ldm       4250  4239  0 Dec19 ?        00:12:42 DMBIN
> ldm      27304  4239  0 13:09 ?        00:00:00 DMRAOB
> ldm      31365  4239  0 13:11 ?        00:00:00 DMMISC
> ldm      31370  4239  0 13:11 ?        00:00:03 DMSFC
> ldm      31632  4239  0 13:19 ?        00:00:50 DMSYN
> ldm       6401  4239  5 15:21 ?        00:00:56 DMNEXR
> 
> any suggestions.

I was under the impression that you were processing (FILEing) the NEXRAD
Level III data using an LDM pqact.conf action, not the McIDAS-XCD DMNEXR
method.  If my remembrance is correct, you should check your LDM log file(s)
(either ~ldm/logs/ldmd.log or ~ldm/logs/ldm-mcidas.log) to see what is
happening.  Since I do not use or recommend the use of the McIDAS-XCD Nexrad
data monitor, DMNEXR, I can not provide much help if you are using it and
having problems.

> i also meant to send this from the mcidas account:
> 
> [mcidas@noaapxcd workdata]$ stat.k
> Decoder Status Display       2007354 204711
> 
> ## Src  Ingestor   Time       Byte    Index    Index file   Origin  Wmo  
> Product
> -- ---- --------  ------  ----------- ------- -----------  ------  ---- 
> -------
> 1  DDS  INGETEXT  204709  720819040   1439792 SM07354.IDX   KWAL   SXPA   50
> 4  HRS  INGEBIN   204708  16762332             HRS.SPL 

>                                               GridF/  Grid
> ## Decoder    Time   Begptr  Lasptr     MD    Row Col       Text       Index
> -- --------  ------  ------- -------  ------  ---- -----  ------------ -------
> 1  SAODEC    204650  742512  742512   4       65 3248                SA07354
> 2  RABDEC    204644  75600   75600    24      16 21                  UJ07354
> 3  SYNDEC    204708  1439760 1439760  54       7 1351                SM07354
> 4  SHPDEC    204708  1439760 1439760  34      21 1041                SM07354
> 7  PIRDEC    204643  44736   44736    64      21 313                 UA07354
> 8  TERDEC    204643  263856  263856 FT07354
> 10 GRIB      204705  16652   16652    54004   93 18Z   0 NWFF
> 12 GRBFILER  204642
> 13 NEXRFILE  204709  N0SICX 2020
> 14 NAMMOS    204643  73872   73872    104     22 114                 FO07354
> 15 GFSMOS    204643  73872   73872    114     43 134                 FO07354
> 16 NGMMOS    204643  73872   73872    44      20 415                 FO07354

OK, so DMNEXR is running (NEXRFILE), so you are apparently processing the
NEXRAD Level III data using it instead of an LDM pqact.conf action.  In this
case I would assume that your 'mcidas' user has a REDIRECTion for the NEXRAD
Level III file name(s).  I would check the REDIRECTion and dataset definition
to make sure that nothing is amiss.  Please remember that in order for the
ADDE serving of the data to work, McIDAS must be able to find the files 
referenced
in the dataset definition.  This would be done by one of three methods:

REDIRECT
MCPATH
DIRFILE= keyword in the ADDE dataset definition

Check your ADDE dataset definition to see which method is being employed and
run the appropriate checks to make sure that it is correct.

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: FKB-492129
Department: Support McIDAS
Priority: Normal
Status: Closed