Hi Saad,
Thanks for responding to another one of my questions. The high memory requirement occurs whether my targets are volumes or surfaces. In case it helps, the commands I used to run the volume seeds/targets are below:
probtrackx --samples=../dti.bedpostX/merged --mask=../dti.bedpostX/nodif_brain_mask --seed=vol_targets/ctx-rh-insula --dir=ctx-rh-insula_1 --forcedir --opd --os2t --s2tastext --targetmasks=vol_targets.txt --stop=subj_stop.nii.gz --xfm=../atlas/subj_free_to_dti.mat --seedref=../atlas/subj_T1.nii.gz --loopcheck --cthr=0.2 --nsteps=2000 --nsamples=5000
probtrackx2 --samples=../dti.bedpostX/merged --mask=../dti.bedpostX/nodif_brain_mask --seed=vol_targets/ctx-rh-insula --dir=ctx-rh-insula_2 --forcedir --opd --os2t --s2tastext --targetmasks=vol_targets.txt --stop=subj_stop.nii.gz --xfm=../atlas/subj_free_to_dti.mat --seedref=../atlas/subj_T1.nii.gz --loopcheck --cthr=0.2 --nsteps=2000 --nsamples=5000
Is there a mistaken in my probtrackx2 command line that could be causing the high memory usage?
-Tyler
|