[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GEMPAK #CYW-235722]: gdcross question

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Subject: [GEMPAK #CYW-235722]: gdcross question
Date: Tue, 20 Nov 2012 14:06:42 -0700
Whoops, the grep command to run in ~ldm/etc/ is "grep NAM212 *"

> Sure, no problem.
> 
> The contents of any grid file are determined by a line in the LDM config file 
> "pqact.conf" (or similar), located in the LDM user's ~/etc/ directory.
> 
> Each pattern action matches a regular expression in the product header, or a 
> file name, and send the message (in this case a grib2 file) to the "dcgrib2" 
> decoder, which decodes from grib2 format to GEMPAK grid format.  The result 
> are the grid files used in GDFILE, such as "2012112012_nam212.gem"
> 
> So, the content of the nam212 GEMPAK grid file is determined by what product 
> feed is being requested (such as CONDUIT, NGRID or HDS).
> 
> I'm guessing that the pattern action for the nam212 on your end is different 
> than what we have here, based on the number of grids in the nam212 file being 
> significantly less than what I see on my end.
> 
> In ~ldm/etc/, run the command "grep NAM212" to list files which contain the 
> text "NAM212" - then view that file with "vi" or "less" and search for the 
> NAM212 entry, copy and paste it back to me so I can see what is different.
> 
> Michael
> 
> 
> > You've lost me on this one, Michael. I am not familiar with the pattern 
> > action (and frankly not familiar with our LDM feed in general). Can you 
> > walk me through this one?
> >
> > --
> > Darren R. Clabo
> > South Dakota State Fire Meteorologist
> > O: (605) 394-1996  M: (605) 381-9253
> > address@hidden
> > http://www.ias.sdsmt.edu/clabo/index.htm
> >
> >
> > -----Original Message-----
> > From: Unidata GEMPAK Support [mailto:address@hidden]
> > Sent: Tuesday, November 20, 2012 12:34 PM
> > To: Clabo, Darren R.
> > Cc: address@hidden
> > Subject: [GEMPAK #CYW-235722]: gdcross question
> >
> > Well, I'm not sure why the elevation isn't showing up for F00 since the 
> > grid exists, but perhaps you can plot elevation as point values in GDPLOT2 
> > to check that coverage is complete for the US.
> >
> > That said, the number of grids in your nam212 file is significantly lower 
> > than in the ones we decode to at Unidata, about 20% of what I see in our 
> > grid files.
> >
> > What does your pattern action look like for the nam212?  Our is pulling 
> > both the HDS and CONDUIT feeds:
> >
> > # NAM #212 40km grid CONUS
> > HDS|CONDUIT     ((/mNAM|/mNMM).*#212|prod/nam.*awip3d)
> > PIPE    dcgrib2 -d data/gempak/logs/dcgrib2_NAM212.log
> > -e GEMTBL=/home/gempak/NAWIPS/gempak/tables
> >
> >
> > The GDINFO grid count for the 212:
> >
> > GRID FILE: /data/ldm/gempak/model/nam/2012112012_nam212.gem
> >
> > GRID NAVIGATION:
> > PROJECTION:          LCC
> > ANGLES:                25.0   -95.0    25.0
> > GRID SIZE:          185 129
> > LL CORNER:              12.19   -133.46
> > UR CORNER:              57.29    -49.39
> >
> > Number of grids in file: 18975
> >
> >
> >
> > -Michael
> >
> >
> > > Here is my output for gdinfo. It appears that only the f00 forecast hour 
> > > has a hght parameter at the surface. None of the rest of the forecast 
> > > hours had a glevel=0 at gvcord=none. Interestingly enough, I was looking 
> > > at the f00 run for the cross section images I just sent to you.
> > >
> > > GEMPAK-GDINFO>l
> > > GDFILE   = /squall1/gempak-data/model/nam/2012111212_nam212.gem
> > > LSTALL   = YES
> > > OUTPUT   =
> > > GDATTIM  = all
> > > GLEVEL   = 0
> > > GVCORD   = none
> > > GFUNC    = hght
> > > GEMPAK-GDINFO>r
> > >
> > > GRID FILE: /squall1/gempak-data/model/nam/2012111212_nam212.gem
> > >
> > > GRID NAVIGATION:
> > > PROJECTION:          LCC
> > > ANGLES:                25.0   -95.0    25.0
> > > GRID SIZE:          185 129
> > > LL CORNER:              12.19   -133.46
> > > UR CORNER:              57.29    -49.39
> > >
> > > GRID ANALYSIS BLOCK:
> > > UNKNOWN ANALYSIS TYPE
> > >
> > > Number of grids in file:  3517
> > >
> > > Maximum number of grids in file:  24000
> > >
> > > NUM       TIME1              TIME2           LEVL1 LEVL2  VCORD PARM
> > > 170     121112/1200F000                          0         NONE HGHT
> > >
> > > --
> > > Darren R. Clabo
> > > South Dakota State Fire Meteorologist
> > > O: (605) 394-1996  M: (605) 381-9253
> > > address@hidden
> > > http://www.ias.sdsmt.edu/clabo/index.htm
> > >
> > >
> > > -----Original Message-----
> > > From: Unidata GEMPAK Support [mailto:address@hidden]
> > > Sent: Tuesday, November 20, 2012 11:19 AM
> > > To: Clabo, Darren R.
> > > Cc: address@hidden
> > > Subject: [GEMPAK #CYW-235722]: gdcross question
> > >
> > > Ok, I believe I know what the issue is.
> > >
> > > GDCROSS uses the surface elevation grid contained in GDFILE.  For the 
> > > nam212, using GDINFO, I see the following:
> > >
> > >
> > > GEMPAK-GDINFO>l
> > > GDFILE   = $MODEL/nam/2012112012_nam212.gem
> > > LSTALL   = YES
> > > OUTPUT   = T
> > > GDATTIM  = all
> > > GLEVEL   = 0
> > > GVCORD   = none
> > > GFUNC    = hght
> > > GEMPAK-GDINFO>r
> > >
> > > NUM       TIME1              TIME2           LEVL1 LEVL2  VCORD PARM
> > > 565     121120/1200F000                          0         NONE HGHT
> > > 1278     121120/1200F003                          0         NONE HGHT
> > > 1933     121120/1200F006                          0         NONE HGHT
> > > 2567     121120/1200F009                          0         NONE HGHT
> > > 3243     121120/1200F012                          0         NONE HGHT
> > > 3862     121120/1200F015                          0         NONE HGHT
> > > 4490     121120/1200F018                          0         NONE HGHT
> > > 5136     121120/1200F021                          0         NONE HGHT
> > > 5821     121120/1200F024                          0         NONE HGHT
> > > 6498     121120/1200F027                          0         NONE HGHT
> > > 7153     121120/1200F030                          0         NONE HGHT
> > > 7791     121120/1200F033                          0         NONE HGHT
> > > 8411     121120/1200F036                          0         NONE HGHT
> > > 9084     121120/1200F039                          0         NONE HGHT
> > > 9717     121120/1200F042                          0         NONE HGHT
> > > 10425     121120/1200F045                          0         NONE HGHT
> > > 11048     121120/1200F048                          0         NONE HGHT
> > > 11682     121120/1200F051                          0         NONE HGHT
> > > 12366     121120/1200F054                          0         NONE HGHT
> > > 13008     121120/1200F057                          0         NONE HGHT
> > > 13680     121120/1200F060                          0         NONE HGHT
> > > 14337     121120/1200F063                          0         NONE HGHT
> > > 14984     121120/1200F066                          0         NONE HGHT
> > > 15647     121120/1200F069                          0         NONE HGHT
> > > 16318     121120/1200F072                          0         NONE HGHT
> > > 16934     121120/1200F075                          0         NONE HGHT
> > > 17589     121120/1200F078                          0         NONE HGHT
> > > 18226     121120/1200F081                          0         NONE HGHT
> > > 18889     121120/1200F084                          0         NONE HGHT
> > >
> > >
> > > Can you check that these grids exist in the file you're using for GDFILE? 
> > >  My guess is that they are not there.  If they are, something else is 
> > > amiss.
> > >
> > > Michael
> > >
> > >
> > > > I just ran that same script for LAX to DEN. Still no surface. See
> > > > attached ago_test.gif-
> > > >
> > > > Additionally, when I run gdprof on the same nam212 file, it is plotting 
> > > > data down to 1000mb regardless of station surface elevation. See 
> > > > attached DNR soundings.
> > > >
> > > > --
> > > > Darren R. Clabo
> > > > South Dakota State Fire Meteorologist
> > > > O: (605) 394-1996  M: (605) 381-9253 address@hidden
> > > > http://www.ias.sdsmt.edu/clabo/index.htm
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Unidata GEMPAK Support
> > > > [mailto:address@hidden]
> > > > Sent: Tuesday, November 20, 2012 10:41 AM
> > > > To: Clabo, Darren R.
> > > > Cc: address@hidden
> > > > Subject: [GEMPAK #CYW-235722]: gdcross question
> > > >
> > > > Ah, I see, thanks.
> > > >
> > > > Using your GDCROSS input I am seeing elevation between CWPL (391 m) and 
> > > > CYMO (9 m) - see attached.
> > > >
> > > > This being a cross-section across Ontario, there's not much elevation 
> > > > to show.  The filled contours are shown below the surface because of 
> > > > the cross-section interpolation.  If I expand CXSTNS out to LAX>BWI, 
> > > > there are grid points below the surface level which are not 
> > > > interpolated to, though there is some overlap (second attachment).
> > > >
> > > > Are you using a different CXSTNS definition which does not show the 
> > > > surface?
> > > >
> > > > -Michael
> > > >
> > > > > Michael-
> > > > > I am simply using a nam212 gempak file within gdcross to plot
> > > > > potential vorticity and theta. Parameter list is (note gvcord)
> > > > >
> > > > > CXSTNS   = CWPL>CYMO
> > > > > GDATTIM  = f00
> > > > > GVCORD   = pres
> > > > > GFUNC    = pvor(thta,wnd)
> > > > > GVECT    =
> > > > > GDFILE   = /squall1/gempak-data/model/nam/2012111212_nam212.gem
> > > > > WIND     =
> > > > > REFVEC   = 10
> > > > > PTYPE    = log
> > > > > YAXIS    =
> > > > > IJSKIP   = 0
> > > > > CINT     =
> > > > > SCALE    = 6
> > > > > LINE     = 32/1/3
> > > > > BORDER   = 1
> > > > > TITLE    = 1/1
> > > > > CLEAR    = yes
> > > > > DEVICE   = gif|ago.gif|1200;900
> > > > > TEXT     = 1
> > > > > PANEL    = 0
> > > > > CONTUR   = 3
> > > > > FINT     = 1
> > > > > FLINE    = 13-30
> > > > > CTYPE    = f
> > > > >
> > > > > Any other thoughts?
> > > > >
> > > > >
> > > > > --
> > > > > Darren R. Clabo
> > > > > South Dakota State Fire Meteorologist
> > > > > O: (605) 394-1996  M: (605) 381-9253 address@hidden
> > > > > http://www.ias.sdsmt.edu/clabo/index.htm
> > > > >
> > > > > -----Original Message-----
> > > > > From: Unidata GEMPAK Support
> > > > > [mailto:address@hidden]
> > > > > Sent: Tuesday, November 20, 2012 8:37 AM
> > > > > To: Clabo, Darren R.
> > > > > Cc: address@hidden
> > > > > Subject: [GEMPAK #CYW-235722]: gdcross question
> > > > >
> > > > > I can confirm that the GDCROSS code is written to only draw surface 
> > > > > elevation when GVCORD is PRES.  I'm trying to make it work for HGHT 
> > > > > and THTA but so far it's not an easy task.  Not the news you wanted 
> > > > > to hear, sorry.
> > > > >
> > > > > Michael
> > > > >
> > > > > > Hi Darren,
> > > > > >
> > > > > > Without seeing the GDCROSS input I'm making a guess about how you 
> > > > > > went about this.  Did you run GDVINT to interpolate to theta levels 
> > > > > > and then run this new grid file through GDCROSS?
> > > > > >
> > > > > > I see what you describe when I plot a linear cross-section of 
> > > > > > temperatures by the HGHT coordinate, though there are only 6 HGHT 
> > > > > > levels for TMPK in the GFS, so the scope is limited, but it does 
> > > > > > not show a surface elevation cross-section at the bottom, like you 
> > > > > > say.
> > > > > >
> > > > > > I'm guessing that surface elevation is only designed to show for 
> > > > > > GVCORD=PRES.  I'm looking at the source code and will see if I can 
> > > > > > get it to work with height.
> > > > > >
> > > > > > -Michael
> > > > > >
> > > > > >
> > > > > >
> > > > > > > Good day-
> > > > > > > I am working on putting together an isentropic analysis in 
> > > > > > > GDCROSS. However, when I am plotting a cross section from across 
> > > > > > > the CONUS, all of the stations are showing data down to 1000 mb. 
> > > > > > > Considering the elevation of the Intermountain West, I was hoping 
> > > > > > > I could get a plot that resembles what is found on the GEMPAK 
> > > > > > > tutorial page 
> > > > > > > (http://www.unidata.ucar.edu/software/gempak/tutorial/vertical_plotting.html#12.2)
> > > > > > >  where the surface elevation is easily seen.
> > > > > > >
> > > > > > > Any thoughts on what I can do?
> > > > > > >
> > > > > > > --
> > > > > > > Darren R. Clabo
> > > > > > > South Dakota State Fire Meteorologist
> > > > > > > O: (605) 394-1996  M: (605) 381-9253 address@hidden
> > > > > > > http://www.ias.sdsmt.edu/clabo/index.htm
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > Ticket Details
> > > > > ===================
> > > > > Ticket ID: CYW-235722
> > > > > Department: Support GEMPAK
> > > > > Priority: Normal
> > > > > Status: Open
> > > > >
> > > > >
> > > >
> > > >
> > > > Ticket Details
> > > > ===================
> > > > Ticket ID: CYW-235722
> > > > Department: Support GEMPAK
> > > > Priority: Normal
> > > > Status: Open
> > > >
> > >
> > > Ticket Details
> > > ===================
> > > Ticket ID: CYW-235722
> > > Department: Support GEMPAK
> > > Priority: Normal
> > > Status: Open
> > >
> > >
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: CYW-235722
> > Department: Support GEMPAK
> > Priority: Normal
> > Status: Open
> >
> >


Ticket Details
===================
Ticket ID: CYW-235722
Department: Support GEMPAK
Priority: Normal
Status: Open
Prev by Date: [GEMPAK #CYW-235722]: gdcross question
Next by Date: [GEMPAK #CYW-235722]: gdcross question
Previous by thread: [GEMPAK #CYW-235722]: gdcross question
Next by thread: [GEMPAK #CYW-235722]: gdcross question
Index(es):
- Date
- Thread