[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
- Subject: 20150616: [Staging #CCM-472749]: Re: 20150522: TDWR Level III data from NOAA NEXRAD Operational Support Facility in McX and McV
- Date: Tue, 16 Jun 2015 16:46:41 -0600
Hi Bob,
In order to bring you a bit more up to speed, I want to make a quick
comment regarding all of the exchanges that have been flying back and
forth regarding support for the TDWR files that have been giving Bob
Rabin and Joleen problems:
I told Barry that I was going to work with Jim N. to get my modified code
incorporated into an SSEC McIDAS-X installation where the mods could be
tested by Bob Rabin and/or Joleen to make sure that there was nothing
omitted. After that test (which I thought would be a couple of minutes
of someone's time), I would update the SSEC McIDAS-X CVS repository with
the code modifications and update the inquiry with relevant information.
The complication arose by Bob Rabin's use of the remote ADDE interface
on rci.ssec.wisc.edu since SSEC v2013.1 is the code being used for
the remote ADDE access, not SSEC v2015.1 where Jim installed my updated
code.
Please let me know if you have questions about what has transpired so far
and what is remaining.
Cheers,
Tom
Bob Carp wrote:
>For #3 below, I don't think you were cc'd on some emails. Tom Y looked
>at the TR0 reflectivity files and noted:
>
>> It turns out that the NEXRAD Level III server in McIDAS-X was missing
>> the definitions for several (previously unseen by me) products, one of
>> which is the one specified in the TR0 file you sent in a previous email.
>> I just added support for images with product code 180 (256 level base reflec
> tivity with 0.08x1 Nmi x Deg resolution), and tested the code change in Unida
> ta McIDAS-X... the product now correctly displays.
>>
>> I will be adding support for the other products (product codes 183 16 level
> base velocity and 187 long range 16 level base reflectivity) as soon as I can
> .
>
>
>You can monitor McIDAS-X Inquiry 15860
><http://mcidas.ssec.wisc.edu/inquiry-x/index.php?inquiry=15860> for any
>updates. Thus far, nothing has been checked in (the Action part of the
>inquiry is empty). Before putting this into a McIDAS-X release, code
>changes would need to be checked in and tested. There will also have to
>be updates to McV and the IDV to get the TR0 files working there. This
>is written up as McIDAS-V Inquiry 2070
><http://mcidas.ssec.wisc.edu/inquiry-v/?inquiry=2070>. As for the TS0
>files, this is the first that I've heard of them. I only have TR0 and
>TV0 files. Can you please send me a TS0 file so we have one to test with?
>
>Thanks -
>Bob Carp
>
>On 6/16/2015 2:23 PM, Jim Nelson wrote:
>> Hi all --
>>
>> 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,
>>
>> Before I was serving everything via a more global TDEN* dataset, and
>> I think that was confusing the issue.
>> FYI, to look at RCI data, you must first: LOGON GOPS 9999 (Please
>> don't share this (highly secure) pw with anybody :) )
>>
>> 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.
>>
>> 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. Does this mean that a fix is at hand for the
>> TR0 files? Where do things stand with the TS0 files?
>>
>> Later!
>>
>> Sincerely,
>>
>> Jim
>> -----
>> 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 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 Pro
> gram
>>>>>> (303) 497-8642 P.O. Box
> 3000
>>>>>> address@hidden Boulder, CO
> 80307
>>>>>> ------------------------------------------------------------------------
> ----
>>>>>> Unidata HomePagehttp://www.unidata.ucar.edu
>>>>>> ************************************************************************
> ****
>>>>>>
>>>>>>
>>>>>> Ticket Details
>>>>>> ===================
>>>>>> Ticket ID: CCM-472749
>>>>>> Department: Support McIDAS
>>>>>> Priority: Normal
>>>>>> Status: Closed
>>>>>>
>>>>
>>>
>>
>
>
>--------------070407020409020605020704
>Content-Type: text/html; charset=ISO-8859-1
>Content-Transfer-Encoding: 7bit
>
><html>
> <head>
> <meta content="text/html; charset=ISO-8859-1"
> http-equiv="Content-Type">
> </head>
> <body bgcolor="#FFFFFF" text="#000000">
> <div class="moz-cite-prefix">Hi Jim -<br>
> <br>
> For #3 below, I don't think you were cc'd on some emails. Tom Y
> looked at the TR0 reflectivity files and noted:<br>
> <br>
> <pre><blockquote type="cite"><pre>It turns out that the NEXRAD Level III
> server in McIDAS-X was missing the definitions for several (previously unsee
> n by me) products, one of which is the one specified in the TR0 file you sent
> in a previous email.
>
>I just added support for images with product code 180 (256 level base reflecti
> vity with 0.08x1 Nmi x Deg resolution), and tested the code change in Unidata
> McIDAS-X... the product now correctly displays.
>
>I will be adding support for the other products (product codes 183 16 level ba
> se velocity and 187 long range 16 level base reflectivity) as soon as I can.<
> /pre></blockquote></pre>
> <br>
> You can monitor <a
> href="http://mcidas.ssec.wisc.edu/inquiry-x/index.php?inquiry=15860";>M
> cIDAS-X
> Inquiry 15860</a> for any updates. Thus far, nothing has been
> checked in (the Action part of the inquiry is empty). Before
> putting this into a McIDAS-X release, code changes would need to
> be checked in and tested. There will also have to be updates to
> McV and the IDV to get the TR0 files working there. This is
> written up as <a
> href="http://mcidas.ssec.wisc.edu/inquiry-v/?inquiry=2070";>McIDAS-V
> Inquiry 2070</a>. As for the TS0 files, this is the first that
> I've heard of them. I only have TR0 and TV0 files. Can you
> please send me a TS0 file so we have one to test with?<br>
> <br>
> Thanks -<br>
> Bob Carp<br>
> <br>
> On 6/16/2015 2:23 PM, Jim Nelson wrote:<br>
> </div>
> <blockquote cite="mid:address@hidden" type="cite">
> <meta content="text/html; charset=ISO-8859-1"
> http-equiv="Content-Type">
> 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/t
> dwr/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/t
> dwr/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/t
> dwr/ncdctest/TDEN*TV*,C=B.
>
> R. TDWR velocity files,<br>
> <br>
> Before I was serving everything via a more global TDEN* data
> set,
> and I think that was confusing the issue.<br>
> FYI, to look at RCI data, you must first: LOGON GOPS
> 9999
> (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<br
> >
> on rci.ssec.wisc.edu, I see reasonable data now from the files
> named: TDEN_SDUS00_TV0DEN_2014052022?? Neither<b
> r>
> the *TR* nor *TS* files are being served properly, however. &
> nbsp; I
> am seeing all 0's, just like Bob.<br>
> <br>
> 3.) Bob, you said: "I just saw the explanation for why
> the TR0
> files weren't working..." What is this? &nb
> sp; I did not see<br>
> that thread anywhere. Does this mean that a fix is at
> hand for
> the TR0 files? Where do things stand with the TS0 file
> s?<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>&nbs
> p; &nb
> sp; &n
> bsp; &
> nbsp;
>
>
> <br>
> Beginning Image Data transfer, bytes=
> 309164
>  
> ; &nbs
> p; <br>
> IMGDISP: loaded frame
> 17 &nbs
> p; &nb
> sp; &n
> bsp; &
> nbsp;
> <br>
> IMGDISP:
> done &n
> bsp; &
> nbsp;
>  
> ; &nbs
> p;
>
>
> <br>
>
>  
> ; &nbs
> p; &nb
> sp; &n
> bsp; &
> nbsp;
>
>
> <br>
> Image Name &
> nbsp; ID Day  
> ; Nominal Time Scan
> Time Band &nb
> sp; <br>
> ---------------- --- --
> ----- ------------
> --------- ---- &nbs
> p; <br>
> TEST/VEL2 &n
> bsp; DEN 4 Jun 15155 23:50:41
>
> MISSING 9 &nb
> sp; <br>
>
>  
> ; &nbs
> p; &nb
> sp; &n
> bsp; &
> nbsp;
>
>
> <br>
>
> File
> Nominal Image
> RAW BRIT &nbs
> p; VEL <br>
> Lat/Lon &nbs
> p; Line/Element
> Line/Element
>  
> ; KT &
> nbsp; <br>
> 39:58:48 / 105:03:45 412/ 294 &
> nbsp; 413/ 295 &nb
> sp;
> 158 158  
> ; 28 <br>
>
>  
> ; &nbs
> p; &nb
> sp; &n
> bsp; &
> nbsp;
>
>
> <br>
> IMGPROBE:
> Done &n
> bsp; &
> nbsp;
>  
> ; &nbs
> p;
>
>
> <br>
>
>  
> ; &nbs
> p; &nb
> sp; &n
> bsp; &
> nbsp;
>
>
> <br>
> Image Name &
> nbsp; ID Day  
> ; Nominal Time Scan
> Time Band &nb
> sp; <br>
> ---------------- --- --
> ----- ------------
> --------- ---- &nbs
> p; <br>
> TEST/VEL2 &n
> bsp; DEN 4 Jun 15155 23:50:41
>
> MISSING 9 &nb
> sp; <br>
>
>  
> ; &nbs
> p; &nb
> sp; &n
> bsp; &
> nbsp;
>
>
> <br>
>
> File
> Nominal Image
> RAW BRIT &nbs
> p; VEL <br>
> Lat/Lon &nbs
> p; Line/Element
> Line/Element
>  
> ; KT &
> nbsp; <br>
> 39:22:45 / 104:07:37 858/ 828 &
> nbsp; 859/ 829 &nb
> sp;
> 117 117  
> ; -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><br
> >
> Image file directory listing for:TEST/REF<br>
> Pos Satellite/ &n
> bsp; Date Time &nb
> sp; Center
> Res (km) Image_Size<br>
> sensor &nb
> sp; &n
> bsp; &
> nbsp; Lat Lon
> Lat Lon<br>
> --- ------------- ------------ --------
> ---- ----
> ----- ----- ------------<br>
> 0 DERIVED DATA 0 JAN 00000
> 00:00:00<br>
> proj: 0 created: 0000
> 000 0 memo:<br>
> type: &nbs
> p; cal type:<br>
> offsets: data= &
> nbsp; 0 navigation= 0
> calibration= 0 auxiliary= 0<
> br>
> doc length: 0 c
> al length: 0 lev length: 0
> PREFIX= 0<br>
> valcod: &n
> bsp; 0 zcor: 0 avg-smp: N<br>
> lcor: 0 ecor:&n
> bsp; 0 bytes per pixel: 0 ss: 0<br>
> Resolution Factors (base=1):  
> ; Line=
> Element=</blockquote>
> <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 occurr
> ed with both files.
>Thanks for following up on this!
></pre>
> </blockquote>
> <pre wrap="">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 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 Program
>(303) 497-8642 P.O. Box 3000
><a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:suppor
> 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>
> </blockquote>
> <br>
> </body>
></html>
>
>--------------070407020409020605020704--
>
--
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.