Freesurfer

freesurfer@nmr.mgh.harvard.edu

15 participants
30097 discussions

trac-all inquiry
by David Soto 02 Aug '13

02 Aug '13

Hi, I have successfully run recon-all in my dataset and now am attempting to use trac-all on my diffusion data obtained on a Siemens scanner. Diffusion dicoms were transformed to .nii using MRIConverter and then to .mnc using nii2mnc output.nii output_t.mnc. I am trying to run trac-all on a single subject and for this I have created the configuration file attached (tracula02ST) As you can see the SUBJECTS_DIR is /home/dsoto/Documents/fmri/rsdtianawmgui and within each subject the T1 serving as input for recon-all are in mri/orig while the diffusion images are in a folder call diffdata (named output_t.mnc) which also contains the bvecs and bvals files, which were transposed and organised according to the tutorial (named as bvecs_t.txt and bvals_t.txt) When I run: trac-all -c tracula02ST.txt I get: ERROR: no analysis step (-{prep,bedp,path}) has been selected THEN I run: trac-all -prep -bedp -path -c tracula02ST.txt which runs for 5 seconds or so and then gives the long output text below with an error message. Segmentation fault (core dumped) foreach: No match. The trac-all.log is attached also. Could you please help? Cheers David -- http://www1.imperial.ac.uk/medicine/people/d.soto/ wmen-dsoto3:~/Documents/fmri/rsdtianawmgui> trac-all -prep -bedp -path -c tracula02ST.txt INFO: SUBJECTS_DIR is /home/dsoto/Documents/fmri/rsdtianawmgui INFO: Diffusion root is /home/dsoto/Documents/fmri/rsdtianawmgui Actual FREESURFER_HOME /usr/local/freesurfer trac-paths -c /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/scripts/dmrirc.local -log /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/scripts/trac-all.log -cmd /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/scripts/trac-all.cmd #------------------------------------- /usr/local/freesurfer/bin/trac-paths #------------------------------------- #@# Path reconstruction Fri Aug 2 09:44:20 BST 2013 /usr/local/freesurfer/bin/dmri_paths --outdir /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dpath/lh.cst_AS_avg33_mni_bbr /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dpath/rh.cst_AS_avg33_mni_bbr /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dpath/lh.ilf_AS_avg33_mni_bbr /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dpath/rh.ilf_AS_avg33_mni_bbr /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dpath/lh.unc_AS_avg33_mni_bbr /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dpath/rh.unc_AS_avg33_mni_bbr /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dpath/fmajor_PP_avg33_mni_bbr /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dpath/fminor_PP_avg33_mni_bbr /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dpath/lh.atr_PP_avg33_mni_bbr /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dpath/rh.atr_PP_avg33_mni_bbr /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dpath/lh.ccg_PP_avg33_mni_bbr /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dpath/rh.ccg_PP_avg33_mni_bbr /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dpath/lh.cab_PP_avg33_mni_bbr /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dpath/rh.cab_PP_avg33_mni_bbr /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dpath/lh.slfp_PP_avg33_mni_bbr /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dpath/rh.slfp_PP_avg33_mni_bbr /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dpath/lh.slft_PP_avg33_mni_bbr /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dpath/rh.slft_PP_avg33_mni_bbr --dwi /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dmri/dwi.nii.gz --grad /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dmri/bvecs --bval /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dmri/bvals --mask /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/diff/lowb_brain_mask.nii.gz --bpdir /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dmri.bedpostX --ntr 2 --fmin 0.05 --roi1 /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.cst_AS_avg33_mni_bbr_end1_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.cst_AS_avg33_mni_bbr_end1_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.ilf_AS_avg33_mni_bbr_end1_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.ilf_AS_avg33_mni_bbr_end1_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.unc_AS_avg33_mni_bbr_end1_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.unc_AS_avg33_mni_bbr_end1_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/fmajor_PP_avg33_mni_bbr_end1_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/fminor_PP_avg33_mni_bbr_end1_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.atr_PP_avg33_mni_bbr_end1_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.atr_PP_avg33_mni_bbr_end1_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.ccg_PP_avg33_mni_bbr_end1_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.ccg_PP_avg33_mni_bbr_end1_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.cab_PP_avg33_mni_bbr_end1_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.cab_PP_avg33_mni_bbr_end1_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.slfp_PP_avg33_mni_bbr_end1_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.slfp_PP_avg33_mni_bbr_end1_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.slft_PP_avg33_mni_bbr_end1_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.slft_PP_avg33_mni_bbr_end1_dil.nii.gz --roi2 /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.cst_AS_avg33_mni_bbr_end2_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.cst_AS_avg33_mni_bbr_end2_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.ilf_AS_avg33_mni_bbr_end2_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.ilf_AS_avg33_mni_bbr_end2_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.unc_AS_avg33_mni_bbr_end2_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.unc_AS_avg33_mni_bbr_end2_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/fmajor_PP_avg33_mni_bbr_end2_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/fminor_PP_avg33_mni_bbr_end2_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.atr_PP_avg33_mni_bbr_end2_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.atr_PP_avg33_mni_bbr_end2_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.ccg_PP_avg33_mni_bbr_end2_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.ccg_PP_avg33_mni_bbr_end2_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.cab_PP_avg33_mni_bbr_end2_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.cab_PP_avg33_mni_bbr_end2_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.slfp_PP_avg33_mni_bbr_end2_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.slfp_PP_avg33_mni_bbr_end2_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.slft_PP_avg33_mni_bbr_end2_dil.nii.gz /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.slft_PP_avg33_mni_bbr_end2_dil.nii.gz --reg /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dmri/xfms/diff2mni.bbr.mat --init /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/diff/lh.cst_AS_avg33_mni_bbr_cpts_5.txt /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/diff/rh.cst_AS_avg33_mni_bbr_cpts_5.txt /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/diff/lh.ilf_AS_avg33_mni_bbr_cpts_5.txt /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/diff/rh.ilf_AS_avg33_mni_bbr_cpts_5.txt /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/diff/lh.unc_AS_avg33_mni_bbr_cpts_5.txt /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/diff/rh.unc_AS_avg33_mni_bbr_cpts_5.txt /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/diff/fmajor_PP_avg33_mni_bbr_cpts_5.txt /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/diff/fminor_PP_avg33_mni_bbr_cpts_5.txt /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/diff/lh.atr_PP_avg33_mni_bbr_cpts_5.txt /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/diff/rh.atr_PP_avg33_mni_bbr_cpts_5.txt /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/diff/lh.ccg_PP_avg33_mni_bbr_cpts_5.txt /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/diff/rh.ccg_PP_avg33_mni_bbr_cpts_5.txt /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/diff/lh.cab_PP_avg33_mni_bbr_cpts_5.txt /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/diff/rh.cab_PP_avg33_mni_bbr_cpts_5.txt /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/diff/lh.slfp_PP_avg33_mni_bbr_cpts_5.txt /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/diff/rh.slfp_PP_avg33_mni_bbr_cpts_5.txt /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/diff/lh.slft_PP_avg33_mni_bbr_cpts_5.txt /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/diff/rh.slft_PP_avg33_mni_bbr_cpts_5.txt --nprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.cst_AS_avg33_mni_bbr_fsnnprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.cst_AS_avg33_mni_bbr_fsnnids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.cst_AS_avg33_mni_bbr_fsnnprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.cst_AS_avg33_mni_bbr_fsnnids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.ilf_AS_avg33_mni_bbr_fsnnprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.ilf_AS_avg33_mni_bbr_fsnnids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.ilf_AS_avg33_mni_bbr_fsnnprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.ilf_AS_avg33_mni_bbr_fsnnids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.unc_AS_avg33_mni_bbr_fsnnprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.unc_AS_avg33_mni_bbr_fsnnids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.unc_AS_avg33_mni_bbr_fsnnprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.unc_AS_avg33_mni_bbr_fsnnids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/fmajor_PP_avg33_mni_bbr_fsnnprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/fmajor_PP_avg33_mni_bbr_fsnnids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/fminor_PP_avg33_mni_bbr_fsnnprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/fminor_PP_avg33_mni_bbr_fsnnids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.atr_PP_avg33_mni_bbr_fsnnprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.atr_PP_avg33_mni_bbr_fsnnids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.atr_PP_avg33_mni_bbr_fsnnprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.atr_PP_avg33_mni_bbr_fsnnids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.ccg_PP_avg33_mni_bbr_fsnnprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.ccg_PP_avg33_mni_bbr_fsnnids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.ccg_PP_avg33_mni_bbr_fsnnprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.ccg_PP_avg33_mni_bbr_fsnnids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.cab_PP_avg33_mni_bbr_fsnnprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.cab_PP_avg33_mni_bbr_fsnnids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.cab_PP_avg33_mni_bbr_fsnnprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.cab_PP_avg33_mni_bbr_fsnnids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.slfp_PP_avg33_mni_bbr_fsnnprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.slfp_PP_avg33_mni_bbr_fsnnids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.slfp_PP_avg33_mni_bbr_fsnnprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.slfp_PP_avg33_mni_bbr_fsnnids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.slft_PP_avg33_mni_bbr_fsnnprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.slft_PP_avg33_mni_bbr_fsnnids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.slft_PP_avg33_mni_bbr_fsnnprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.slft_PP_avg33_mni_bbr_fsnnids --lprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.cst_AS_avg33_mni_bbr_fsprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.cst_AS_avg33_mni_bbr_fsids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.cst_AS_avg33_mni_bbr_fsprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.cst_AS_avg33_mni_bbr_fsids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.ilf_AS_avg33_mni_bbr_fsprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.ilf_AS_avg33_mni_bbr_fsids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.ilf_AS_avg33_mni_bbr_fsprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.ilf_AS_avg33_mni_bbr_fsids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.unc_AS_avg33_mni_bbr_fsprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.unc_AS_avg33_mni_bbr_fsids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.unc_AS_avg33_mni_bbr_fsprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.unc_AS_avg33_mni_bbr_fsids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/fmajor_PP_avg33_mni_bbr_fsprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/fmajor_PP_avg33_mni_bbr_fsids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/fminor_PP_avg33_mni_bbr_fsprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/fminor_PP_avg33_mni_bbr_fsids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.atr_PP_avg33_mni_bbr_fsprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.atr_PP_avg33_mni_bbr_fsids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.atr_PP_avg33_mni_bbr_fsprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.atr_PP_avg33_mni_bbr_fsids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.ccg_PP_avg33_mni_bbr_fsprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.ccg_PP_avg33_mni_bbr_fsids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.ccg_PP_avg33_mni_bbr_fsprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.ccg_PP_avg33_mni_bbr_fsids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.cab_PP_avg33_mni_bbr_fsprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.cab_PP_avg33_mni_bbr_fsids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.cab_PP_avg33_mni_bbr_fsprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.cab_PP_avg33_mni_bbr_fsids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.slfp_PP_avg33_mni_bbr_fsprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.slfp_PP_avg33_mni_bbr_fsids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.slfp_PP_avg33_mni_bbr_fsprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.slfp_PP_avg33_mni_bbr_fsids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.slft_PP_avg33_mni_bbr_fsprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/lh.slft_PP_avg33_mni_bbr_fsids /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.slft_PP_avg33_mni_bbr_fsprior /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/rh.slft_PP_avg33_mni_bbr_fsids --seg /home/dsoto/Documents/fmri/rsdtianawmgui/02ST/dlabel/mni/aparc+aseg.nii.gz --nb 200 --ns 7500 --nu 0 --nk 5 Segmentation fault (core dumped) foreach: No match. wmen-dsoto3:~/Documents/fmri/rsdtianawmgui>

3 3

Alternative methods of controlling for grey matter exclusion
by Gonzalo Iribarne 02 Aug '13

02 Aug '13

Hello Freesurfer Experts, I am attaching snapshots of problem areas I continue to work with in reconstructing surfaces from children T1 weighted scans. In several different participants, movement is often a factor in creating striated movement artifacts along the outer edge of cortex. I have previously edited white matter and added control points that have sufficiently moved the pial surface, but there are several occasions where "white" high intensity voxels appear outside grey matter surfaces, yet visually seem too close to the edge to designate as white matter with control points/wm edits. In other instances, there are several areas excluded from grey matter boundaries that have no "white matter" voxels near enough to help extend the surface. Can bias field/normalization be used in making corrections for excluded grey matter/noisy high intensity voxels? Thank you in advance, Gonzalo Iribarne [image: Inline image 2][image: Inline image 3][image: Inline image 1]

1 0

Re: [Freesurfer] [tracula] error running trac-all -prep
by Borsodi Florian 02 Aug '13

02 Aug '13

Hi Anastasia Thank you for your answer. Yes, those files exist. I also extracted the bvec an bval files with anotther software then dcm2nii and i keep getting the same kind of error. Also, about the 6 diffusion direction, those data i sent you, are just testdata for running tracula. sincerely Florian >>> Anastasia Yendiki 02.08.13 0.41 Uhr >>> Hi Florian - Do these files exist? /data/physics/florian/nii/1020000485074_20080319/dmri/dwi_orig.mghdti.bvecs /data/physics/florian/nii/1020000485074_20080319/dmri/dwi_orig.mghdti.bvals The format of the bvecs and bvals that you sent seems fine, but (and this has nothing to do with the error you're getting) I have to warn you that you may not be able to get good results running probabilistic tractography on this data. It looks like you're acquiring the same 6 diffusion directions, repeated 8 times. Six directions is the absolute minimum for reconstructing the tensor model, but will probably not be sufficient for the crossing fiber model that bedpostx reconstructs (and is used by tracula). Your scan time is better spent acquiring 48 different directions, rather than the same 6 directions 8 times. a.y On Mon, 29 Jul 2013, Borsodi Florian wrote: > Hello, > > I have been trying to run tracula on my data and i keep getting the same > kind of error repeatedly. > For my imput I am using dicoms from a Siemens scanner with a stadard > diffusion protocol. However, tracula cannot read the bvec and bval data out > of the dicom header. Therefore, I implemented bvec and bval files into the > config file. > After doing so, I got the error which says that tracula cannot find the > "dwi_orig_flip.mghdti.bvecs" and "dwi_orig_flip.mghdti.bvals" files. > I have tried many options, but still cannot find a solution. > I am hoping to get some troubleshooting help. > > I have atteched my log- and config- files, as well as my bvec and bval > files. > To uphold patient confidentiality, I have encode the name patient's data as > "AAAAAA". > > I believe the problems are the bvec and bval files or their structures. The > log-file lete me assume this, especially the lines 202 - 205, 264 - 268 and > 1480 - 1484. > > Thank you in advance for your help, and your speedy response. > > With kind regards, > > Florian Borsodi > Department of Neurology > Medical University of Graz > > The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail.

2 1

GLUT: Fatal Error
by Amy Bilderbeck 02 Aug '13

02 Aug '13

I'm getting started on my first Freesurfer project (previously using SPM and FSL only). I'm working via the jalapeno cluster at FMRIB (University of Oxford) which runs, I believe, the latest version of FreeSurfer. I've run into a number of early problems, including whilst working on the tutorial data. I will describe what I hope is a basic problem. I cannot get tkmedit to work, and see the error message GLUT: Fatal Error in tkmedit.bin: OpenGL GLX extension not supported by display: :7.0 (my display number for my VNC connection is 7) I have, I think, launched FreeSurfer correctly in the terminal before running the tkmedit command, using either . $FREESURFER_HOME/SetUpFreeSurfer.sh SUBJECTS_DIRecho SUBJECTS Or tcsh source . $FREESURFER_HOME/SetUpFreeSurfer.csh setenv SUBJECTS_DIR $TUTORIAL_DATA/buckner_data/tutorial_subjs So, I can see previous threads suggesting I have not launched FreeSurfer correctly but I suspect FreeSurfer is indeed launched, or perhaps because I need to be using X11/xming. But of course I am unsure. Any tips? Dr. Amy Bilderbeck University of Oxford, Dept of Psychiatry Warneford Hospital, OX3 7JX

2 1

Re: [Freesurfer] optseq2
by Douglas Greve 01 Aug '13

01 Aug '13

On 8/1/13 8:03 PM, Claire Wilcox wrote: > Thanks much! Good to know:). > > Can you clarify the second option? Do you mean just specify one event, and then change the name to one of four possibilities (low cs, low us, high cs, high us)? That prob wouldn't work as we would love to optimize contrast bw low and high cs/us. Yes, this is what I mean. :( > > We actually also want to keep the cs and us separate (and jitter time between) so that we can look at activation associated with cs separate from us, so sadly your first idea won't work either. > > Sent from my iPhone > > On Aug 1, 2013, at 5:35 PM, Douglas Greve <greve(a)nmr.mgh.harvard.edu> wrote: > >> Hi Claire, you can't do this type of design in optseq because optseq >> requires that there be no constraints of which stimulus can follow >> itself or another stimulus (obviously this does not work for your >> design). If you take a CS-US pair as a stimulus, then that should work. >> Also, you could spec just one condition and randomly recode stimuli as >> CS and US. It is not perfect, but you'd get the random timing, and it is >> probably good enough. >> >> doug >> >> >> On 8/1/13 6:44 PM, Claire Wilcox wrote: >>> hello, >>> i'm struggling with how to specify a schedule and then ask optseq2 to identify an optimal timing schedule. specifically i have a conditioned cue and an unconditioned stimulus. the high threat CS always needs to follow with a high pain US and low threat CS with a low pain CS. how can i specify such a schedule in optseq2? i've been trying a number of combinations of below, but am failing miserably with lots of varying warnings and error messages and inability to read files or 'Bus error' >>> >>> what should the --in input schedule file format look like? that might be the missing link .. although that's hard to say for sure. >>> >>> many thanks, >>> claire >>> >>> >>> >>> _______________________________________________ >>> Freesurfer mailing list >>> Freesurfer(a)nmr.mgh.harvard.edu >>> https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer >> _______________________________________________ >> Freesurfer mailing list >> Freesurfer(a)nmr.mgh.harvard.edu >> https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer >> >> >> The information in this e-mail is intended only for the person to whom it is >> addressed. If you believe this e-mail was sent to you in error and the e-mail >> contains patient information, please contact the Partners Compliance HelpLine at >> http://www.partners.org/complianceline . If the e-mail was sent to you in error >> but does not contain patient information, please contact the sender and properly >> dispose of the e-mail. >> >

1 0

wmparc.mgz
by Pedro Rosa 01 Aug '13

01 Aug '13

Hi, Is it possible to obtain the wmparc.mgz file without running all steps from autorecon2 and 3? Thanks, Pedro.

2 1

[tracula] error running trac-all -prep
by Borsodi Florian 01 Aug '13

01 Aug '13

Hello, I have been trying to run tracula on my data and i keep getting the same kind of error repeatedly. For my imput I am using dicoms from a Siemens scanner with a stadard diffusion protocol. However, tracula cannot read the bvec and bval data out of the dicom header. Therefore, I implemented bvec and bval files into the config file. After doing so, I got the error which says that tracula cannot find the "dwi_orig_flip.mghdti.bvecs" and "dwi_orig_flip.mghdti.bvals" files. I have tried many options, but still cannot find a solution. I am hoping to get some troubleshooting help. I have atteched my log- and config- files, as well as my bvec and bval files. To uphold patient confidentiality, I have encode the name patient's data as "AAAAAA". I believe the problems are the bvec and bval files or their structures. The log-file lete me assume this, especially the lines 202 - 205, 264 - 268 and 1480 - 1484. Thank you in advance for your help, and your speedy response. With kind regards, Florian Borsodi Department of Neurology Medical University of Graz

3 2

white matter surface crosses over pial surface
by Maia Pujara 01 Aug '13

01 Aug '13

Hi, I recently came across a subject whose white matter surface cuts through the pial surface for about 10 slices bilaterally (see attached screenshot). I think it may be a problem with the white matter mask, but I'm not sure. Are there any recommendations for troubleshooting this particular problem? Thank you, Maia

2 1

Can I include this pre- vs. post- patient dataset?
by Qi Wu 01 Aug '13

01 Aug '13

Hi Freesurfer experts, I have a difficult decision to make and I don't know which direction is better. Your opinions are needed. We are planning a paper on the treatment effects of a drug on the cortical plasticity in a group of patients ( the pre- vs. post- design). It has been a huge challenge to recruit patients for this subject. So far, after 3 years of active recruitment, we have only 13 complete set of pre- vs. post- data. But , we have another set of data which was collected at the earliest stage of the project with slightly different parameters. The main difference is the in-plane resolution; those 13 patients have a 1mm*1mm*1mm isovoxel resolution and that particular patients has a 1mm*0.86mm*0.86mm resolution. To include the subject increases the power of the pre- vs. post analysis, as we are working in the range of relatively low S/N (only 13 pairs). We also know that we are open to attack if we include the subject with different scan parameters. Anyone knows how big the impact would be. Is there anyway to estimate the impact? Is it easy to get away with the potential critique about this issue? Is it a must-not case? Many thanks Keith Postdoc fellow Toronto Western Hospital Canada

2 2

TR,TE,TI,FA variability w/ mri_ca_train
by Mark Plantz 01 Aug '13

01 Aug '13

Hello freesurfers, I currently have a series of images with various TR,TE,TI,FA values. I would like to use mri_ca_train to create a .gca atlas based on these segmented volumes. Unfortunately, they all have slightly different control parameters (TR,TE,TI,FA). Is there any way around this problem, or would it be best to break the subjects into multiple groups with the same control parameters? Here are the various parameters: [each row is a subject] *TR* *TE* *TI* *flip angle* 9.38 3.86 450 12 9.34 3.86 450 12 9.38 3.86 450 12 9.38 3.86 450 12 9.34 3.86 450 12 9.44 3.87 450 12 9.39 3.86 450 12 2065.98 7.61 886.92 90 9.45 3.89 450 12 9.41 3.87 450 12 9.41 3.87 450 12 9.42 3.91 450 12 9.38 3.86 450 12 9.38 3.86 450 12 9.44 3.86 450 12 9.44 3.86 450 12 9.38 3.86 450 12 9.38 3.86 450 12 9.38 3.86 450 12 9.34 3.86 450 12 9.34 3.86 450 12 9.39 3.86 450 12 1900 2.6 900 9 1900 2.6 900 9 1900 2.6 900 9 9.41 3.87 450 12 9.41 3.87 450 12 9.41 3.87 450 12 1900 2.6 900 9 9.41 3.87 450 12 1900 2.6 900 9 1900 2.6 900 9 Thank you in advance. -Mark

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Freesurfer