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

[McIDAS #IGY-419036]: raobcon

Hi Paul,

> ---- --------- ------------ ------------ ---------
> -rw-      9985 Mar 18 15:24 RAOBCON.CORE /home/mcidas/data
> -rwx       215 Mar 18 15:05 RAOBCON.SITE /home/mcidas/workdata
> -rwx       216 Mar 24 15:37 RAOBCON.USER /home/mcidas/dat

Presumably, the directory for RAOBCON.USER is /home/mcidas/data (the listing
above is missing the trailing 'a').

The things that jump out at me from this DMAP listing are:

- the time stamp on RAOBCON.(CORE|SITE) are older than my email
  explaining the apparent error in your DELTZ definition.  This
  suggests to me that neither file contains the corrected definition
  which would explain the failure/error

- The notion is that the .USER file should be in one's $MCDATA
  directory, and the .SITE file should be in the ~mcidas/data directory.
  Your listing shows these being reversed; I would change this.

  I am not suggesting, however, that the location is in any way a cause
  of failure.  All files should be read/used as long as the directories
  in which the files exist are in one's MCPATH.  I know that yours
  are because the files wouldn't be listed in a DMAP output if they
  were not.

So, I think that you should:

- review the content of RAOBCON.SITE to make sure that your DELTZ
  definition is the same as it is in RAOBCON.USER

- move RAOBCON.SITE back to the ~mcidas/data directory

- move RAOBCON.USER to the ~mcidas/workdata directory


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: IGY-419036
Department: Support McIDAS
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.