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

20000725: 20000725: brightness legend on satellite pictures

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: 20000725: 20000725: brightness legend on satellite pictures
Date: Tue, 25 Jul 2000 18:55:28 -0600

Chris,

As you can tell, this is an ongoing work in progress.

I just tarred up some luts that I created this afternoon.
They are in ~gbuddy/nawips-5.4/patches/sounder_luts.tar.Z

Unpack these from $NAWIPS.

Then edit the $GEMTBL/sat/imgtyp.tbl table to be:
!
! SOUNDER Products from GINI
SOUNDER              LI            0    255     70  2**15      1 GRAY
SOUNDER              PW            0    255     70  2**16      1 GRAY
SOUNDER              SFC_SKIN      0    255     70  2**17      1 GRAY
SOUNDER              CTP           0    255     70  2**26      1 GRAY
!
! CIMMS AREA FILES
SOUNDER              CTP           0    255     75  2**26      1 ctp_upc.tbl
SOUNDER              PW            0    255     75  2**27      1 pw_upc.tbl
SOUNDER              LI            0    255     75  2**28      1 snd_li.tbl
SOUNDER              CAPE          0    255     75  2**29      1 cape_upc.tbl
SOUNDER              OZONE         0    255     75  2**30      1 ozone_upc.tbl
SOUNDER              SST           0    255     70  2**30      1 sst_upc.tbl

The CIMMS section will use the luts I just created.
The other section is for the SOUNDER products on NOAAport in GINI format (which
use a different platform number...and are on a different NOAAPORT channel than
the nwstg- so your aren't receiving them from us at this time).

Everything I'm doing here is back and forth from my twp different versions of
GEMPAK- so it takes some organizing for me to get things in sync.

After I get this all working for you...then I'll pack up things as a patch
for the compete distribution.

Thansk for the feedback.

CHiz





>From: "C. Vandersip" <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200007252342.e6PNg7T01418

>Steve,
>
>Works great...I did notice that each time I bring these products up the
>color table defaults to gray, which you mentioned would be the case. Also,
>I get warning messages about color tables for the following products:
>
>LI
>--
>GEMPAK: [IM -8]  Could not open LUT file snd_li.tbl
>
>PW
>--
>GEMPAK: [IM -8]  Could not open LUT file snd_pwin.tbl
>
>SST
>---
>GEMPAK: [IM -8]  Could not open LUT file ssmi_mpc.tbl
>
>No warnings with CAPE, CTP, and OZONE.  I see from
>$NAWIPS/gempak5.4/tables/sat/imgtyp.tbl that this is why the warnings are
>generated:
>
>! SOUNDER Products
>SOUNDER              LI            0    255     70  2**15      1 GRAY
>SOUNDER              PW            0    255     70  2**16      1 GRAY
>SOUNDER              SFC_SKIN      0    255     70  2**17      1 GRAY
>SOUNDER              CTP           0    255     70  2**26      1 GRAY
>!
>SOUNDER              CTP           0    255     75  2**26      1 GRAY
>SOUNDER              PW            0    255     75  2**27      1 snd_pwin.tbl
>SOUNDER              LI            0    255     75  2**28      1 snd_li.tbl
>SOUNDER              CAPE          0    255     75  2**29      1 GRAY
>SOUNDER              OZONE         0    255     75  2**30      1 GRAY
>SOUNDER              SST           0    255     70  2**30      1 ssmi_mpc.tbl
>
>I checked luts/ and found that these 3 tables didn't exist in that
>directory.  I looked in the ftp site and didn't find them there.  
>BTW, are the duplicates of LI, PW, and CTP in the SOUNDER section of
>imgtyp.tbl a factor?
>
>Regards,
>
>Chris
>
>On Tue, 25 Jul 2000, Unidata Support wrote:
>
>> 
>> Chris,
>> 
>> I have one more routine for you to try out.
>> In the ~gbuddy/nawips-5.4/patches directory is a copy of $GARPHOME/gempak/po
> interinfo.c.
>> You can move your current copy from pointerinfo.c to pointerinfo.c.old,
>> then download the new version to pointerinfo.c.
>> 
>> Finally, make and install Garp with:
>> cd $GARPHOME
>> make all
>> make install
>> 
>> 
>> this will enable the pointer within the image area to return the value
>> interpolated back from the Raw pixel value.
>> 
>> One thing to note- all of these products are multi-part calibrartions.
>> Eg, for PW products, pixel values 0 through 200 represent PW values from
>> 0 to 67mm. Pixel values 201-255 represent cloud top temperatures -
>> and not PW values. So, the values displayed for the pointer return
>> PW values only where those pixels exist and represent PW.
>> 
>> Feedback is appreciated!
>> 
>> Steve Chiswell
>> Unidata User Support
>> 
>> 
>> 
>> >From: "C. Vandersip" <address@hidden>
>> >Organization: UCAR/Unidata
>> >Keywords: 200007251739.e6PHdvT17642
>> 
>> >Beautiful!  Works great, Steve.  I appreciate it very much.
>> >
>> >Regards,
>> >
>> >Chris
>> >
>> >On Tue, 25 Jul 2000, C. Vandersip wrote:
>> >
>> >> Doh!
>> >> 
>> >> As I did this patching late last night, I think I forgot to do make
>> >> install in $GARPHOME.  That's probably causing this problem.  I'm redoing
>> >> it and will let you know.
>> >> 
>> >> Chris
>> >> 
>> >> 
>> >> On Tue, 25 Jul 2000, C. Vandersip wrote:
>> >> 
>> >> > Steve,
>> >> > 
>> >> > Ok, I installed the patch files, but I'm still getting the standard BRI
> T
>> >> > colorbar.  From looking at $GARPHOME/gempak/colorbardraw.f, it appears
>> >> > that 
>> >> > 
>> >> > IF ( cmcalb .eq. 'BRIT' .and. imtype .ne. 1 ) THEN
>> >> > 
>> >> > is being satisfied as true, even though it's not supposed to be for the
> se
>> >> > products (right?). Is there something else I should do? Any information
>  I
>> >> > should provide you?  
>> >> > 
>> >> > Thanks,
>> >> > 
>> >> > Chris
>> >> > 
>> >> 
>> >>    ###############################################################
>> >>    #                      Chris Vandersip                        #
>> >>    #        Computer Research Specialist/Dept. Sysadmin          #
>> >>    #  Rm. 024, Dept. of Meteorology, Florida State University    #
>> >>    #          address@hidden   (850)644-2522                     #
>> >>    ###############################################################
>> >> 
>> >> 
>> >
>> >     ###############################################################
>> >     #                      Chris Vandersip                        #
>> >     #        Computer Research Specialist/Dept. Sysadmin          #
>> >     #  Rm. 024, Dept. of Meteorology, Florida State University    #
>> >     #          address@hidden   (850)644-2522                     #
>> >     ###############################################################
>> >
>> 
>> ****************************************************************************
>> 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/     
>> ****************************************************************************
>> 
>
>        ###############################################################
>        #                      Chris Vandersip                        #
>        #        Computer Research Specialist/Dept. Sysadmin          #
>        #  Rm. 024, Dept. of Meteorology, Florida State University    #
>        #          address@hidden   (850)644-2522                     #
>        ###############################################################
>
>
>

Prev by Date: DIFAX Alternatives
Next by Date: 20000726: DATTIM when plotting NGM MOS
Previous by thread: DIFAX Alternatives
Next by thread: 20000726: DATTIM when plotting NGM MOS
Index(es):
- Date
- Thread