arrayfire / arrayfire/arrayfire

[BUG] approx1 and approx2 produce suspect values in last bin

未關閉
#3,239 1 則留言 0 個 reaction 已指派 1 人 已被 @syurkevi 認領 在 GitHub 檢視
bug
主要語言
C++
星號
4.9k
分支
555
平均合併
1 小時 24 分鐘
30 天內合併 PR
1

描述

approx1 and approx2 cubic spline interpolation methods produce suspect values in the last bin at the boundary.

Description
===========
* Used official installers
* Occurs on all backends
* Partial workaround is just using higher resolution so that boundary regions are small
* Bug is reliably reproducible
* Expected output to match scipy's RectBivariateSpline method, which wraps fitpack
* No error output

Example interpolating on cos(x) with comparison to scipy:
image

Reproducible Code and/or Steps
------------------------------
* Any use of approx1 or approx2 with cubic spline interpolation type

System Information
------------------
Tested with AF version 3.7.2 on Mac & 3.8.1 on Ubuntu 20.04, both via the Rust bindings.

Info from Mac for convenience:
```
Available backends: [OPENCL, CPU]
Active backend: CPU
Number of available devices: 1
Device number: 0
Device info: ("Intel", "CPU", "AppleClang 10.0.0.10001044", "0.0")
```

Checklist
---------

- [x] Using the latest available ArrayFire release
- [x] GPU drivers are up to date

貢獻指南

開啟貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。