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.
Hi Paul, I am currently at home shoveling the 24+" of snow that has fallen overnight and still coming down hard. I will try to look into all that you include below from time to time today. Quick question: - how many graphic and image levels are available in the McIDAS "session" (interactive or one created by a script by 'mcenv') when these images were were created? This can be listed using the UCU utility: UCU PEEK 500 <- graphics levels UCU PEEK 600 <- image (aka gray) levels The reason I ask is that the display of an enhancement can look very strange if there are a lot more enhancement levels defined than there are image levels. I don't think that this is causing your problems, but I want to be sure. Also, I don't understand this comment (at the end of your note): > And then, the values are random on the > side so they are not displaying the accurate number. I don't see "random" numbers. Can you explain what you mean? re: > If the non-use of a stretch table is best, why do the labels plot out as > they do and I cannot find the zero isodop and highlight it? If the mapping from original image value to velocity is fixed, then finding/highlighting the zero isodop would be simple/straightforward. Since the mapping of original image values to display levels varies from image to image, this will be difficult (and I have not spent enough time on the problem to be able to give you an ABC of what to do). re: > Also, why is > there such a large color interval between 0 and -1 kts? ??? Where? I guess I am missing something. By the way, I sent a note to the MUG folks at SSEC requesting a conference call to discuss the issue of dynamic mapping of image values and its effect on displays. We will be "getting together" as soon as they feel that they have reviewed the problem enough to comment. One possible approach is to have the server map original image values to fixed data ranges, but I think that this would result in loss of information. Cheers, Tom > The output > I think every time I understand what is happening, I run some commands and > get an entirely different result. So I am going to break this down in > small pieces and see if I can capture the process. > > http://climate.cod.edu/data/nexrad/TLX/N0S/TLX.N0S.20120203.1500.gif > > Is an image I just generated. This was done with only an EU table that I > created. I wanted the grey to be the zero isodop but it evidently maps to > a varying scale based on the image that comes in. > > When I use SU with the following table > BREAKPOINTS STORED IN TABLE : NEWVEL.ST > INPUT OUTPUT > ----- ------ > -70 1 > -70 15 > -69.9999 16 > -64 31 > -63.9999 32 > -50 47 > -49.9999 48 > -36 63 > -35.9999 64 > -26 79 > -25.9999 80 > -20 95 > -19.9999 96 > -10 111 > -9.9999 112 > -.0001 127 > 0 128 > 9.9999 143 > 10 144 > 19.9999 159 > 20 160 > 25.9999 175 > 26 176 > 35.9999 191 > 36 192 > 49.9999 207 > 50 208 > 63.9999 223 > 64 224 > 69.9999 239 > 70 240 > 70 255 > CALIBRATION TYPE : NIDS > CALIBRATION UNITS : VEL > BAND NUMBER : -1 > INTERPOLATION TYPE: LIN > > I get the picture at > http://climate.cod.edu/data/nexrad/TLX/N0S/TLX.N0S.20120203.1508.gif > > Notice I lose the RF pallete so I clearly do not know where within the > data file RF is assigned. Nor the TH data.So to have the color pallette I > am choosing match those numbers which I do not know. Now when I use > > Then I get this image > http://climate.cod.edu/data/nexrad/TLX/N0S/TLX.N0S.20120203.1526.gif > > when I use the SU table in IMGDISP command and BAR command > mcidas@climate:~/paulsbatches$ su.k TABLE PAULVEL > BREAKPOINTS STORED IN TABLE : PAULVEL.ST > INPUT OUTPUT > ----- ------ > -90 0 > -90 14 > -89.9999 15 > 89.9999 239 > 90 240 > 90 255 > CALIBRATION TYPE : NEXR > CALIBRATION UNITS : VEL > BAND NUMBER : -1 > INTERPOLATION TYPE: LIN > > mcidas@climate:~/paulsbatches$ eu.k TABLE NEWVEL > Brightness Blue Green Red > min max min max min max min max > --- --- --- --- --- --- --- --- > 0 13 0 0 0 0 0 0 > 14 47 255 190 180 70 0 0 > 48 118 75 0 255 85 0 0 > 119 127 70 200 100 200 70 200 > 128 129 200 200 200 200 200 200 > 130 136 181 70 181 70 186 100 > 137 208 0 0 0 0 85 255 > 209 235 105 0 160 255 250 255 > 236 240 0 0 255 255 255 255 > 241 255 127 127 0 0 127 127 > eu.k: Done > > So level 0-13 are supposed to be black. I just cant figure out WHY the > colors show up the way they do. And then, the values are random on the > side so they are not displaying the accurate number. > > If the non-use of a stretch table is best, why do the labels plot out as > they do and I cannot find the zero isodop and highlight it? Also, why is > there such a large color inteval between 0 and -1 kts? > > Thanks > > Paul > > > On Mon, 30 Jan 2012, Unidata McIDAS Support wrote: > > > Hi Paul, > > > > re: I want the interval to be labelled at 10DBZ, not 8. > > > > I'll take a look at BAR to see if there is a straightforward way of > > making the reflectivity levels be evenly divisible by 5 or 10. > > > > Cheers, > > > > Tom > > -- > > **************************************************************************** > > Unidata User Support UCAR Unidata Program > > (303) 497-8642 P.O. Box 3000 > > address@hidden Boulder, CO 80307 > > ---------------------------------------------------------------------------- > > Unidata HomePage http://www.unidata.ucar.edu > > **************************************************************************** > > > > > > Ticket Details > > =================== > > Ticket ID: AIT-655217 > > Department: Support McIDAS > > Priority: Normal > > Status: Closed > > > > ****************************************************************************** > * Paul L. Sirvatka | Office: (630) 942-2118 BIC3501 * > * Professor of Meteorology | COD Weather Lab: (630) 942-2590 * > * College of DuPage | Address: 425 Fawell Blvd. Glen Ellyn, IL 60137 * > ****************************************************************************** > > Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: AIT-655217 Department: Support McIDAS Priority: Normal Status: Open