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

[McIDAS #YUS-533577]: Accessing archived NEXRAD Level III images in ADDE

Hi Randy,

> Interesting. When i re-issue the DSSERVE command it
> does NOT complain,

Well, DSSERVE will never complain _unless_ you have a syntax error
in your invocation command line.  DSSERVE does not check to see if
the data you are trying to use in a dataset is of the type that you
are saying it is.

> however, IMGLIST still shows no files.
> Interestingly, the help.k DSSERVE does not list NEXR
> is a valid format type.

Good catch!  That is a glaring omission form the documentation.

And, oops: the DSSERVE command should be:


Also, you should use the regular expression specified as the value of
DIRFILE with 'ls' to see if you have the correct pattern.  Example:

ls /d2/nexrad/lwx*.n0r

If the 'ls' invocation shows the expected list of files, then the pattern
is correct.  If it does NOT show the expected list of files, then the
pattern is incorrect.

Finally, the files specified in the dataset must be readable by the user
trying to access them.

Really finally, if the IMGLIST RJA/NX ID=<id> still doesn't work, then
you should turn trace debugging on:


The file 'trce' should be created in your McIDAS working directory if
the dataset is LOCAL-DATA or in the ~mcidas/mcidas/data if the dataset
is served through the remote ADDE server.  Look through the file for
clues as to why the serving is failing.


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: YUS-533577
Department: Support McIDAS
Priority: Low
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.