20000203: Scripts, and NIDS

Mark,

I still run nsat_ links because there is no way to file the AREA files from
the LDM to obtain the necessary information to identify the time, date
etc other than AREAxxxx, so the areaInfo program has to be run.

Steve Chiswell
Unidata User Support



>From: Mark Tucker <address@hidden>
>Organization: .
>Keywords: 200002051349.GAA21377

>On Fri, 4 Feb 2000, Unidata Support wrote:
>
>I've made the changes for NIDS and other radar data you recommended.  What
>should I be doing about the nsat_links script?
>
>> >From: Mark Tucker <address@hidden>
>> >Organization: .
>> >Keywords: 200002041530.IAA11267
>> 
>> >On Thu, 3 Feb 2000, Unidata Support wrote:
>> >
>> >> However, I do see that you downloaded the pl15 linux binary distribution
>> >> on Jan 26. You should update the dcgrib decoder to pl15 (either binary di
> str
>> > ibution
>> >> or local build) since it will allow you to use the UK Met grids as
>> >> well.
>> > 
>> >That was the problem.  I had the old decoders still in use instead of the
>> >the ones in pl15.  Many things were fixed with that.  I cannot find the
>> >nsat_links, nowrad_links, and nids_links scripts in the new distribution
>> >of gempak.  Are these available somewhere else?
>> >
>> >Also, now that our gridded data filenames and locations match (closely)
>> >the distributed Garp_defaults I can now get at the model data.  For some
>> >reason the nids are still not showing up in the "Image Products" dialog.
>> >Is this because the nids_links script has not been run yet?  The
>> >environment and directory structure are correct.
>> >
>> >Thanks.
>> >
>> >Mark Tucker
>> >Information Technology
>> >Lyndon State College
>> >address@hidden
>> >
>> >
>> 
>> Mark,
>> 
>> In the Garp_defaults in the distribution, I have RADDIR defined
>> as $GEMDATA/nexrad. Now that Tom has an ADDE server that can
>> read the nids data from the same directory structure, I have just been
>> filing the data into the $GEMDATA/nexrad tree rather than using the nids
>> and nowrad link scripts, eg:
>> WSI     ^NEX/(.*)/(.*)/([1-2][0-9])([0-9][0-9])([0-1][0-9])([0-3][0-9])([0-2
> ][0-9])([0-6][0-9])
>>         FILE    data/gempak/nexrad/NIDS/\1/\2/\1-\2_\3\4\5\6_\7\8
>> WSI     ^(NOW)/USRAD/([1-2][0-9])([0-9][0-9])([0-1][0-9])([0-3][0-9])([0-2][
> 0-9])([0-6][0-9])
>>         FILE    data/gempak/nexrad/USRAD/8km/\1/\1_\2\3\4\5_\6\7
>> WSI     ^(NOW)/MASTER/([1-2][0-9])([0-9][0-9])([0-1][0-9])([0-3][0-9])([0-2]
> [0-9])([0-6][0-9])
>>         FILE    data/gempak/nexrad/USRAD/2km/\1/\1_\2\3\4\5_\6\7
>> 
>> I use the prune_nexrad.csh script to scour the nids and nowrad files
>> rather than maintaining the links, but I posted the all scripts in the 
>> ~gbuddy/nawips-5.4/scripts directory..
>> 
>> Steve Chiswell
>> ****************************************************************************
>> Unidata User Support                                    UCAR Unidata Program
>> (303)497-8644                                                  P.O. Box 3000
>> address@hidden                                   Boulder, CO 80307
>> ----------------------------------------------------------------------------
>> Unidata WWW Service                        http://www.unidata.ucar.edu/     
>> ****************************************************************************
>> 
>
>Mark Tucker
>Information Technology
>Lyndon State College
>address@hidden
>
>