Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
N
NIFTy
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 13
    • Merge Requests 13
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ift
  • NIFTy
  • Issues
  • #294

Closed
Open
Opened Apr 17, 2020 by Martin Reinecke@mtrOwner

Potential confusion in the direction of FFTs

In the current implementation of FFTOperator (https://gitlab.mpcdf.mpg.de/ift/nifty/-/blob/NIFTy_6/nifty6/operators/harmonic_operators.py#L76) we have the code:

        if x.domain[self._space].harmonic:  # harmonic -> position
            func = fft.fftn
            fct = 1.
        else:
            func = fft.ifftn
            fct = ncells

where x is the input field. This looks exactly the wrong way around.

@parras, @pfrank, @kjako, @reimar, @veberle, what do you think?

Switching the FFT direction breaks almost none of our tests (only one, which already has a FIXME :).

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
May 13, 2020
Due date
May 13, 2020
Reference: ift/nifty#294