[ncl-talk] Serious bug in the taper (and taper_n) function with option 1

[Sakaguchi, Koichi]

Dear NCL support staff and users,

I found a bug in the ncl function taper (and taper_n) such that when the option 1 is chosen the function does not copy all the values of the input array to the output array, except for the portions that are tapered. In my environment (NERSC and PNNL computing facilities), the uncopied values in the output array are all zero. This bug had a serious impact on my work.

The function works correctly when option 0 is chosen. This difference arises because the output array is not initialized properly in the underlying fortran code (taper.f) when option 1 is selected.
I provided more details in the NCL github issues
https://github.com/NCAR/ncl/issues/171


I posted a bug report about a month ago following https://www.ncl.ucar.edu/Support/posting_guidelines.shtml, but no responses have been provided, so I am reporting here in the ncl-talk. I see a few even older postings without responses from the developers there... I am aware that NCL is in the maintenance mode without further development, but I think more close and regular attention should be paid to the issues posted on NCL github because NCL is still very widely used.

Best regards,

Koichi

--------------------------------
Koichi Sakaguchi, Ph.D.
Earth Scientist
ATMOSPHERIC SCIENCES & GLOBAL CHANGE

Pacific Northwest National Laboratory
3200 Innovation Blvd
PO Box 999, MSIN: K9-24
Richland, WA 99352 USA
Phone: 509-375-7385
Fax: 509-375-6448
Email:koichi.sakaguchi at pnnl.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.ucar.edu/pipermail/ncl-talk/attachments/20210822/4d3e99f4/attachment.html>