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

20000328: date label on model plan view

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: 20000328: date label on model plan view
  • Date: Wed, 29 Mar 2000 09:47:53 -0700
>From: Anthony Rockwood - MSCD Meteorology <address@hidden>
>Organization: .
>Keywords: 200003291521.IAA16183

>Chiz,
>
>Now that I think about it, this problem may have started around 29 Feb.
>Anyway, this is where I get into real trouble.  Upgrades have always led
>to days worth of frustrating trial and error for me since I really don't
>know what I'm doing.  More often than not, I do more harm than good.  I
>usually end up as the project manager - trying to get people who have the
>ability to actually do the work.  It's difficult to tackle a job like this
>in the middle of a semester, so maybe I should hold off till this summer ?
>
>If you could outline what would need to be done, it would help me plan the
>best strategy.
>
>Thanks,
>
>Tony
>
> ****************************************************************************
>   Anthony A. Rockwood              Metropolitan State College of Denver    
>   Meteorology Program              Dept.of Earth and Atmospheric Sciences 
>   303.556.8399                     P.O. Box 173362, Campus Box 22
>   address@hidden                Denver, CO  80217-3362                  
>   http://www.mscd.edu/~eas         http://clem.mscd.edu/~rockwooa
> ****************************************************************************
>
>

Tony,

In this case, we can just try upgrading the executable (the underlying tables
for garp remain the same...so it shouldn't be as painful as upgrading last 
time when you went from Garp 2.02 to Garp 2.1.

My suggestion would be:

1) move the current Garp execuatble to a backup

cd $GEMEXE
mv garp garp.bak

2) FTP the current version of the Garp executable from 
   ~gbuddy/nawips-5.4/binary/solaris_X86/garp into your $GEMEXE directory

3) Set the executable mode bits of the file you just downloaded

chmod a+x garp

Then give it a try.


If this doesn't quickly solve your problem, then I should probably get a login
and see why I can't reproduce the problem here.

Steve Chiswell