<div dir="ltr">Dave B,<div><br></div><div>That's great news. I look forward to the next release. Thank you.</div><div><br></div><div>--Dave A.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 25, 2014 at 4:47 PM, David Brown <span dir="ltr"><<a href="mailto:dbrown@ucar.edu" target="_blank">dbrown@ucar.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Dave,<br>
<br>
I can let you know that this issue has been addressed. For the next<br>
NCL release, coordinate subscripts may be any numeric type, and are<br>
independent of the type of the coordinate values.<br>
-dave<br>
<br>
On Thu, Nov 20, 2014 at 10:36 AM, David Brown <<a href="mailto:dbrown@ucar.edu">dbrown@ucar.edu</a>> wrote:<br>
> Hi Dave,<br>
> I am back now and I will look into this issue soon.<br>
> -dave<br>
><br>
> On Thu, Nov 20, 2014 at 12:52 AM, Dave Allured - NOAA Affiliate<br>
> <<a href="mailto:dave.allured@noaa.gov">dave.allured@noaa.gov</a>> wrote:<br>
>> Mary,<br>
>><br>
>> The "totype" workaround is working fine, it's just that the issue keeps<br>
>> coming back whenever we encounter type variations in new data and program<br>
>> combinations. For this and my original reasons, it would be helpful to have<br>
>> this feature in the language.<br>
>><br>
>> --Dave<br>
>><br>
>> On Wed, Nov 19, 2014 at 3:37 PM, Mary Haley <<a href="mailto:haley@ucar.edu">haley@ucar.edu</a>> wrote:<br>
>>><br>
>>> Hi Dave,<br>
>>><br>
>>> Our JIRA ticket database is down for maintenance at the moment, so I can't<br>
>>> check the status. I'm pretty sure nothing has been done on it yet. Dave<br>
>>> Brown will be the one to answer this, but he's not in this week.<br>
>>><br>
>>> You had mentioned that "totype" would work as a temporary fix. Is this<br>
>>> still working for you for now?<br>
>>><br>
>>> --Mary<br>
>>><br>
>>><br>
>>> On Wed, Nov 19, 2014 at 11:22 AM, Dave Allured - NOAA Affiliate<br>
>>> <<a href="mailto:dave.allured@noaa.gov">dave.allured@noaa.gov</a>> wrote:<br>
>>>><br>
>>>> NCL support,<br>
>>>><br>
>>>> Is there any progress on this request? This issue keeps coming up in my<br>
>>>> work group. We perform a lot of generalized file handling. Thank you.<br>
>>>><br>
>>>> --Dave<br>
>>>><br>
>>>> On Thu, Aug 22, 2013 at 12:30 PM, David Brown <<a href="mailto:dbrown@ucar.edu">dbrown@ucar.edu</a>> wrote:<br>
>>>>><br>
>>>>> Hi Dave,<br>
>>>>> This is a very good suggestion. We will create a ticket for it.<br>
>>>>> -dave<br>
>>>>><br>
>>>>> On Aug 22, 2013, at 12:06 PM, Dave Allured - NOAA Affiliate<br>
>>>>> <<a href="mailto:dave.allured@noaa.gov">dave.allured@noaa.gov</a>> wrote:<br>
>>>>><br>
>>>>> > NCL support,<br>
>>>>> ><br>
>>>>> > This is a request for improved support for mixed types in coordinate<br>
>>>>> > subscripting. For example, it is legal to subscript a double<br>
>>>>> > coordinate with floats, but going the other way is an error. This<br>
>>>>> > shows that type handling in simple NCL relational operators is more<br>
>>>>> > liberal than in coordinate subscripting:<br>
>>>>> ><br>
>>>>> > lats = (/ 0., 10., 20., 30., 40., 50., 60. /)<br>
>>>>> > x = (/ 0, 111, 222, 333, 444, 555, 666 /)<br>
>>>>> > x!0 = "lat"<br>
>>>>> > y = x<br>
>>>>> ><br>
>>>>> > x&lat = tofloat (lats)<br>
>>>>> > y&lat = todouble (lats)<br>
>>>>> ><br>
>>>>> > f1 = 20. ; floats<br>
>>>>> > f2 = 40.<br>
>>>>> > d1 = 20d ; doubles<br>
>>>>> > d2 = 40d<br>
>>>>> ><br>
>>>>> > ind1 = ind (y&lat .ge. f1 .and. y&lat .le. f2)<br>
>>>>> > print (ind1+"")<br>
>>>>> > print ("")<br>
>>>>> ><br>
>>>>> > ind2 = ind (x&lat .ge. d1 .and. x&lat .le. d2)<br>
>>>>> > print (ind2+"")<br>
>>>>> > print ("")<br>
>>>>> ><br>
>>>>> > sub1 = y({f1:f2}) ; float subscripts double<br>
>>>>> > print (sub1&lat+" "+typeof(sub1&lat))<br>
>>>>> > print ("")<br>
>>>>> ><br>
>>>>> > sub2 = x({d1:d2}) ; double subscripts float<br>
>>>>> > print (sub2&lat+" "+typeof(sub2&lat))<br>
>>>>> ><br>
>>>>> > Result:<br>
>>>>> ><br>
>>>>> > NCAR Command Language Version 6.1.2<br>
>>>>> > (0) 2<br>
>>>>> > (1) 3<br>
>>>>> > (2) 4<br>
>>>>> > (0)<br>
>>>>> > (0) 2<br>
>>>>> > (1) 3<br>
>>>>> > (2) 4<br>
>>>>> > (0)<br>
>>>>> > (0) 20 double<br>
>>>>> > (1) 30 double<br>
>>>>> > (2) 40 double<br>
>>>>> > (0)<br>
>>>>> > fatal:Coordinate subscript type mismatch. Subscript (0) can not be<br>
>>>>> > coerced to type of coordinate variable<br>
>>>>> > fatal:["Execute.c":8128]:Execute: Error occurred at or near line 26 in<br>
>>>>> > file mixed-mode-coord-subscripts.ncl<br>
>>>>> ><br>
>>>>> > I think it would be generally helpful if coordinate subscripting could<br>
>>>>> > be broadened to support all reasonable cases of mixed types. At a<br>
>>>>> > minimum, please support the same combinations as for the relational<br>
>>>>> > operators. I know that there are simple workarounds, but this<br>
>>>>> > improvement would benefit simpler user code and generalized file<br>
>>>>> > support. Thanks for your consideration.<br>
>>>>> ><br>
>>>>> > --Dave A.<br>
>>>>> > NOAA/PSD/CIRES Climate Analysis Branch<br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> ncl-talk mailing list<br>
>> List instructions, subscriber options, unsubscribe:<br>
>> <a href="http://mailman.ucar.edu/mailman/listinfo/ncl-talk" target="_blank">http://mailman.ucar.edu/mailman/listinfo/ncl-talk</a><br>
>><br>
</blockquote></div><br></div>