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

Bigarray: complex <-> float #4333

Closed
vicuna opened this issue Jun 30, 2007 · 3 comments
Closed

Bigarray: complex <-> float #4333

vicuna opened this issue Jun 30, 2007 · 3 comments

Comments

@vicuna
Copy link

vicuna commented Jun 30, 2007

Original bug ID: 4333
Reporter: @Chris00
Status: acknowledged (set by @xavierleroy on 2012-08-06T16:30:19Z)
Resolution: open
Priority: normal
Severity: feature
Version: 3.10.0
Category: otherlibs
Tags: patch
Monitored by: @hcarty @Chris00

Bug description

It would be nice to have in place "reshaping" between complex and float bigarrays -- splitting complexes in real and imaginary parts. Something along the lines

to_float : (Complex.t, complex64_elt, 'a) Genarray.t -> (float, float64_elt, 'a) Genarray.t
to_complex : (float, float64_elt, 'a) Genarray.t -> (Complex.t, complex64_elt, 'a) Genarray.t

(and the same for Array1, Array2, and Array3). [to_complex] will raise an exception if the last (for c_layout) or first (for fortran_layout) dimension is not even.
The interest of this is for in-place transforms, specifically in my case in-place FFT transforms between float and hermitian arrays.

File attachments

@vicuna
Copy link
Author

vicuna commented Aug 6, 2012

Comment author: @xavierleroy

I've been sleeping for too long on this feature request. If anyone feels strongly about it, a patch is welcome.

@vicuna
Copy link
Author

vicuna commented Aug 9, 2012

Comment author: @Chris00

Patch uploaded.

@github-actions
Copy link

This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc.

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