[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
20010205: 20010201: 20010201: GEMPAK's gdplot2
- Subject: 20010205: 20010201: 20010201: GEMPAK's gdplot2
- Date: Mon, 05 Feb 2001 10:31:52 -0700
Stephen,
You don't have to recompile anything when making changes in datatype.tbl or
mod_res.tbl. They are read at startup by nmap/nmap2. But, you do have to
restart the program tpam to reread the tables.
If your not finding the files, it could be a typo/path/ problem in the config
file,
orsomething else minor.
Let me know.....
Steve Chiswell
Unidata User SUpport
>From: Stephen Sinnis <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200102051658.f15GwpX10810
>Chiz,
>
>I only have one more last question :) I am not seeing anything at all in
>nmap2, until I included the line "GDFILE=2001020415_reg.gem", in the
>$NMAP_RESTORE/prcp file that I was using.
>
>Do I have to recompile the Gempak package after modifying the
>$GEMTBL/config/datatype.tbl, and $GEMTBL/mod_res.tbl files when defining new
>gem files?
>
>Thanks again for your help.
>
>Stephen Sinnis, The Weather Network
>****************************************************************************
>
>Stephen,
>
>I think I see what you are seeing.
>
>The cmcreg data I have is 6 hourly with accumulated precipitations at
>each forecast time, eg P06M^f06, P12M^f12, P18M^f18, P24M^f24....etc to
>P48M^f48
>
>When I use just the 12hr_mm restore file (eg p12m, I get displays at
>F012, F024 and f048 with blank screens at the other times.
>
>You are correct that the P--M parameter allows the software to accumulate
>over time.
>This is done through both PRXX grids (precipitation rate grids) or major
>and subinterval P--M grids, eg: DG_PRFT().
>However, the code only has the subinterval accumulations at :
> cdt / '03', '06', '09', '12', '24', '48' /
>
>That is why I only get 12 hour precip grids at 12, 24 and 48. There is no
>18 hour or 30 hour accumulation interval etc.
>
>What the code is trying to do is create a p12m grid at each forecast time
>step from the accumulating value at each forecast time, eg p12M, p24m, p48m.
>
>The eta for instance gives us P06m at F006, F018, F030, F042, F054 and
>P12M at F012, F024, F036, F048, F060. The gempak code actually subtracts
>the P06M from the P12M to get the P06M values at all the forecast times.
>
>So, I think the problem lies in whether you want a constant period of
>accumulation
>(eg 6 hours) or just the total accumulation (growing with time). To
>accomplish
>the first case, you could add these times into the source code (both major
>and
>subinterval times).
>
>To see the the accumulation values, its probably easiest just to rename the
>grids so that the code doesn't interpret the data as [PCS]--M grids
>(gempak will actually try to use P = S + C algebra to calculate total
>precip from largescale and convective grids too).
>
>For instance:
>#!/bin/csh -f
>
>@ COUNT = 6
>while ($COUNT <= 48)
> if($COUNT < 10) then
> set HOUR=0${COUNT}
> else
> set HOUR=$COUNT
> endif
> echo $HOUR
> gddiag << EOF
> gdfile = $MODEL/2001020112_cmcreg.gem
> gdoutf = $MODEL/2001020112_cmcreg.gem
> glevel = 0
> gvcord = none
> GFUNC = p${HOUR}m
> GDATTIM = f${HOUR}
> GRDNAM = ptot
> gpack =
> r
>
> e
>EOF
>
> @ COUNT = $COUNT + 6
>
>end
>
>
>
>In the restore file, I just plotted GFUNC = PTOT. This gives me the growing
>blobs for the total accumulation as CMC is creating.
>
>So I guess the question is, what do you expect to see: totals, or the
>sub(PyyM, PxxM) type of plots?
>
>Steve Chiswell
>Unidata User Support
>
>
>
>
>
>
>
>
>>From: Stephen Sinnis <address@hidden>
>>Organization: UCAR/Unidata
>>Keywords: 200102012237.f11MbOX28437
>
>>Steve,
>>
>>I think I might of missed something in one of the configuration files which
>>identifies the GEM to the NAWIPS. Everything is ok if I use the other
>>models like eta, mrf, ruc....
>>
>>I can use gdplot2 and see any on the GEM's precip grids if I specify
>>PXXM^fXX for gdpfunc, but the same assignment does not work with NMAP2. I
>>have included the contents of the NTS file I use ok with gdplot2. What's
>>also neat is that if I specify just p03m, I get the same as if i specify
>>sub(pYYm,pXXm), where YY is XX+3hr. for each time step (from gdplot2).
>>
>>!
>>! Restore File : reg_precip_3_48
>>!
>>! Log:
>>! S.W.Sinnis/Pelmorex 12/00 Initial creation
>>!
>>GDATTIM f003-f012-003
>>GLEVEL 0
>>
>>GVCORD none
>>
>>PANEL 0
>>
>>SKIP 0
>>
>>SCALE 0
>>
>>GDPFUN p03m^f3!p06m^f6!p09m^f9!p12m^12
>>TYPE f
>>CONTUR 1
>>
>>CINT
>>LINE
>>FINT .01;.1;.25;.5;.75;1;1.25;1.5;1.75;2;2.5;3;4;5;6;7;8;9
>>FLINE 0;21-30;14-20;5
>>HILO 31;0/x#2/0.1-99//100;0/y
>>HLSYM 1.5
>>CLRBAR 1
>>
>>WIND
>>
>>REFVEC
>>
>>TITLE 5/-1/~ Total Cummulative Precipitation (mm)
>>TEXT 1/21//hw
>>
>>GAREA grid
>>CLEAR yes
>>
>>STNPLT
>>
>>SATFIL
>>
>>RADFIL
>>
>>STREAM
>>
>>POSN 4
>>
>>COLORS 2
>>
>>MARKER 2
>>
>>GRDLBL 5
>>
>>LUTFIL none
>>FILTER yes
>>-----Original Message-----
>>From: Unidata Support [mailto:address@hidden]
>>Sent: Thursday, February 01, 2001 5:12 PM
>>To: Stephen Sinnis
>>Cc: address@hidden
>>Subject: 20010201: GEMPAK's gdplot2
>>
>>
>>
>>Stephen,
>>
>>I was able to plot the 12mm precip in NMAP2 by adding cmc entry to the
>>existing
>>PRECIP_12hr_MM entry in mod_res.tbl. You mentioned creating your own
>>entry in $NMAP_RESTORE/prcp/- so not using the existing product?
>>
>>When you load, you will not have a 12 hour precip frame for F000, but
>>will have data plotted for frames 3, 5 and 9 (12, 24 and 48 hours as you
>>mention below with gdplot). You can select the time widget to start with
>>F012
>>instead of F000 (that over rides the GDATTIM in the restore file).
>>
>>Since you don't mention seeing any data for any frames, I guess I should
>ask
>>you
>>to either provide me with the entry in the prcp directory you created,
>>or ask you to try using the restore file that already exists.
>>
>>
>>Steve Chiswell
>>Unidata User SUpport
>>
>>
>>
>>>From: Stephen Sinnis <address@hidden>
>>>Organization: UCAR/Unidata
>>>Keywords: 200102011635.f11GZwX13624
>>
>>>Good day.
>>>
>>>I am having a problem displaying the precipitation of a GRID using NMAP2,
>>>(GEMPAK6a HP-UX 10.20).
>>>
>>>I created entries in $GEMTBL/config/datatype.tbl, $GEMTBL/mod_res.tbl and
>>>$NMAP_RESTORE/prcp/ for NMAP2, and can request the loading of the precip,
>>>but nothing appears on the screen.
>>>
>>>If I use GDPLOT2 and restore the same precip NTS file from
>>>$NMAP_RESTORE/prcp/precip_12hr_mm, I get images for 12, 24 and 48.
>>>
>>>Any suggestions would be appreciated.
>>>
>>>Stephen Sinnis - The Weather Network
>>>
>>>DETAILS:
>>>
>>>I get a Canadian Regional (short-term F000-F048-003) GEM grib file, (I
>>>included the gdinfo at the end of this e-mail). I use dcgrib2, with the
>>>wmogrib2 file that has all 255 components active. The parameter 61 (Total
>>>Precipitation) is available for each of the 3hr grid sets i.e. P00M, P03M,
>>>P06M,...,P48M, and is defined by CMS to contain the total accumulated
>>>precipitation at each successive grid. That is the value for P48M will
>>>always be greater than or equal to any other PXXM in the file.
>>>
>>>(GDINFO FALL ALL)
>>>
>>>
>>> GRID NAVIGATION:
>>> PROJECTION: CED
>>> GRID SIZE: 410 104
>>> LL CORNER: 40.00 220.02
>>> UR CORNER: 62.66 310.00
>>>
>>> GRID ANALYSIS BLOCK:
>>> UNKNOWN ANALYSIS TYPE
>>>
>>> Number of grids in file: 264
>>>
>>> Maximum number of grids in file: 5000
>>>
>>> NUM TIME1 TIME2 LEVL1 LEVL2 VCORD PARM
>>> 1 010201/0000F000 10000 ELVL TMPK
>>>
>>> 2 010201/0000F000 10000 ELVL DWPK
>>>
>>> 3 010201/0000F000 10000 ELVL UREL
>>>
>>> 4 010201/0000F000 10000 ELVL VREL
>>>
>>> 5 010201/0000F000 10000 ELVL WXTR
>>>
>>> 6 010201/0000F000 850 PRES UREL
>>>
>>> 7 010201/0000F000 850 PRES VREL
>>>
>>> 8 010201/0000F000 700 PRES UREL
>>>
>>> 9 010201/0000F000 700 PRES VREL
>>>
>>> 10 010201/0000F000 500 PRES UREL
>>>
>>> 11 010201/0000F000 500 PRES VREL
>>>
>>> 12 010201/0000F000 0 NONE PMSL
>>>
>>> 13 010201/0000F000 0 NONE PXXM
>>>
>>> 14 010201/0000F000 0 NONE C00M
>>>
>>> 15 010201/0000F000 0 NONE CLD
>>>
>>> 16 010201/0000F000 0 NONE LFT4
>>>
>>> 17 010201/0000F003 10000 ELVL TMPK
>>>
>>> 18 010201/0000F003 10000 ELVL DWPK
>>>
>>> 19 010201/0000F003 10000 ELVL UREL
>>>
>>> 20 010201/0000F003 10000 ELVL VREL
>>>
>>> 21 010201/0000F003 10000 ELVL WXTR
>>>
>>> 22 010201/0000F003 850 PRES UREL
>>>
>>> 23 010201/0000F003 850 PRES VREL
>>>
>>> 24 010201/0000F003 700 PRES UREL
>>>
>>> 25 010201/0000F003 700 PRES VREL
>>>
>>> 26 010201/0000F003 500 PRES UREL
>>>
>>> 27 010201/0000F003 500 PRES VREL
>>>
>>> 28 010201/0000F003 0 NONE PMSL
>>>
>>> 29 010201/0000F003 0 NONE P03M
>>>
>>> 30 010201/0000F003 0 NONE C03M
>>>
>>> 31 010201/0000F003 0 NONE CLD
>>>
>>> 32 010201/0000F006 10000 ELVL TMPK
>>>
>>> 33 010201/0000F006 10000 ELVL DWPK
>>>
>> 34 010201/0000F006 10000 ELVL UREL
>>>
>>> 35 010201/0000F006 10000 ELVL VREL
>>>
>>>...
>>> 234 010201/0000F045 10000 ELVL TMPK
>>>
>>> 235 010201/0000F045 10000 ELVL DWPK
>>>
>> 236 010201/0000F045 10000 ELVL UREL
>>>
>>> 237 010201/0000F045 10000 ELVL VREL
>>>
>>> 238 010201/0000F045 10000 ELVL WXTR
>>>
>>> 239 010201/0000F045 850 PRES UREL
>>>
>>> 240 010201/0000F045 850 PRES VREL
>>>
>>> 241 010201/0000F045 700 PRES UREL
>>>
>>> 242 010201/0000F045 700 PRES VREL
>>>
>>> 243 010201/0000F045 500 PRES UREL
>>>
>>> 244 010201/0000F045 500 PRES VREL
>>>
>>> 245 010201/0000F045 0 NONE PMSL
>>>
>>> 246 010201/0000F045 0 NONE P45M
>>>
>>> 247 010201/0000F045 0 NONE C45M
>>>
>>> 248 010201/0000F045 0 NONE CLD
>>>
>>> 249 010201/0000F048 10000 ELVL TMPK
>>>
>>> 250 010201/0000F048 10000 ELVL DWPK
>>>
>>> 251 010201/0000F048 10000 ELVL UREL
>>>
>>> 252 010201/0000F048 10000 ELVL VREL
>>>
>>> 253 010201/0000F048 10000 ELVL WXTR
>>>
>>> 254 010201/0000F048 850 PRES UREL
>>>
>>> 255 010201/0000F048 850 PRES VREL
>>>
>>> 256 010201/0000F048 700 PRES UREL
>>>
>>> 257 010201/0000F048 700 PRES VREL
>>>
>>> 258 010201/0000F048 500 PRES UREL
>>>
>>> 259 010201/0000F048 500 PRES VREL
>>>
>>> 260 010201/0000F048 0 NONE PMSL
>>>
>>> 261 010201/0000F048 0 NONE P48M
>>>
>>> 262 010201/0000F048 0 NONE C48M
>>>
>>> 263 010201/0000F048 0 NONE CLD
>>>
>>> 264 010201/0000F048 0 NONE LFT4
>>>
>>
>>***************************************************************************
>*
>><
>>Unidata User Support UCAR Unidata
>Program
>><
>>(303)497-8644 P.O. Box
>3000
>><
>>address@hidden Boulder, CO
>80307
>><
>>---------------------------------------------------------------------------
>-
>><
>>Unidata WWW Service http://www.unidata.ucar.edu/
>><
>>***************************************************************************
>*
>><
>>
>
>****************************************************************************
><
>Unidata User Support UCAR Unidata Program
><
>(303)497-8644 P.O. Box 3000
><
>address@hidden Boulder, CO 80307
><
>----------------------------------------------------------------------------
><
>Unidata WWW Service http://www.unidata.ucar.edu/
><
>****************************************************************************
><
>