arrayfire / arrayfire/arrayfire-python
delay scaling of ffts until after the transforms.
Open
- Dominant language
- Python
- Stars
- 422
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Description
As seen here, the results can be order of magnitudes off if the scaling happens upfront.
https://gist.github.com/pavanky/dc64fc83e0fa298e942a3e0ca07ccd15
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked gist and reproduce the FFT case where upfront scaling produces results orders of magnitude off. Trace the Python FFT entry point and its transform/scaling path; done means scaling is applied after the transforms and the reproduced results match the expected values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100