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

20000327: case study in ntl

Welker,

The model fields and macros are displayed based on the model key names.
You have model keys like: eta,avn,meso etc.

These keys are search under the fdf directory defined in the Garp_defaults 
file as:

fdfdir          : $(GARPHOME)/fdf

Under the fdf, you will find the scalar and vector subdirectories which
contain the fields which are provided for the various models.
The distributed Garp_defaults defines model keys such as eta211, eta212 to
match on those strings in the grid file directory. These are also searched
for in the fdf directory and if found, will be used as the fields available
for the model pulldowns. If the key name is not found, then the very basic
set of fields under "default" will be used.

If you use different model keys in your Garp_defaults, then you either
need to create directories in the fdf directories to match your keys (or
symbolic links), or define your own fdfdir directory which provides the
fdfs that you want for your case study under the directory names which
match your model keys.

Let me know if you need more information.

Steve Chiswell
Unidata User Support

On Mon, 27 Mar 2000, Walker Ashley wrote:

> Hey Chiz...
> 
> Walker here at UNL trying to figure out this case study data problem with
> ntl. I have put a comet case study on two cds: one with weather and images,
> the other with model and obs. Here is the cd structure:
> _________________________________
> 
> cdrom1 (cd name /gempakdata/)
> 
> - /grids/...
> - /surface/...
> - /upperair/...
> 
> cdrom2 (cd name /weather/)
> 
> - /images
>       - /radar/...
>       - /sat/...
> - /weather
> _________________________________
> 
> Ok, not so bad. Clint and I created a case.env so we could source the case
> study data on the cdroms when we loaded up ntl. Here is the case.env:
> _________________________________
> setenv GEMDATA /cdrom/cdrom0
> setenv HDS ${GEMDATA}/grids
> setenv SATDIR ${GEMDATA}/images/sat
> setenv TEXT_DATA ${GEMDATA}/weather
> setenv RAD ${GEMDATA}/images/radar
> setenv GARP_PATH $HOME/mygarp
> _________________________________
> mygarp contains my version of garp_defaults (see attatch.)
> _________________________________
> 
> So I type in source case.env, and then load up ntl. Everything looks great.
> I get surface and upper air data along with some model output. This is were
> the problem begins. When I push the plan projection model I get the models
> that I specified in mygarp which includes the garp_defaults setup that I
> modified for the case. All the macros and fdfs load up for the AVN and MESO
> data, but only a handfull of choices (no macros available) load up for the
> NGM, RUC, and ETA. In other words, I can only get general scalar values
> such as temps and moisture values. I then went back through the
> garp_defaults to see why it might not be calling the fdfs and macros for
> the NGM, RUC, and ETA models. I simply cannot find anything wrong. 
> 
> I will attatch my version of the garp_defaults that I use for the case
> data. I changed the values that you suggested to Clint on the phone. 
> 
> Chiz, I have no clue why the macros load up for one model and not for the
> other. If you can figure it out let me know.
> 
> Thanks
> Walker