[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
20150616: [Staging #CCM-472749]: Re: 20150522: TDWR Level III data from NOAA NEXRAD Operational Support Facility in McX and McV (cont.)
- Subject: 20150616: [Staging #CCM-472749]: Re: 20150522: TDWR Level III data from NOAA NEXRAD Operational Support Facility in McX and McV (cont.)
- Date: Tue, 16 Jun 2015 16:51:22 -0600
Hi Jim,
re:
>Hi again, Tom -- I'm in the process of having Technical Computing
>get the McIDAS ADDE server account (mcadde) to be running M-X 2015.1.
Excellent!
re:
>Hopefully this can get done by mid-morning Wednesday (or if I'm really
>lucky by the end of the day on Tuesday).
>
>Then let's see where all of this TDWR stuff stands.
Sounds good.
re:
>Thank you for all of your help!
No worries.
Cheers,
Tom
>---------------------------------------------------------------------------
>Thanks to Tom for refreshing my (poor) memory on this...
>
>My screwup -- I totally forgot about updating where the ADDE server
>account looks for *its* McIDAS-X software. I'm sorry. I will speak
>with John about updating that account to 2015.1.
>
>Later, again.
>
>Sincerely,
>
>Jim
>-----
>On 6/16/2015 3:06 PM, Unidata User Support wrote:
>> Hi Jim, et. al,
>>
>> Jim Nelson wrote:
>>> 1.) One thing I did which I think is helping me to understand things a
>>> little better is to serve Bob's data via 3 different ADDE datasets:
>>>
>>> N1=RCI,N2=NCDCR,TYPE=IMAGE,RT=N,K=NEXR,R1=1,R2=999999,MASK=/home/rabin/tdwr
> /ncdctest/TDEN*TR*,C=B. R. TDWR reflectivity files,
>>>
>>> N1=RCI,N2=NCDCS,TYPE=IMAGE,RT=N,K=NEXR,R1=1,R2=999999,MASK=/home/rabin/tdwr
> /ncdctest/TDEN*TS*,C=B.R. TDWR ????? files,
>>>
>>> N1=RCI,N2=NCDCV,TYPE=IMAGE,RT=N,K=NEXR,R1=1,R2=999999,MASK=/home/rabin/tdwr
> /ncdctest/TDEN*TV*,C=B. R. TDWR velocity files,
>> Some comments:
>>
>> 1 - the DIRMASK= (represented by RESOLV.SRV MASK= clauses) does not account
>> for the set of files that Bob provided to me
>>
>> The set of files that were provided to me were named:
>>
>> TDWR Base Reflectivity file (TR0):
>> TDEN_SDUS00_TR0DEN_201405202229
>>
>> TDWR Base Velocity file (TV0):
>> TDEN_SDUS00_TV0DEN_201405202230
>> KBOU_SDUS55_TV0DEN_201506042350
>> TDEN_SDUS00_TV0DEN_201405202229
>>
>> If you have the same set of files, then the dataset definitions would
>> be better defined as:
>>
>> N1=RCI,N2=NCDCR,TYPE=IMAGE,RT=N,K=NEXR,R1=1,R2=999999,MASK=/home/rabin/tdwr/
> ncdctest/*TR0*,C=B. R. TDWR reflectivity files,
>>
>> N1=RCI,N2=NCDCV,TYPE=IMAGE,RT=N,K=NEXR,R1=1,R2=999999,MASK=/home/rabin/tdwr/
> ncdctest/*TV0*,C=B. R. TDWR velocity files,
>>
>> 2 - I was never told about any issue with TDWR TS0 files, and I was never
>> provided with examples to work with
>>
>> Since I have no example TS0 files, I can't comment on how the set of on
> es
>> that you have should be described.
>>
>> BUT, I can comment that my code update included modifications for
>> what is likely to be the high resolution (256 color instead of 16 color
> )
>> TDWR TS0 product (product code 186). I could verify this really
>> is the case if I am provided with one or more of the TS0 files.
>>
>> re:
>>> Before I was serving everything via a more global TDEN* dataset, and I
>>> think that was confusing the issue.
>> I agree.
>>
>> re:
>>> FYI, to look at RCI data, you must first: LOGON GOPS 9999 (Please
>>> don't share this (highly secure) pw with anybody :) )
>> OK.
>>
>> re:
>>> 2.) Given #1 above, I concur with Bob Carp at the McIDAS Help Desk.
>>> Using the 2015.1 version of M-X currently installed
>>> on rci.ssec.wisc.edu, I see reasonable data now from the files named:
>>> TDEN_SDUS00_TV0DEN_2014052022?? Neither
>>> the *TR* nor *TS* files are being served properly, however. I am
>>> seeing all 0's, just like Bob.
>> I see the same thing. This _strongly_ suggests that the NEXRAD Level
>> III/TDWR server that is being used in the remote ADDE access to RCI/NCDCR
>> on rci.ssec.wisc.edu is _not_ the server that was updated with the three
>> files (nexradir.cp, nexrutil.c and kbxnexr.dlm) that I gave Jim last
>> Tuesday while I was in Madison. The reason I say this is because the
>> "all zero"s output from IMGLISTs is exactly the behavior I saw before
>> updating the server code.
>>
>> re:
>>> 3.) Bob, you said: "I just saw the explanation for why the TR0 files
>>> weren't working..." What is this? I did not see
>>> that thread anywhere.
>> Bob C. sent us a couple of emails this morning to let us know that he
>> was checking into things while Barry is on vacation. One of his emails
>> included the comment that processing of Bob R's TV0 files looked good,
>> but processing for Bob R's TR0 file was bad.
>>
>> re:
>>> Does this mean that a fix is at hand for the
>>> TR0 files? Where do things stand with the TS0 files?
>> The fix is included in the source code files that I provided while at the
>> MUG meeting. I am willing to bet that the version of McIDAS-X that
>> is being used by the remote ADDE interface on rci.ssec.wisc.edu is still
>> SSEC v2013.1, and this was not the code that was updated by Jim last week.
>> A quick test of this would be to update the NEXRAD Level III/TDWR servers
>> with my code updates in the SSEC v2013.1 distribution on rci.ssec.wisc.edu.
>>
>> Cheers,
>>
>> Tom
>>
>>> -----
>>> On 6/16/2015 12:15 PM, McIDAS Help Desk wrote:
>>>> Sorry about that, I just saw the explanation for why the TR0 files
>>>> weren't working... should have looked back at older emails :( . That
>>>> being said, I'm using McIDAS-X 2015.1 and I'm seeing what looks like
>>>> good IMGPROBE output of the TV0 data.
>>>> *
>>>> *
>>>>> *IMGDISP TEST/VEL2.1 MAG=-2 ID=DEN*
>>>>> Beginning Image Data transfer, bytes= 309164
>>>>> IMGDISP: loaded frame 17
>>>>> IMGDISP: done
>>>>>
>>>>> Image Name ID Day Nominal Time Scan Time Band
>>>>> ---------------- --- ------- ------------ --------- ----
>>>>> TEST/VEL2 DEN 4 Jun 15155 23:50:41 MISSING 9
>>>>>
>>>>> File Nominal Image RAW
>>>>> BRIT VEL
>>>>> Lat/Lon Line/Element
>>>>> Line/Element KT
>>>>> 39:58:48 / 105:03:45 412/ 294 413/ 295 158
>>>>> 158 28
>>>>>
>>>>> IMGPROBE: Done
>>>>>
>>>>> Image Name ID Day Nominal Time Scan Time Band
>>>>> ---------------- --- ------- ------------ --------- ----
>>>>> TEST/VEL2 DEN 4 Jun 15155 23:50:41 MISSING 9
>>>>>
>>>>> File Nominal Image RAW
>>>>> BRIT VEL
>>>>> Lat/Lon Line/Element
>>>>> Line/Element KT
>>>>> 39:22:45 / 104:07:37 858/ 828 859/ 829 117
>>>>> 117 -11
>>>>>
>>>>> IMGPROBE: Done
>>>> I've tested with both of the TV0 files sent out by Bob R on 06/13.
>>>>
>>>> - Bob Carp
>>>>
>>>> On 6/16/2015 10:02 AM, McIDAS Help Desk wrote:
>>>>> Hi all -
>>>>>
>>>>> Barry is on vacation this week, so I've been looking at this issue
>>>>> this morning. Perhaps I missed something earlier, but I don't think
>>>>> that the problem is with the velocity (TV0) files, but rather with
>>>>> the reflectivity files (TR0). The TV0 files I have are working fine
>>>>> for me in McIDAS-X, McIDAS-V and the IDV.
>>>>>
>>>>> Tom, have you tried the TR0 file in Unidata McIDAS-X?
>>>>>
>>>>> When I do an IMGLIST in McIDAS-X of a TR0 file, everything lists out
>>>>> as 0:
>>>>>> *IMGLIST TEST/REF FORM=EXP ID=DEN*
>>>>>> Image file directory listing for:TEST/REF
>>>>>> Pos Satellite/ Date Time Center Res (km)
>>>>>> Image_Size
>>>>>> sensor Lat Lon Lat Lon
>>>>>> --- ------------- ------------ -------- ---- ---- ----- -----
>>>>>> ------------
>>>>>> 0 DERIVED DATA 0 JAN 00000 00:00:00
>>>>>> proj: 0 created: 0000000 0 memo:
>>>>>> type: cal type:
>>>>>> offsets: data= 0 navigation= 0 calibration= 0
>>>>>> auxiliary= 0
>>>>>> doc length: 0 cal length: 0 lev length: 0 PREFIX= 0
>>>>>> valcod: 0 zcor: 0 avg-smp: N
>>>>>> lcor: 0 ecor: 0 bytes per pixel: 0 ss: 0
>>>>>> Resolution Factors (base=1): Line= Element=
>>>>> An *IMGDISP* just prints out 'IMGDISP: done' without anything making
>>>>> it to the display.
>>>>>
>>>>> Thanks -
>>>>> Bob Carp
>>>>>
>>>>> On 6/14/2015 3:19 PM, Robert Rabin wrote:
>>>>>> Hi Tom,
>>>>>>
>>>>>> Thanks! Hopefully, the differences with the Unidata version of McIDAS-X
>>>>>> will not be too hard to find.
>>>>>>
>>>>>> -Bob
>>>>>>
>>>>>> On Sun, Jun 14, 2015 at 09:34:44AM -0600, Unidata McIDAS Support wrote:
>>>>>>> Hi Bob,
>>>>>>>
>>>>>>> re:
>>>>>>>> Attached are the following files:
>>>>>>>>
>>>>>>>> KBOU_SDUS55_TV0DEN_201506042350 (downloaded from NCDC)
>>>>>>>> TDEN_SDUS00_TV0DEN_201405202230 (file obtained from NEXRAD/ROC).
>>>>>>> Thanks!
>>>>>>>
>>>>>>> re:
>>>>>>>> I believe the problem with the "D" command occurred with both files.
>>>>>>>> Thanks for following up on this!
>>>>>>> I extracted both of the TV0 files you provided, and added them to
>>>>>>> the TV0 dataset I created for testing. I am able to display and
>>>>>>> interrogate all three test images without problems in the Unidata
>>>>>>> version of McIDAS-X.
>>>>>>>
>>>>>>> In order to determine if there is some relevant difference between the
>>>>>>> Unidata and SSEC McIDAS-X releases, I have been looking through relevan
> t
>>>>>>> code, and I do not see why the SSEC v2015.1 version that Jim N. updated
>>>>>>> does not work correctly.
>>>>>>>
>>>>>>> I will need to work with Jim to see if there is some difference that I
>>>>>>> am overlooking. More as the investigations continue...
>>>>>>>
>>>>>>> Cheers,
>>>>>>>
>>>>>>> Tom
>>>>>>> --
>>>>>>> ***********************************************************************
> **
>>> ***
>>>>>>> Unidata User Support UCAR Unidata Pr
> og
>>> ram
>>>>>>> (303) 497-8642 P.O. Box
> 3
>>> 000
>>>>>>> address@hidden Boulder, CO
> 8
>>> 0307
>>>>>>> -----------------------------------------------------------------------
> --
>>> ---
>>>>>>> Unidata HomePagehttp://www.unidata.ucar.edu
>>>>>>> ***********************************************************************
> **
>>> ***
>>>>>>>
>>>>>>> Ticket Details
>>>>>>> ===================
>>>>>>> Ticket ID: CCM-472749
>>>>>>> Department: Support McIDAS
>>>>>>> Priority: Normal
>>>>>>> Status: Closed
>>>>>>>
>>>
>>> --------------080105010500090005040000
>>> Content-Type: text/html; charset=ISO-8859-1
>>> Content-Transfer-Encoding: 7bit
>>>
>>> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
>>> <html>
>>> <head>
>>> <meta content="text/html; charset=ISO-8859-1"
>>> http-equiv="Content-Type">
>>> </head>
>>> <body text="#000000" bgcolor="#ffffff">
>>> Hi all --<br>
>>> <br>
>>> 1.) One thing I did which I think is helping me to understand
>>> things a little better<br>
>>> is to serve Bob's data via 3 different ADDE datasets:<br>
>>> <br>
>>>
>>> N1=RCI,N2=NCDCR,TYPE=IMAGE,RT=N,K=NEXR,R1=1,R2=999999,MASK=/home/rabin/
> tdw
>>> r/ncdctest/TDEN*TR*,C=B.
>>> R. TDWR reflectivity files,<br>
>>>
>>> N1=RCI,N2=NCDCS,TYPE=IMAGE,RT=N,K=NEXR,R1=1,R2=999999,MASK=/home/rabin/
> tdw
>>> r/ncdctest/TDEN*TS*,C=B.
>>> R. TDWR ????? files,<br>
>>>
>>> N1=RCI,N2=NCDCV,TYPE=IMAGE,RT=N,K=NEXR,R1=1,R2=999999,MASK=/home/rabin/
> tdw
>>> r/ncdctest/TDEN*TV*,C=B.
>>> R. TDWR velocity files,<br>
>>> <br>
>>> Before I was serving everything via a more global TDEN* dat
> ase
>>> t,
>>> and I think that was confusing the issue.<br>
>>> FYI, to look at RCI data, you must first: LOGON GOPS
> 99
>>> 99
>>> (Please don't share this (highly secure) pw with anybody :)
> )<
>>> br>
>>> <br>
>>> 2.) Given #1 above, I concur with Bob Carp at the McIDAS Help
>>> Desk. Using the 2015.1 version of M-X currently installed<b
> r>
>>> on rci.ssec.wisc.edu, I see reasonable data now from the files
>>> named: TDEN_SDUS00_TV0DEN_2014052022?? Neither<
> br>
>>> the *TR* nor *TS* files are being served properly, however.
> &nb
>>> sp; I am
>>> seeing all 0's, just like Bob.<br>
>>> <br>
>>> 3.) Bob, you said: "I just saw the explanation for wh
> y t
>>> he TR0
>>> files weren't working..." What is this? &n
> bsp
>>> ; I did not see<br>
>>> that thread anywhere. Does this mean that a fix is at
> ha
>>> nd for
>>> the TR0 files? Where do things stand with the TS0 fil
> es?
>>> <br>
>>> <br>
>>> Later!<br>
>>> <br>
>>> Sincerely,<br>
>>> <br>
>>> Jim<br>
>>> -----<br>
>>> On 6/16/2015 12:15 PM, McIDAS Help Desk wrote:
>>> <blockquote cite="mid:address@hidden" type="cite">
>>> <meta content="text/html; charset=ISO-8859-1"
>>> http-equiv="Content-Type">
>>> <div class="moz-cite-prefix">Sorry about that, I just saw the
>>> explanation for why the TR0 files weren't working... should have
>>> looked back at older emails :( . That being said, I'm using
>>> McIDAS-X 2015.1 and I'm seeing what looks like good IMGPROBE
>>> output of the TV0 data.<br>
>>> <b><br>
>>> </b>
>>> <blockquote type="cite"><b>IMGDISP TEST/VEL2.1 MAG=-2 ID=DEN</b>&nb
> sp;
>>> &nb
> sp
>>> ; &n
> bs
>>> p; &
> nb
>>> sp;
>>>
>>> <br>
>>> Beginning Image Data transfer, bytes=
>>> 309164  
> ;&n
>>> bsp;  
> ;&
>>> nbsp; &nbs
> p;
>>> <br>
>>> IMGDISP: loaded frame
>>> 17 &nb
> sp;
>>> &nb
> sp
>>> ; &n
> bs
>>> p; &
> nb
>>> sp;
>>> <br>
>>> IMGDISP:
>>> done &
> nbs
>>> p; &
> nb
>>> sp;
> &n
>>> bsp;  
> ;&
>>> nbsp; &nbs
> p;
>>>
>>>
>>> <br>
>>>  
> ;&n
>>> bsp;  
> ;&
>>> nbsp; &nbs
> p;
>>> &nb
> sp
>>> ; &n
> bs
>>> p; &
> nb
>>> sp;
>>>
>>> <br>
>>> Image Name
> &nb
>>> sp; ID Day  
> ;
>>> Nominal Time Scan
>>> Time Band &n
> bsp
>>> ; <br>
>>> ---------------- --- -
> ---
>>> --- ------------
>>> --------- ---- &nb
> sp;
>>> <br>
>>> TEST/VEL2 &
> nbs
>>> p; DEN 4 Jun 15155 23:50:41
> &n
>>> bsp;
>>> MISSING 9 &n
> bsp
>>> ; <br>
>>>  
> ;&n
>>> bsp;  
> ;&
>>> nbsp; &nbs
> p;
>>> &nb
> sp
>>> ; &n
> bs
>>> p; &
> nb
>>> sp;
>>>
>>> <br>
>>>  
> ;&n
>>> bsp; File
> &n
>>> bsp; Nominal Image
>>> RAW BRIT &nb
> sp;
>>> VEL <br>
>>> Lat/Lon &nb
> sp;
>>> Line/Element
>>> Line/Element  
> ;&n
>>> bsp;  
> ;&
>>> nbsp; KT &
> nb
>>> sp; <br>
>>> 39:58:48 / 105:03:45 412/ 294
> &nb
>>> sp; 413/ 295 &nb
> sp
>>> ;
>>> 158 158 &nbs
> p;&
>>> nbsp; 28<br>
>>>  
> ;&n
>>> bsp;  
> ;&
>>> nbsp; &nbs
> p;
>>> &nb
> sp
>>> ; &n
> bs
>>> p; &
> nb
>>> sp;
>>>
>>> <br>
>>> IMGPROBE:
>>> Done &
> nbs
>>> p; &
> nb
>>> sp;
> &n
>>> bsp;  
> ;&
>>> nbsp; &nbs
> p;
>>>
>>>
>>> <br>
>>>  
> ;&n
>>> bsp;  
> ;&
>>> nbsp; &nbs
> p;
>>> &nb
> sp
>>> ; &n
> bs
>>> p; &
> nb
>>> sp;
>>>
>>> <br>
>>> Image Name
> &nb
>>> sp; ID Day  
> ;
>>> Nominal Time Scan
>>> Time Band &n
> bsp
>>> ; <br>
>>> ---------------- --- -
> ---
>>> --- ------------
>>> --------- ---- &nb
> sp;
>>> <br>
>>> TEST/VEL2 &
> nbs
>>> p; DEN 4 Jun 15155 23:50:41
> &n
>>> bsp;
>>> MISSING 9 &n
> bsp
>>> ; <br>
>>>  
> ;&n
>>> bsp;  
> ;&
>>> nbsp; &nbs
> p;
>>> &nb
> sp
>>> ; &n
> bs
>>> p; &
> nb
>>> sp;
>>>
>>> <br>
>>>  
> ;&n
>>> bsp; File
> &n
>>> bsp; Nominal Image
>>> RAW BRIT &nb
> sp;
>>> VEL <br>
>>> Lat/Lon &nb
> sp;
>>> Line/Element
>>> Line/Element  
> ;&n
>>> bsp;  
> ;&
>>> nbsp; KT &
> nb
>>> sp; <br>
>>> 39:22:45 / 104:07:37 858/ 828
> &nb
>>> sp; 859/ 829 &nb
> sp
>>> ;
>>> 117 117 &nbs
> p;&
>>> nbsp; -11<br>
>>> <br>
>>> IMGPROBE: Done<br>
>>> </blockquote>
>>> <br>
>>> I've tested with both of the TV0 files sent out by Bob R on
>>> 06/13.<br>
>>> <br>
>>> - Bob Carp<br>
>>> <br>
>>> On 6/16/2015 10:02 AM, McIDAS Help Desk wrote:<br>
>>> </div>
>>> <blockquote cite="mid:address@hidden" type="cite">
>>> <meta content="text/html; charset=ISO-8859-1"
>>> http-equiv="Content-Type">
>>> <div class="moz-cite-prefix">Hi all -<br>
>>> <br>
>>> Barry is on vacation this week, so I've been looking at this
>>> issue this morning. Perhaps I missed something earlier, but
> I
>>> don't think that the problem is with the velocity (TV0) files,
>>> but rather with the reflectivity files (TR0). The TV0 files
> I
>>> have are working fine for me in McIDAS-X, McIDAS-V and the
>>> IDV.<br>
>>> <br>
>>> Tom, have you tried the TR0 file in Unidata McIDAS-X?<br>
>>> <br>
>>> When I do an IMGLIST in McIDAS-X of a TR0 file, everything
>>> lists out as 0:<br>
>>> <blockquote type="cite"><b>IMGLIST TEST/REF FORM=EXP ID=DEN</b><b
> r>
>>> Image file directory listing for:TEST/REF<br>
>>> Pos Satellite/ &
> nbs
>>> p; Date Time &nb
> sp
>>> ; Center Res
>>> (km) Image_Size<br>
>>> sensor &n
> bsp
>>> ; &n
> bs
>>> p; &
> nb
>>> sp; Lat Lon
>>> Lat Lon<br>
>>> --- ------------- ------------ --------
> --
>>> -- ---- -----
>>> ----- ------------<br>
>>> 0 DERIVED DATA 0 JAN 00000
> 00
>>> :00:00<br>
>>> proj: 0 created: 000
> 000
>>> 0 0 memo:<br>
>>> type: &nb
> sp;
>>> cal type:<br>
>>> offsets: data=
> &nb
>>> sp; 0 navigation= 0
>>> calibration= 0 auxiliary= 0
> <br
>>> doc length: 0
> cal
>>> length: 0 lev length: 0
>>> PREFIX= 0<br>
>>> valcod: &
> nbs
>>> p; 0 zcor: 0 avg-smp: N<br>
>>> lcor: 0 ecor:&
> nbs
>>> p; 0 bytes per pixel: 0 ss: 0<br>
>>> Resolution Factors (base=1): &nbs
> p;
>>> Line= Element=</block
> qu
>>> ote>
>>> <br>
>>> An<b>IMGDISP</b> just prints out 'IMGDISP: done' without
>>> anything making it to the display.<br>
>>> <br>
>>> Thanks -<br>
>>> Bob Carp<br>
>>> <br>
>>> On 6/14/2015 3:19 PM, Robert Rabin wrote:<br>
>>> </div>
>>> <blockquote cite="mid:address@hidden"
>>> type="cite">
>>> <pre wrap="">Hi Tom,
>>>
>>> Thanks! Hopefully, the differences with the Unidata version of McIDAS-X
>>> will not be too hard to find.
>>>
>>> -Bob
>>>
>>> On Sun, Jun 14, 2015 at 09:34:44AM -0600, Unidata McIDAS Support wrote:
>>> </pre>
>>> <blockquote type="cite">
>>> <pre wrap="">Hi Bob,
>>>
>>> re:
>>> </pre>
>>> <blockquote type="cite">
>>> <pre wrap="">Attached are the following files:
>>>
>>> KBOU_SDUS55_TV0DEN_201506042350 (downloaded from NCDC)
>>> TDEN_SDUS00_TV0DEN_201405202230 (file obtained from NEXRAD/ROC).
>>> </pre>
>>> </blockquote>
>>> <pre wrap="">Thanks!
>>>
>>> re:
>>> </pre>
>>> <blockquote type="cite">
>>> <pre wrap="">I believe the problem with the "D" command occur
> red
>>> with both files.
>>> Thanks for following up on this!
>>> </pre>
>>> </blockquote>
>>> <pre wrap="">I extracted both of the TV0 files you provided, an
> d a
>>> dded them to
>>> the TV0 dataset I created for testing. I am able to display and
>>> interrogate all three test images without problems in the Unidata
>>> version of McIDAS-X.
>>>
>>> In order to determine if there is some relevant difference between the
>>> Unidata and SSEC McIDAS-X releases, I have been looking through relevant
>>> code, and I do not see why the SSEC v2015.1 version that Jim N. updated
>>> does not work correctly.
>>>
>>> I will need to work with Jim to see if there is some difference that I
>>> am overlooking. More as the investigations continue...
>>>
>>> Cheers,
>>>
>>> Tom
>>> --
>>> ***************************************************************************
> *
>>> Unidata User Support UCAR Unidata Progra
> m
>>> (303) 497-8642 P.O. Box 300
> 0
>>> <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:sup
> por
>>> address@hidden">address@hidden</a>
>>> Boulder, CO 80307
>>> ---------------------------------------------------------------------------
> -
>>> Unidata HomePage<a moz-do-not-send="true" class="moz-tx
>>> t-link-freetext" href="http://www.unidata.ucar.edu";>http://www.unidata.ucar
> .e
>>> du</a>
>>> ***************************************************************************
> *
>>>
>>>
>>> Ticket Details
>>> ===================
>>> Ticket ID: CCM-472749
>>> Department: Support McIDAS
>>> Priority: Normal
>>> Status: Closed
>>>
>>> </pre>
>>> </blockquote>
>>> </blockquote>
>>> <br>
>>> </blockquote>
>>> <br>
>>> </blockquote>
>>> <br>
>>> </body>
>>> </html>
>>>
>>> --------------080105010500090005040000--
>>>
>> --
>> **********************************************************************<
>> Unidata User Support UCAR Unidata Program<
>> (303)497-8643 P.O. Box 3000<
>> address@hidden Boulder, CO 80307<
>> ----------------------------------------------------------------------<
>> Unidata Web Support http://www.unidata.ucar.edu/support<
>> ----------------------------------------------------------------------<
>> NOTE: All email exchanges with Unidata User Support are recorded in the
>> Unidata inquiry tracking system and then made publicly available
>> through the web. If you do not want to have your interactions made
>> available in this way, you must let us know in each email you send to us.
>
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web. If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.