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

[McIDAS #AOE-843254]: problem with DEV=T

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [McIDAS #AOE-843254]: problem with DEV=T
  • Date: Wed, 05 May 2010 11:57:24 -0600
Hi Owen,

re:
> I'm having a problem with getting DEV=T to send some grid data to a text
> file whilst issuing the command form a mcidas .sh script.that is called
> by my crontab.
> 
> If I issue the following command from my unix prompt it works fine and
> sends the requested data to the designated text file.
> 
> grdinfo.k  RTGRIDS/NAM LIST DAY=125 TIME=12 FDAY=128 FTIME=00 GRIB=211 X
> X X LAT=40 42 LON=123 125 PARAM=U V Z LEV=1000 950 900 850 800 750 700
> 650 600 550 500 450 400 350 300 250 200 150 100 NUM=ALL DEV=T
> THD_125_12_128_00.GEO
> 
> but when the command is part of a batch file called by a mcidas .sh
> script I get the following error
> 
> GRDINFO RTGRIDS/NAM LIST DAY=125 TIME=12 FDAY=128 FTIME=00 GRIB=211 X X
> X LAT=40 42 LON=123 125 PARAM=U V Z LEV=1000 950 900 850 800 750 700 650
> 600 550 500 450 400 350 300 250 200 150 100 NUM=ALL DEV=T
> THD_125_12_128_00.GEO
> Problem with DEV= global keyword
> GRDINFO failed, RC=1
> 
> 
> any ideas?

Hmm...  I do not have this problem in the simple test I setup:

- copy your GRDLIST invocation to the file TEST.BAT in my $MCDATA directory

- copy ~mcidas/data/mcrun.sh to my $MCDATA directory as myrun.sh

- edit $MCDATA/myrun.sh:

  - add invocation of BATCH file:

    batch.k TEST.BAT

  - make sure that MCDATA, MCPATH, MCBIN, etc. are set correctly

- run myrun.sh from the Unix command line:

  ./myrun.sh

The output is the file THD_125_12_128_00.GEO.

Thoughts:

- is it possible that you not correctly set the McIDAS environment
  variables needed in your .sh script?

- is it possible that you are trying to write to a directory that
  you do not have permission to write to?

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