User Tools

Site Tools


biac:analysis:topup_correction

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
biac:analysis:topup_correction [2019/02/21 19:29]
cmp12
biac:analysis:topup_correction [2023/02/23 18:43] (current)
Line 7: Line 7:
 There will be two series of single timepoint EPI images.  You can grab relevant info to create the acq_params.txt files from your XML header. There will be two series of single timepoint EPI images.  You can grab relevant info to create the acq_params.txt files from your XML header.
  
-You need to calculate readout time in seconds ( the physical time it takes to get the acquisition matrix of a single slice ) and get the polarity direction ( phase encode direction ).+You need to calculate readout time in seconds of the PEPOLAR images ( the physical time it takes to get the acquisition matrix of a single slice ) and get the polarity direction ( phase encode direction ). 
  
 the readout time in seconds for the parameter file will be: the readout time in seconds for the parameter file will be:
-<code>readout = (echospacing * (acquisitionmatrix[0] * (percentsampling/100))) / 1e6 +**For singleband images :** 
 +<code> 
 +readout = (echospacing * (acquisitionmatrix[0] * (percentsampling/100))) / 1e6 
  
 echospacing in the BXH header is in microseconds echospacing in the BXH header is in microseconds
Line 16: Line 19:
  
  
-the polarity for the entry will have to be determined from the **seriesdescription**, which is typically "field map reverse polarity" or "field map regular"+**For mutli-band images the readout calculation is more complex:**  
 +<code> 
 +readout = ( ( ceil ((1/Round_factor) * AcquisitionMatrixPE / Asset_R_factor ) * Round_factor) - 1 ) * EchoSpacing * 0.000001 
 + 
 +AcquisitionMatrixPE = the acquisition size of the data ( acquisitionmatrix[0] ) 
 +Round_factor = 4 if partial fourier ( PFF is in scanoptions ), 2 if full fourier.  most all scans will be 4 
 +Asset_R_factor = the reciprocal of the first value of dcm tag (0043,1083) 
 +</code> 
 + 
 +unfortunately at this point the polarity of the images will have to be determined from visual inspection. we aren't provided enough information in the metadata to give an entry into the BXH file ( yet ). 
 + 
 +Here is a rough guide to help with inspection.  Take note of the eyeballs being crushed in for AP and stretched out for PA.  Below shows the PEPOLAR images in red/blue on top of a mean functional. 
 +{{:biac:analysis:connneuro_func.png?800|}} 
  
 reverse will be "-1" in the acq_params.txt and regular will be "1" reverse will be "-1" in the acq_params.txt and regular will be "1"
Line 62: Line 78:
 applytopup --imain=../bia6_00186_009_01.nii.gz --inindex=1 --method=jac --datain=acq_params.txt --topup=rs_topup --out=run009 --verbose applytopup --imain=../bia6_00186_009_01.nii.gz --inindex=1 --method=jac --datain=acq_params.txt --topup=rs_topup --out=run009 --verbose
 applytopup --imain=../bia6_00186_010_01.nii.gz --inindex=1 --method=jac --datain=acq_params.txt --topup=rs_topup --out=run010 --verbose applytopup --imain=../bia6_00186_010_01.nii.gz --inindex=1 --method=jac --datain=acq_params.txt --topup=rs_topup --out=run010 --verbose
 +</code>
 +
 +If you have the scenario where the functional data was acquired with acceleration, but the PEPOLAR images were not.  You can create an additional acq_params file with a modified readout time to help prevent over correction.  You will need to divide the echospacing by the sensefactor from your BXH header of the functional run.  If your functional data and PEPOLAR images have the same sensefactor, this compensation is not needed.
 +
 +<code>readout = ((echospacing/sensefactor) * (acquisitionmatrix[0] * (percentsampling/100))) / 1e6 
 +echospacing in the BXH header is in microseconds
 </code> </code>
  
Line 88: Line 110:
 ==== Create your acq_params.txt file === ==== Create your acq_params.txt file ===
  
-the readout time in seconds for the parameter file will be: +calculate your readout time from above
-<code>readout = (echospacing * (acquisitionmatrix[0] * (percentsampling/100))) / 1e6  +
- +
-echospacing in BXH header is in microseconds +
-</code>+
  
 the regular B0s will get the "1" and the reverse phase B0s will get the "-1" the regular B0s will get the "1" and the reverse phase B0s will get the "-1"
Line 181: Line 199:
 [[https://mrtrix.readthedocs.io/en/latest/|mrtrix3]] has a nice wrapper for FSL's eddy/topup/apply_topup that can do the above corrections and along with eddy corrections [[https://mrtrix.readthedocs.io/en/latest/|mrtrix3]] has a nice wrapper for FSL's eddy/topup/apply_topup that can do the above corrections and along with eddy corrections
  
-==== Calculate your readout time ==== +If you are running dwidenoise, do it BEFORE dwipreproc. 
-<code>readout = (echospacing * (acquisitionmatrix[0] * (percentsampling/100))) / 1e6 +
  
-echospacing in BXH header is in microseconds +==== Calculate your readout time as mentioned above ====
-</code>+
  
 ==== Prepare your input datasets ==== ==== Prepare your input datasets ====
  
 there are 2 scenarios that typically apply here there are 2 scenarios that typically apply here
-1) a short acquisition with RPE B0s +1) DWI and a short acquisition with RPE B0s 
-2) an entire acquisition with the same gradient table and reverse phase encoding +2) entire acquisitions with the same gradient table and reverse phase encoding 
  
 In both scenarios it is important to create your data with normal phase encoding direction first, followed by reversed. In both scenarios it is important to create your data with normal phase encoding direction first, followed by reversed.
Line 198: Line 214:
  
 ==== Prepare your input datasets ==== ==== Prepare your input datasets ====
 +
 +Specify that a set of images (typically b=0 volumes) will be provided for use in inhomogeneity field estimation only
  
 For scenario 1, create your blip up / blip down B0 data the same way as above. For scenario 1, create your blip up / blip down B0 data the same way as above.
Line 204: Line 222:
 bxhselect --timeselect 0 bia6_00197_013.bxh bd bxhselect --timeselect 0 bia6_00197_013.bxh bd
 fslmerge -t bud bu.nii.gz bd.nii.gz fslmerge -t bud bu.nii.gz bd.nii.gz
 +rm bu.* bd.*
 </code> </code>
  
Line 220: Line 239:
 #put THOSE back into the mif header #put THOSE back into the mif header
 mrconvert -grad grads.b dwi.mif dwi.mif -force mrconvert -grad grads.b dwi.mif dwi.mif -force
 +
 </code> </code>
  
-The last step seems redundant, but there is an issue with how mrtrix3 tools are handling the multi-shell GE data produced on our scanners.  If you data is NOT multi-shell, then you don't need it.  If your data IS multi-shell, then putting it back in can workaround other issues until their RC4 code is released.  +The last step seems redundant, but there is an issue with how mrtrix3 tools are handling the multi-shell GE data produced on our scanners.  If you data is NOT multi-shell, then you don't need it.  If your data IS multi-shell, then putting it back in can workaround other issues until their RC4 code is released.  [[https://github.com/MRtrix3/mrtrix3/issues/1487|discussion here]]
  
-===== Run dwipreproc -rpe_pair =====+==== Run dwipreproc -rpe_pair ====
  
 Run [[https://mrtrix.readthedocs.io/en/latest/reference/scripts/dwipreproc.html|dwipreproc]] with the "-rpe_pair" option Run [[https://mrtrix.readthedocs.io/en/latest/reference/scripts/dwipreproc.html|dwipreproc]] with the "-rpe_pair" option
  
 <code> <code>
-dwipreproc dwi.mif dwi_corr.mif -rpe_pair -se_epi bud.nii.gz -pe_dir AP -readout_time 0.10656  -debug+dwifslpreproc dwi.mif dwi_corr.mif -rpe_pair -se_epi bud.nii.gz -pe_dir AP -readout_time 0.10656  -debug
  
 -rpe_pair specifies you're providing a pair of B0s ( regular, reversed ) -rpe_pair specifies you're providing a pair of B0s ( regular, reversed )
Line 246: Line 266:
 ===== Scenario 2 ===== ===== Scenario 2 =====
  
-You have an entire acquisition with the same gradient table as your DWI sequence, but with reverse phase encoding.+You have an entire acquisition with the same gradient table as your DWI sequence, but with reverse phase encoding.  This information will be used to perform a recombination of image volumes (each pair of volumes with the same b-vector but different phase encoding directions will be combined together into a single volume).
  
 Calculate the readout time in the same way as above Calculate the readout time in the same way as above
Line 256: Line 276:
 <code> <code>
 #concat the 2 series ( regular, reversed )  #concat the 2 series ( regular, reversed ) 
-bxh_concat bia6_00260_007_LAS.bxh bia6_00260_008_LAS.bxh both+bxh_concat bia6_00260_00 
 +7_LAS.bxh bia6_00260_008_LAS.bxh both
  
 #extract the gradients #extract the gradients
-extractdiffdirs --fsl both bvecs bvals+extractdiffdirs --fsl both.bxh bvecs bvals
  
 #convert to mif #convert to mif
Line 281: Line 302:
 dwipreproc dwi.mif dwi_corr.mif -rpe_all -pe_dir AP -readout_time 0.10656 -debug dwipreproc dwi.mif dwi_corr.mif -rpe_all -pe_dir AP -readout_time 0.10656 -debug
  
--rpe_all signals that you've replicated ALL the directions with a rpe acquisition +- rpe_all signals that you've replicated ALL the directions with a rpe acquisition 
--pe_dir is the phase encode direction of your regular acquisition +- pe_dir is the phase encode direction of your regular acquisition 
--readout_time from above  +- readout_time from above  
 </code> </code>
  
 +
 +{{ :biac:analysis:trace_raw_corr.png?800 |}}
  
biac/analysis/topup_correction.1550777365.txt.gz · Last modified: 2019/02/21 19:29 by cmp12