Skip to content
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

Add stricter type requirements #115

Open
matze opened this issue Nov 14, 2016 · 0 comments
Open

Add stricter type requirements #115

matze opened this issue Nov 14, 2016 · 0 comments
Assignees
Milestone

Comments

@matze
Copy link
Contributor

matze commented Nov 14, 2016

Data is currently identified as an n-dimensional array of float arrays. However, certain filters require the input to contain semantically more specialized data (e.g. ifft input should be complex values). Passing more type information along the pipeline allows to catch subtle bugs.

There are two ways to implement this: 1) adding fields to the internal structure and add more API to query this or 2) using the meta data infrastructure. Open for discussion.

@matze matze added this to the Version 0.12 milestone Nov 14, 2016
@matze matze self-assigned this Nov 14, 2016
@matze matze modified the milestones: Version 0.12, Version 0.13 Nov 24, 2016
@matze matze modified the milestones: Version 0.13, Version 1.0 Dec 5, 2017
MarcusZuber pushed a commit that referenced this issue May 10, 2022
The kernel event for the FFT (in case of "from-real") was recorded by the
profiler but freed before profiling information was written out.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant