Complex Float32 data are not well handle

[aTrotier]

While working on a benchmark against bart (which is using Float32). I wanted to create a data acq with that possibility.
One of the issue was in CartesianTrajectory3D

I had to change the type of the keyword parameters to Float32

T=Float32
 tr = MRIBase.CartesianTrajectory3D(Float32,128,128,numSlices=128,TE=T(0),AQ=T(0))

Should we change that ?

It is also the same issue for the reconstruction regularization parameters

[tknopp]

yes these need to be fixed but in a clever way. The point is that the user will often specify TE, AQ, lambda ... using Float64 even if the data should be reconstructed in Float32. Thus, these parameters should be promoted to the eltype of the array instead of enforcing them to be of the same type as the array (or in this case the first argument of the function).

[aTrotier]

I'll put that on my to do. Especially for all the high level functions. Le ven. 9 sept. 2022 à 21:27, Tobias Knopp ***@***.***> a écrit :

…

yes these need to be fixed but in a clever way. The point is that the user will often specify TE, AQ, lambda ... using Float64 even if the data should be reconstructed in Float32. Thus, these parameters should be promoted to the eltype of the array instead of enforcing them to be of the same type as the array (or in this case the first argument of the function). — Reply to this email directly, view it on GitHub <#103 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC5P7O7MRXG644EGJFIFNXDV5OFRBANCNFSM6AAAAAAQI2YOJM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[migrosser]

Commit d1efe5d should fix the issue with the type of TE and AQ in the trajectories. Furthermore, I changed setupIterativeReco so that the type of lambda is adapted to the underlying datatype in AcquisitionData in commit b84a9ee

[aTrotier]

Thanks ! Le ven. 30 sept. 2022 à 19:29, migrosser ***@***.***> a écrit :

…

Commit d1efe5d <d1efe5d> should fix the issue with the type of TE and AQ in the trajectories. Furthermore, I changed setupIterativeReco so that the type of lambda is adapted to the underlying datatype in AcquisitionData in commit b84a9ee <b84a9ee> — Reply to this email directly, view it on GitHub <#103 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC5P7OYAAA4OFPTBUM36MPLWA4PQPANCNFSM6AAAAAAQI2YOJM> . You are receiving this because you authored the thread.Message ID: ***@***.***>