Repository navigation
t_ktraj not returned from seq.calculate_kspace #281
Description
Hello,
apparently seq.calculate_kspace() in pypulseq does not return t_ktraj. t_ktraj is very helpful when comparing measured and nominal trajectories.
[k_traj_adc, k_traj, t_excitation, t_refocusing, t_adc] = seq.calculate_kspace()
vs. Matlab:
[ktraj_adc, t_adc, ktraj, t_ktraj, t_excitation, t_refocusing, slicepos, t_slicepos] = seq.calculateKspace();
It would be very helpful if calculateKspace() could be extended to the same functionality as in the Matlab Version.
All the Best
Activity
Nikbert commentedon May 14, 2025
I just added t_ktraj to the return statement of seq.calculate_kspace(), as it was already used there .
Now it works for me. I think it would make sense to apply this change to the master branch to make the behavior consistent with pulseq.
Nikbert commentedon May 14, 2025
OK, if the modification will be approved we have to change "ext_test_report.py", in line 33 as well. To expect the additional value t_ktraj.
Nikbert commentedon May 14, 2025
this issue would be fixed with pullrequest #282