Conversation
|
In dc500da I changed how the amplitude of the readout gradient is modified for the symmetric EPI readout. In the previous version the EPI-object was modified. This meant that for an odd number of phase encoding steps, the readout gradient of the EPI-object was flipped at the end of I removed the rev-label here: mrseq/src/mrseq/utils/EpiReadout.py Line 633 in dc500da I think this should be fine but maybe @schuenke could double check |
| epi2d.adc, | ||
| pp.make_label(label='REV', type='SET', value=gx.amplitude < 0), | ||
| pp.make_label(label='SEG', type='SET', value=gx.amplitude < 0), | ||
| pp.make_label(label='AVG', type='SET', value=(n + 1) == 3), |
There was a problem hiding this comment.
| pp.make_label(label='AVG', type='SET', value=(n + 1) == 3), |
There was a problem hiding this comment.
I would remove this, because it leads to 1 readout having avg = 0 and two readouts with avg = 0,1 which then leads to problems for the MRpro sorting routines. They are not really averages anyway because there is T2* decay.
| epi2d.adc, | ||
| pp.make_label(label='REV', type='SET', value=gx_sign < 0), | ||
| pp.make_label(label='SEG', type='SET', value=gx_sign < 0), | ||
| pp.make_label(label='AVG', type='SET', value=(n + 1) == 3), |
There was a problem hiding this comment.
| pp.make_label(label='AVG', type='SET', value=(n + 1) == 3), |
same as for epi2d_fid
|
The above changes were necessary to get the correct trajectory for the navigators. Probably similary changes are needed for the epi2d_fid. We could add the part on reading out the navigators to the example notebook. What do you think @schuenke ? |
- unify code for FID and SE sequence - move navigator code from kernels to EpiReadout class - allow arbitrary number of navigator scans


To do: