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

20041122: Garp bug -- model vertical cross sections foul up subsequent data

David,

You are correct in that there is a bug in the plan view plotting routines
of Garp that was introduced into Garp when the underlying gemlib routines 
were modified to support the IJSKIP usage. I will update these routines
in the 5.7.4 release I am getting ready to pack up.

Steve Chiswell
Unidata User Support




>From: David Ovens <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200411230012.iAN0CO7j009694

>Hello,
>
>I have found a bug in Garp that appears once a model vertical cross
>section is plotted.
>
>I just created some GEMPAK files using ETA 104 grids and 1-degree
>global GFS grids (both of which can be found in the CONDUIT data feed:
> ETA 104 : 
> files are SL.us008001/ST.opnl/MT.eta_CY.12/RD.20041122/PT.grid_DF.gr1/*grbgrd
>  
> GFS :
> files are SL.us008001/ST.opnl/MT.avn_CY.12/RD.20041122/PT.grid_DF.gr1/*gr.one
> deg
>)
>using dcgrib2 as found in the GEMPAK 5.7.3 Unidata Linux binary
>package. 
>
>When I run garp (again 5.7.3 Unidata binary version), at first I can
>plot model plan views of wind bards at 1000 mb with no problem.  Then,
>I do a model vertical cross section from vbg>nyc plotting wind barbs.
>These look fine.  Then, I go back to model plan view to replot my
>first plot and all hours, all dates, and all levels now display the
>exact same _erroneous_ wind barbs.
>
>This happens in 5.6.L and 5.7.2 versions as well, again with both of
>these ETA 104 and GFS grids.
>
>David
>-- 
>David Ovens             e-mail: address@hidden
>Research Meteorologist    phone: (206) 685-8108
>Dept of Atm. Sciences      plan: Real-time MM5 forecasting for the
>Box 351640                        Pacific Northwest
>University of Washington          http://www.atmos.washington.edu/mm5rt
>Seattle, WA  98195               Weather Graphics and Loops
>                                  http://www.atmos.washington.edu/~ovens/loops
>
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly 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.