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.
> Steve > > > I presume you are telling me to test these functions by changing one of > my exec's with > the information that you have provided, etc. Actually, I was saying to run the GDINFO program unrelated to your script. But certainly as you say, timing is a critical path as well. Steve Chiswell Unidata User Support > > I think part of the problem is in the timing of these exec's showhow > there is some iterference with too many grid files or grid files from > various sources such as the NAM and or grid 212 or 215 etc. > > example..... > > # Panel 1 500 mb heights/vort > > DEVICE = ps|${FILENAME} > GDFILE = $gridfile > echo GDFILE > GDATTIM = f06 > DATTIM = > STNPLT = > PANEL = 1/1//2 > TEXT = .7/21//hw > CONTUR = 1 > MAP = 1 > CLEAR = no > CLRBAR = 1 > GAREA = 20;-126;50;-60 > PROJ = uslcc > > > > > These instructions must be > > Unidata GEMPAK Support wrote:s > > >Harvey, > > > >We do not have the ability here to accept requests for hired support. > >You may find that the gembed email list can be a resource to find if > >anyone in the community would be looking for temporary employment. > > > >My instructions regarding running GDINFO is to set the parameters: > > LSTALL = yes > > OUTPUT = t > > GDATTIM = all > > GLEVEL = all > > GVCORD = all > > GFUNC = all > > > >The after defining your GDFILE, run the program, and see all the grids that > >are within > >your grid file to verify if the data at the level you are expecting is > >present. > > > >Steve Chiswell > >Unidata User Support > > > > > > > > > >>Dear Steve or Support > >> > >>I have been unable to determine what the problem is with your help. Is > >>it possible to hire someone at your office for several hours or a day to > >>analyze our scripts and cron? > >> > >>Basically, I believe that our scripts work, but there may be some > >>conflicts, between the time the cron > >>starts the programs and the amount of data that we are receiving from > >>Noaaport, i.e. the different NAM grids etc. > >> > >>I am not completely sure what you mean when you say that I can run > >>GDINFO with GDATTIM, GVCORS and GFUNC set to "all" to see what levels, > >>times, parameters are available. I recognize these names and see them > >>in the scripts, but am not sure how you mean to test the system, etc. > >> > >>I would make the time to talk to someone at your office to try to debug > >>the system with your help. > >>Harvey > >> > >> > >> > >> > > > > > >Ticket Details > >=================== > >Ticket ID: MNS-455454 > >Department: Support GEMPAK > >Priority: Critical > >Status: Closed > > > > > > > Thanks Stev > > Ticket Details =================== Ticket ID: MNS-455454 Department: Support GEMPAK Priority: Critical Status: Closed