Gribfiles "Time is fixed" problem

[k.oliver@t-online.de]

Hallo,
I have got Grads 1.9b4 running on Suse Linux 9.2. I downloaded the grib
file
nww3.all.grb from ftp://ftp.polar.ncep.noaa.gov/waves/latest_run.

The grib file contains 30 timesteps. I created a control file with
grib2ctl.pl , corrected the file format with ctlkorrektur.pl and created
an
IDX file with gribmap.

oliver at blizzard:~$ /opt/grads/bin/grib2ctl.pl -verf nww3.all.grb
| ../ctlkorrektur.pl 06 > ww3.ctl
oliver at blizzard:~$ gribmap -i ww3.ctl

I started grads and opend the control file:

oliver at blizzard:~$ gradshdf
Landscape mode? (no for portrait):  y
GX Package Initialization: Size = 11 8.5
ga-> open ww3
Scanning description file:  ww3
Data file nww3.all.grb is open as file 1
LON set to 0 360
LAT set to -78 78
LEV set to 1 1
Time values set: 2005:7:11:6 2005:7:11:6

When I query the dimensions Grads tells me that the time dimension is
fixed,
although there are 30 timesteps in the gribfile.
ga-> q dims
Default file number is: 1
X is varying   Lon = 0 to 360   X = 1 to 289
Y is varying   Lat = -78 to 78   Y = 1 to 157
Z is fixed     Lev = 1  Z = 1
T is fixed     Time = 12Z11JUL2005  T = 1

How can I tell grads that the time dimension should be varying?

I checked the contents of nww3.all.grb with:
wgrib nww3.all.grb
1:0:d=05071512:WIND:kpds5=32:kpds6=1:kpds7=1:TR=0:P1=0:P2=0:TimeU=1:sfc:anl:NAve=0
2:50430:d=05071512:WDIR:kpds5=31:kpds6=1:kpds7=1:TR=0:P1=0:P2=0:TimeU=1:sfc:anl:NAve=0
3:115756:d=05071512:UGRD:kpds5=33:kpds6=1:kpds7=1:TR=0:P1=0:P2=0:TimeU=1:sfc:anl:NAve=0
4:169910:d=05071512:VGRD:kpds5=34:kpds6=1:kpds7=1:TR=0:P1=0:P2=0:TimeU=1:sfc:anl:NAve=0
5:224064:d=05071512:HTSGW:kpds5=100:kpds6=1:kpds7=1:TR=0:P1=0:P2=0:TimeU=1:sfc:anl:NAve=0
6:263646:d=05071512:WVPER:kpds5=103:kpds6=1:kpds7=1:TR=0:P1=0:P2=0:TimeU=1:sfc:anl:NAve=0
7:306606:d=05071512:WVDIR:kpds5=101:kpds6=1:kpds7=1:TR=0:P1=0:P2=0:TimeU=1:sfc:anl:NAve=0
8:366484:d=05071512:PERPW:kpds5=108:kpds6=1:kpds7=1:TR=0:P1=0:P2=0:TimeU=1:sfc:anl:NAve=0
9:409380:d=05071512:DIRPW:kpds5=107:kpds6=1:kpds7=1:TR=0:P1=0:P2=0:TimeU=1:sfc:anl:NAve=0
10:469164:d=05071512:PERSW:kpds5=110:kpds6=1:kpds7=1:TR=0:P1=0:P2=0:TimeU=1:sfc:anl:NAve=0
11:507582:d=05071512:DIRSW:kpds5=109:kpds6=1:kpds7=1:TR=0:P1=0:P2=0:TimeU=1:sfc:anl:NAve=0
12:556890:d=05071512:WIND:kpds5=32:kpds6=1:kpds7=1:TR=0:P1=3:P2=0:TimeU=1:sfc:3hr

fcst:NAve=0
13:607320:d=05071512:WDIR:kpds5=31:kpds6=1:kpds7=1:TR=0:P1=3:P2=0:TimeU=1:sfc:3hr

fcst:NAve=0
14:672646:d=05071512:UGRD:kpds5=33:kpds6=1:kpds7=1:TR=0:P1=3:P2=0:TimeU=1:sfc:3hr

fcst:NAve=0
15:726800:d=05071512:VGRD:kpds5=34:kpds6=1:kpds7=1:TR=0:P1=3:P2=0:TimeU=1:sfc:3hr

fcst:NAve=0
16:780954:d=05071512:HTSGW:kpds5=100:kpds6=1:kpds7=1:TR=0:P1=3:P2=0:TimeU=1:sfc:3hr

fcst:NAve=0
17:823920:d=05071512:WVPER:kpds5=103:kpds6=1:kpds7=1:TR=0:P1=3:P2=0:TimeU=1:sfc:3hr

fcst:NAve=0
18:866880:d=05071512:WVDIR:kpds5=101:kpds6=1:kpds7=1:TR=0:P1=3:P2=0:TimeU=1:sfc:3hr

fcst:NAve=0
19:926758:d=05071512:PERPW:kpds5=108:kpds6=1:kpds7=1:TR=0:P1=3:P2=0:TimeU=1:sfc:3hr

fcst:NAve=0
20:969660:d=05071512:DIRPW:kpds5=107:kpds6=1:kpds7=1:TR=0:P1=3:P2=0:TimeU=1:sfc:3hr

fcst:NAve=0
21:1029454:d=05071512:PERSW:kpds5=110:kpds6=1:kpds7=1:TR=0:P1=3:P2=0:TimeU=1:sfc:3hr

fcst:NAve=0
22:1067350:d=05071512:DIRSW:kpds5=109:kpds6=1:kpds7=1:TR=0:P1=3:P2=0:TimeU=1:sfc:3hr

fcst:NAve=0
23:1115954:d=05071512:WIND:kpds5=32:kpds6=1:kpds7=1:TR=0:P1=6:P2=0:TimeU=1:sfc:6hr

fcst:NAve=0
24:1166384:d=05071512:WDIR:kpds5=31:kpds6=1:kpds7=1:TR=0:P1=6:P2=0:TimeU=1:sfc:6hr

fcst:NAve=0
25:1231710:d=05071512:UGRD:kpds5=33:kpds6=1:kpds7=1:TR=0:P1=6:P2=0:TimeU=1:sfc:6hr

fcst:NAve=0
26:1285864:d=05071512:VGRD:kpds5=34:kpds6=1:kpds7=1:TR=0:P1=6:P2=0:TimeU=1:sfc:6hr

fcst:NAve=0
etc.

Maybe the problem ist that TimeU is always 1!!!

Please help! Thanks!

--
Oliver König