Skip to content

Fix default parameters for fftR2C and fftC2R from 0 to 1.0 #3178

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 5, 2021

Conversation

umar456
Copy link
Member

@umar456 umar456 commented Oct 4, 2021

Set the default value for norm_factor from 0 to 1 for fftR2C and fftC2R. The functionality is still the same but 1.0 is a better representation of the operation being performed.

Description

  • The default value for the norm_factor parameter on fft2 was set to zero instead of 1. The zero value implied that the returned value would always be zero but it actually means that the norm factor will be 1.

Changes to Users

No changes will need to be performed by the user.

Checklist

  • Rebased on latest master
  • Code compiles
  • Tests pass
  • [ ] Functions added to unified API
  • [ ] Functions documented

@umar456 umar456 added this to the 3.8.1 milestone Oct 4, 2021
@umar456 umar456 requested a review from syurkevi October 4, 2021 18:26
@9prady9 9prady9 merged commit 451331d into arrayfire:master Oct 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants