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

20010405: 20010404: Garp can't see data

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: 20010405: 20010404: Garp can't see data
  • Date: Thu, 05 Apr 2001 09:54:29 -0600
>From: "Patrick O'Reilly" <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200104051522.f35FMoL20912

>Steve,
>
>Looks like all the files have 2 digit years.  They match the strings at the
>end of Garp_defaults.  I think I mentioned that Garp sees none of the data.
>I  have started NTL and pointed Nsharp at the model data, which worked.  I
>tried sitting on top of $GEMDATA and using the command "ntl -bash data" to
>try to force Garp to start looking at /data/gempak and /data/images.  None
>worked.  I am attaching my Gemenviron.bash file for you to see, I
>highlighted a line where a configuration directory is defined, which doesn't
>actually exist on my system.  Any other ideas?
>


Patrick,

try renaming the files to 4 digit years and using the templates for 4 digit 
years 
as provided in the distribution. The Y2K fixes for garp assume 4 digit years.
I provided a rename script for a similar problem in:
http://www.unidata.ucar.edu/glimpse/gempak/3775
 
Steve Chiswell
Unidata User Support





>Patrick
>
>
>
>>
>>Patrick,
>>
>>Looks like your $GARPHOME/config/Garp_defaults should have
>>nowrad defined as: $(RADDIR)/nowrad and not
>>$(RADDIR)/nowrad/US_2km/BREF.
>>
>>At thios point, I don't see any problem with the sat directory structure.
>You
>>probably want to clean up your definition of G8 to be:
>>G8    : "$(SATDIR)/GOES-8"
>>
>>Are your grids, surface and upperair data really under $GEMDATA/gempak?
>>The normal assumption us that these directories are under $GEMDATA.
>>
>>Can you send the output of "lr -R" from $GEMDATA? Also, you disn't
>>specifically menation what data sets weren't viewable, or all?!
>>The ls output will show is the file names compare to the templates at the
>bottom
>>of $GARPHOME/config/Garp_defaults.
>>
>>The default Garp_defaults expects 4 digit years. Looks like you have
>changed
>>that. You probably want to change this back and use 4 digit years for your
>>file names.
>>
>>Steve Chiswell
>>Unidata User Support
>>
>>
>>
>>>Hi-
>>>
>>>We recently installed GEMPAK, and I acquired a data set from COMET.  The =
>>>data set came in a certain directory structure which I am familiar with. =
>>> I edited my (attached) Garp_defaults file to match where the data is, =
>>>how it is named and the directory structure (I thought).  Here is what I =
>>>have set up for data directory structure:
>>>
>>>$GEMDATA/images/radar/nowrad/US_2km/BREF/*
>>>$GEMDATA/images/sat/GOES-8/4km/(vis and ir)/*
>>>$GEMDATA/images/sat/GOES-8/8km/wv/*
>>>$GEMDATA/gempak/grids/*
>>>$GEMDATA/gempak/surface/*
>>>$GEMDATA/gempak/upperair/*
>>>
>>>My Gemenviron file has:
>>>
>>>Top level directory:
>>>
>>>export NAWIPS=3D"/home/gempak/GEMPAK5.6"
>>>
>>>export GARPHOME=3D"$NAWIPS/comet/garp"
>>>
>>>export GARP_PATH=3D"$GARPHOME/config"
>>>
>>>
>>>
>>># GEMPAK directory:
>>>
>>>#
>>>
>>>export GEMPAK=3D"$NAWIPS/gempak"
>>>
>>>export GEMPAKHOME=3D"$NAWIPS/gempak"
>>>
>>>#
>>>
>>># CONFIGURATION directory
>>>
>>>export CONFIGDIR=3D"$NAWIPS/config"
>>>
>>>and my Garp_defaults file sits in $GARPHOME/config
>>>
>>>Can you see the problem or do you need more information?
>>>
>>>Patrick
>>>
>>>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>Patrick O'Reilly   =20
>>>Meteorologist/Support Scientist   =20
>>>The STORM Project
>>>University of Northern Iowa
>>>voice: (319) 273-3789
>>>e-mail: address@hidden
>>>
>
>