Shift in trajectory between TR with calculate_kspace() #175
-
Hello, this is my first post here. I hope I did not overlook something in the issues section regarding this matter... In version 1.4.0 there is a k-space shift between TR when calling the function This does not happen in version 1.3.1 I'm just wondering if this is intentional, or if this could be an issue? I've added two examples with interleaved spirals for version 1.3.1 and 1.4.0 (with https://github.com/FrankZijlstra/pypulseq/tree/bugfixes installation). Spirals were created with the https://github.com/mrphysics-bonn/spiraltraj package. Code for reproduction: V1.4.0:
V1.3.1:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi @felixlandmeyer. I ran your test case. The result is indeed as you shared. Here is the reason: Spirals are not starting from zero. I guess the PyPulseq 1.3.1 was adding the zeros, but v1.4.0 is not. I feel like there should be a warning for such cases, I will take a look. If you go ahead and uncomment line 36 in your Pulseq v1.4.0 and change it to |
Beta Was this translation helpful? Give feedback.
Hi @felixlandmeyer. I ran your test case. The result is indeed as you shared. Here is the reason:
Spirals are not starting from zero. I guess the PyPulseq 1.3.1 was adding the zeros, but v1.4.0 is not. I feel like there should be a warning for such cases, I will take a look.
If you go ahead and uncomment line 36 in your Pulseq v1.4.0 and change it to
spiral = np.concatenate((np.zeros((1,2)), spiral, np.zeros((1,2))), axis=0)
to add zeros to the beginning and end (you don't need 5 zeros, 1 should be enough), here is the plot I get: