History of DataProcessing3T (No. 4)
- History
- View the diff.
- View the diff current.
- View the source.
- Go to DataProcessing3T.
- 1 (2016-06-23 (Thu) 01:20:33)
- 2 (2016-07-01 (Fri) 03:58:22)
- 3 (2016-07-12 (Tue) 02:42:52)
- 4 (2016-08-08 (Mon) 04:28:28)
- 5 (2016-08-09 (Tue) 02:12:03)
- 6 (2016-09-02 (Fri) 08:29:49)
- 7 (2017-03-15 (Wed) 07:15:27)
- 8 (2017-03-16 (Thu) 02:56:45)
- 9 (2017-04-04 (Tue) 02:35:57)
- 10 (2017-05-12 (Fri) 11:58:59)
- 11 (2017-06-02 (Fri) 08:28:17)
- 12 (2017-06-23 (Fri) 06:53:21)
- 13 (2017-07-10 (Mon) 01:03:51)
- 14 (2017-12-18 (Mon) 06:47:48)
- 15 (2017-12-19 (Tue) 03:09:42)
- 16 (2019-02-27 (Wed) 16:04:53)
- 17 (2019-08-18 (Sun) 17:52:25)
- 18 (2020-03-18 (Wed) 15:54:30)
- 19 (2020-12-23 (Wed) 22:50:13)
- 20 (2020-12-24 (Thu) 19:20:46)
###--- Under construction ---###
Individual data processing†
>cd 0001<RET> >dcms2sdt . (-)<RET> : dicom to sdt data conversion(unifying the multiple dicom files), '-' flag is required for EPI data. (>demosaic all<RET> : decompose the mosaic format (EPI/DTI data)) >sdt2to4 all<RET> : 2-byte unsigned short to 4-byte float data conversion If you want to transfer the data to the other software, >sdt2spm all + <RET> Then NIFTI-1 format file is ready as all.nii
EPI data(fMRI data)†
start from all_dM.sdt/spr and peak.bit files You need to correct the acq.peak.bit file. >acqbitc acq.peak.bit acq.peak.new.bit 37<RET> The number, N=37, need to be adjusted to fit to your data. The acquisition pulses were recorded for individual volumes but we need to have same number of triggers as the number of acquisition(e.g. number of slices/slice sets x number of volumes). It must be equal to the number of timing recorded as mosaic_timmng. We'll put the number of additional triggers, so in N=37 case,38 triggers were prepared for each volumes after the acqbitc processing.
despike_tst all_dM<RET> Remove the slow drift and sharp spikes physiofix all_dMDs acq.peak.new.bit resp.peak.bit card.peak.bit<RET> Retrospective physiological noise removal mcafni all_dMDs<RET> Motion correction by afni. mc2dafni is also available for 2d motion correction. ssc2 all_dMDs<RET> Slice scan time correction ... (sdtt, sdtcc, sdtglm,...)
DTI data†
To make gradient table file, >dcms2gtb<RET> Then grd.txt has gradient(x,y,z) and b-value You can use this for Diffusion Toolkit(Trackvis). This procedure is likely unnecessary because Diffusion Toolkit has standard Siemens gradient setting as defaults.