[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GEMPAK #ZMJ-753300]: GFS Gempak issue
- Subject: [GEMPAK #ZMJ-753300]: GFS Gempak issue
- Date: Thu, 06 Sep 2007 11:19:34 -0600
> So basically with the default files, gempak (nmap2) doesnt support
> the gfs other than the then?
>
> Ray
>
Ray,
Not at all. You have full control over the configuration.
My suggestion if to define GFS in $GEMTBL/config/datatype.tbl
as the data set you want to use as "GFS" I define it to
be the global 1 degree, but if you are happy with CONUS 40km,
then define it to be the same as the GFS212 entry.For CONDUIT
recipients, the global gfshd (grid #004) is the highest resolution.
NMAP2 uses the model list in $GEMTBL/nmap/mod_res.tbl to
populate the list of available choices. I expand the longer range
model choices that come from NCEP from:
dgex;gfs;gfshd
to
dgex;gfs;gfshd;gfs002;gfs003;gfsthin
But, if you want to ass GFS211 and GFS212 to thatlist, it can either be simply
done
with a global searsh/replace in mod_res.tbl, or you can regenerate the
mod_res.tbl file
by going to $GEMTBL/nmap/mod_res and running "mod_res.csh" after editing the
list in "mod_res.awk".
Steve Chiswell
Unidata User Support
>
>
> -----Original Message-----
> From: "Unidata GEMPAK Support" <address@hidden>
> To: address@hidden
> Cc: address@hidden
> Date: Thu, 06 Sep 2007 09:07:43 -0600
> Subject: [GEMPAK #ZMJ-753300]: GFS Gempak issue
>
>
> Ray,
>
> The gfs 211 and 212 grids are aliased in datatype.tbl
> as GFS211 and GFS212.
>
> As an example:
>
> GEMPAK-GDINFO>l
> GDFILE = GFS211
> LSTALL = yes
> OUTPUT = t
> GDATTIM = all
> GLEVEL = all
> GVCORD = all
> GFUNC = all
> >r
>
> GRID FILE: /data/ldm/gempak/model/gfs/2007090606_gfs211.gem
>
>
> GRID NAVIGATION:
> PROJECTION: LCC
> ANGLES: 25.0 -95.0 25.0
> GRID SIZE: 93 65
> LL CORNER: 12.19 -133.46
> UR CORNER: 57.29 -49.38
>
> GRID ANALYSIS BLOCK:
> UNKNOWN ANALYSIS TYPE
>
> Number of grids in file: 3414
>
> Maximum number of grids in file: 10000
>
> NUM TIME1 TIME2 LEVL1 LEVL2 VCORD PARM
> 1 070906/0600F000 180 0 PDLY CAPE
>
> 2 070906/0600F000 180 0 PDLY CINS
>
> 3 070906/0600F000 180 150 PDLY TMPK
>
> 4 070906/0600F000 180 150 PDLY RELH
>
> 5 070906/0600F000 180 150 PDLY UREL
>
> 6 070906/0600F000 180 150 PDLY VREL
>
> 7 070906/0600F000 150 120 PDLY RELH
>
> 8 070906/0600F000 150 120 PDLY TMPK
>
> 9 070906/0600F000 150 120 PDLY UREL
> <etc>
>
> The GFS alias in datatype.tbl I have defaulted to the global grid #003
> which is available in CONDUIT, but since you don't have #003 files below,
> you won't
> see any output for those. There is no gfs01 template that I provide.
>
> BTW,
>
> I built 5.10.3 under FC4 here using G77 and the required
> motif libraries and dependencies. See note on using g77
> as a compiler instead of gfortran as you probably have an old
> 4.0.2 gfortran on your old fc4 distribution.
>
> Steve Chiswell
> Unidata User Support
>
>
> > Here is the issue...
> >
> > I have Gempak 5.10.2 running, (can't compile 5.10.3 on Fedora Core 4),
> > and cannot display any of the GFS except the "thin".
> >
> > These files are present in the model/gfs dir:
> >
> > -rw-r--r-- 1 ldm mcidas 4737536 Sep 5 06:48 2007090506_gfs202.gem
> > -rw-r--r-- 1 ldm mcidas 3726336 Sep 5 06:48 2007090506_gfs203.gem
> > -rw-r--r-- 1 ldm mcidas 49382400 Sep 5 06:48 2007090506_gfs211.gem
> > -rw-r--r-- 1 ldm mcidas 964096 Sep 5 05:28 2007090506_gfs212.gem
> > -rw-r--r-- 1 ldm mcidas 23865856 Sep 5 06:48 2007090506_gfs213.gem
> > -rw-r--r-- 1 ldm mcidas 47484416 Sep 5 06:15 2007090506_thin.gem
> >
> > The "thin" shows on the gempak load list, and I can display it, but
> nothing
> > else shows in the "gfs" "gfs01" etc.
> >
> > Appreciate any idea.
> >
> > Ray Weber
> > MA Skywarn
> >
> >
> >
> >
>
>
> Ticket Details
> ===================
> Ticket ID: ZMJ-753300
> Department: Support GEMPAK
> Priority: Normal
> Status: Closed
>
>
Ticket Details
===================
Ticket ID: ZMJ-753300
Department: Support GEMPAK
Priority: Normal
Status: Closed