Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
P
pypocketfft
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 4
    • Issues 4
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Martin Reinecke
  • pypocketfft
  • Issues
  • #4

Closed
Open
Opened Jul 17, 2019 by Martin Reinecke@mtrMaintainer

sine and cosine transforms?

I'm thinking about adding sine and cosine transforms when I find some time. The main reason is that scipy.fft offers these transforms but will fall back to scipy.fftpack if they are called. I'm not worried about performance but rather about accuracy, which is notoriously bad for fftpack's real transforms (if the transform sizes are near-prime).

Also, at the moment, existing programs using scipy that do not switch explicitly to scipy.fft won't benefit from the new library and still use fftpack, correct? If pypocketfft contains fftpack's full functionality, then maybe it could replace fftpack entirely (behind scipy.fftpack's original interface, of course).

@peterbell10, do you think this is a useful plan? Or will it be too tedious to put pypocketfft behind the fftpack interface?

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: mtr/pypocketfft#4