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

20040511: GRDCOPY in NcIDAS-X 2003

>From: Eirh-Yu Hsie <address@hidden>
>Organization: Aeronomy Laboratory/NOAA
>Keywords: 200405111727.i4BHRQtK005371 McIDAS GRDCOPY

Hsie,

>I have a question regarding to GRDCOPY command in McIDAS-X v2003.  The 
>system is a Sun Sparc running Solaris 5.8.  The following command only 
>give me one match:
>
>% grdcopy.k RTGRIDS/ETA MYDATA/GRIDS.132 DAY=2004132 TIME=12 GPRO=LAMB 
>NUM=ALL FHOUR=0 12 24 36 48 LEV=1000 850 700 500 250 PARAM=Z T U V
>
>% grdinfo.k MYDATA/GRIDS.132 LIST X GRI=1 LAST
>Listing data from  48-hour forecast V    Grid at 250 MB   from ETA
>Grid is at 120000 UTC on 2004132 from dataset: MYDATA/GRIDS
>     Row    Col    Latitude    Longitude    Value         Units  Level 
>Param
>      1       1      54.838     153.092   0.2042000E+02    MPS  250  MB   V
>GRDINFO Done, Number of grids listed=1

OK.

>It seems to me that it only give me the last match (V at 250 mb and 
>48-hr forecast).  Is this the corect behavior?

No, all grids matching the selection criteria should be copied.  What
I believe is happening is that GRID0132 was created to allow only
one grid.  If you rerun your commands after first creating an
output GRID file that can contain a lot of grids, it will succeed:

igu.k DEL 132
igu.k MAKE 132 1000
grdcopy.k RTGRIDS/ETA MYDATA/GRIDS.132 DAY=2004132 TIME=12 GPRO=LAMB NUM=ALL 
FHOUR=0 12 24 36 48 LEV=1000 850 700 500 250 PARAM=Z T U V
grdinfo.k MYDATA/GRIDS.132 LIST X GRI=1 LAST

A different way to list the grids in a GRID file is by using GRDLIST:

grdlist.k MDATA/GRIDS.132 NUM=ALL

Cheers,

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically 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.