Hi Stephen and Mark,

I recently had time to look into this again and I have some questions and observations about various TBSS steps that may have resulted in my original finding of slight differences in the ROI values of deprojected atlas-defined segmentations of the template skeleton that seem to be linked to which subset of subjects are processed together with TBSS. I am using the -T flag in stages 2 and 3. I believe the post here: https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind1411&L=FSL&F=&S=&P=274836 is a related thread. Files that do not appear to depend on the subset are the raw data (of course), the warp file (i.e. subj_ID_FA_to_target.mat), and the FA/target (when template is used). I'm mainly wondering about tbss_skeleton, which is called in various processing stages of TBSS after stages 2 and 3 (i.e. tbss_4_prestats, tbss_deproject). tbss_skeleton looks like it takes files as inputs that depend on the subset being processed i.e. mean_FA, mean_FA_mask, and all_FA (line references refer to FSL Release 4.0):

tbss_4_prestats, line 99: ${FSLDIR}/bin/tbss_skeleton -i mean_FA -p $thresh mean_FA_skeleton_mask_dst ${FSLDIR}/data/standard/LowerCingulum_1mm all_FA all_FA_skeletonised 

tbss_deproject, line 94: $FSLDIR/bin/tbss_skeleton -i mean_FA -p `cat thresh.txt` mean_FA_skeleton_mask_dst $FSLDIR/data/standard/LowerCingulum_1mm all_FA ${IN}_tmp -D $IN

In the case of stage 4, inspecting the frames of all_FA_skeletonised corresponding to the same subject across subsets, they are identical wherever there is data for both. However, they look as if they are filling different FA skeletons with the trend that the more subjects processed together the less voxels in the skeleton, presumably because the more subjects that are processed together the higher likelihood for the inclusion of a subject without data for a given voxel and thus a larger mask applied to all_FA and mean FA at the end of stage 3 when the -T flag is used (lines 192 and 194). This observation would agree with Mark's response that images are masked so that each voxel has data in every single subject.

In the case of tbss_deproject, after the first stage of the deprojection (<atlas>_to_all_FA) again comparing frames corresponding to the same subject across subsets, the skeletons differ following the same trend as observed for stage 4. This intermediate step of deprojection that appears linked to the subset being processed would seem to explain the discrepancy in ROI values ultimately extracted from regions of a deprojected (to native space) region of the template skeleton. Stephen mentioned that mean_FA should be the FMRIB58_FA_1mm if the -T flag is used, but that is not what I am finding (FA/target is, however). Again, looking at tbss_3_postreg lines 192-195, it appears that when the -T flag is used the mean_FA_skeleton is replaced by the template but that the mean_FA derived from the template and all FA are still masked by subset-dependent mean_FA_mask (or am I misunderstanding stage 3 lines 183-185?) .

Also, I see a slight difference in the distance maps (mean_FA_skeleton_mask_dst) across subsets, which I would have expected to be the same since the call to distancemap doesn't appear to contain any subset-dependent files.

Do you think any of these observations explain the discrepancies I'm finding?


Thank you so much for your continued assistance!

Ben


---------- Forwarded message ----------
From: Mark Jenkinson <[log in to unmask]>
Date: Tue, Mar 11, 2014 at 3:54 AM
Subject: Re: [FSL] Troubles with TBSS and ROI values even using template option
To: [log in to unmask]


Hi,

Yes, the images are masked so that each voxel has data in every single subject.

All the best,
Mark


On 10 Mar 2014, at 13:29, Benjamin Trotter <[log in to unmask]> wrote:

Hi - The mean_FA and all_FA appear to be changing depending on the subject subset even with the -T flag (although the mean_FA skeletons are identical to each other--both are the FMRIB58 template skeleton). I sent Matthew what I could regarding the issue, will follow up here with his reply for anyone who digs up this thread in the future.  Inspecting the all_FA file, the individual subjects seem like more voxels are masked out the more subjects that are run, possibly a step to ensure all the same voxels are present for each subject in later statistical analysis? Just a guess on my part.  Thanks again for all the help!


On Thu, Mar 6, 2014 at 2:36 AM, Stephen Smith <[log in to unmask]> wrote:
Hi - if you are sure that your mean_FA is being derived from the standard space template and not (different subsets) of your study data - which should happen if you use the -T option for stages 2 and 3 - then you should get the same deprojected data for a given subject, regardless of what other subjects are in the analysis.   If you are sure this is not working right, then please send the data to Matthew to check out - see the FSL wiki for data upload instructions.

Cheers, Steve.



On 5 Mar 2014, at 18:43, Benjamin Trotter <[log in to unmask]> wrote:

Hello again, following up on my last email.  I think it better describes the specific issue I'm experiencing than the original email.  The issue remains unresolved on my end.  I am wondering if you have any insight regarding why I am finding the discrepancies in DTI measures for the same ROI in the same subject depending on what subject subset the particular subject was processed as a part of--despite the fact that, for either subset, we are deprojecting the same subject's data from the same template according to the same atlas to get the ROI values.  It seems like it should be independent from which other subjects were processed with the particular subject. As always, thanks for the assistance.


On Mon, Feb 24, 2014 at 9:30 AM, Benjamin Trotter <[log in to unmask]> wrote:
Hi - I was hoping to account for the different mean_FA skeletons resulting from running different subsets by using the template option in both tbss_2_reg and tbss_3_postreg.  If I use the -T flag for these steps, and then run the command "tbss_deproject <atlas> 2 -n", can I expect that the ROI defined by the atlas will have the same diffusion measure values regardless of the subset of subjects that was processed? This result is not what I am finding.  It is a good suggestion, to start with the full analysis, but the research project is on-going and more subjects are still being added to the study.  We hoped that by using the template and its derived skeleton that we would be able to include these new subjects in analyses as their data comes in without having to episodically re-run every subject, which as of now seems like it would only result in a (for the most part slightly) new dataset anyways. Thanks again for your assistance, hoping to get to the bottom of this.


On Sat, Feb 22, 2014 at 3:52 AM, Stephen Smith <[log in to unmask]> wrote:
Hi - if you run "full" TBSS analyses with different subsets of subjects, you will get a slightly different mean_FA and hence skeleton each time - which will then change individual subjects' results (hopefully only slightly).
Would that explain it?   I think it would be easy enough to avoid this by starting with a full analysis of all subjects, and then only rerunning sub-parts of the analysis for subsetes of the data, making sure to always base things on the same mean_FA and skeleton?

Cheers.



On 21 Feb 2014, at 17:18, Benjamin Trotter <[log in to unmask]> wrote:

Hi Stephen,

Thanks for your response, I think I need to clarify the inconsistency that's troubling me.   I believe the all_FA and warp files are all in order. My expectation is that, regardless of how many subjects are processed at once, the DTI measures for a given ROI for the same subject should not change. For example, if I process 150 subjects on one day, and then 200 subjects a different day, and then compare the value I get out for FA in a given tract for the same subject (after deprojection to that subject's native space) that the FA value will be consistent between processing-days/#subjects-processed. I'm finding that their is a discrepancy here.  Can you think of what may be causing this inconsistency?

Thanks again!


On Fri, Feb 21, 2014 at 2:17 AM, Stephen Smith <[log in to unmask]> wrote:
Hi - the output of the deprojection is dictated by various files, such as the ordering of subjects in all_FA (and the warp files from the first stage of the registration) - so you need to make sure these all match your expectations.  I can't think why there would be (eg) any inconsistency between the set of subjects inside all_FA and the outputs from the deprojection - 

Cheers



On 20 Feb 2014, at 19:50, Benjamin Trotter <[log in to unmask]> wrote:

I am running through the TBSS processing stream and am finding that after deprojection according to a segmentation atlas (tbss_deproject <atlas> 2 -n) to a subject's native space that the ROI values I get out for the DTI measures using asegstats2table change depending on how many subjects I am running at a time.  As a fix, I've tried using the template flag for both the tbss_2_reg and tbss_3_postreg steps, so that in theory the same skeleton voxels will be deprojected regardless of which subjects are run at once.  However, even using the template I am still getting differences between runs depending on which subjects I run.  It is probably useful to note that I get no differences between runs when I run the same set of subjects for each run. Has anyone else experienced this issue? I'm wondering if there are processing steps happening "behind the scenes" in TBSS that could result in these differences even if the template is used.  

The differences between runs are generally minor, with most across-run tract DTI measures being well correlated, however I would like to better understand the source of these discrepancies and whether there is anything I can change in my processing to avoid them.  

Thanks in advance for any and all assistance!


---------------------------------------------------------------------------
Stephen M. Smith, Professor of Biomedical Engineering
Associate Director,  Oxford University FMRIB Centre

FMRIB, JR Hospital, Headington, Oxford  OX3 9DU, UK
+44 (0) 1865 222726  (fax 222717)
[log in to unmask]    http://www.fmrib.ox.ac.uk/~steve
---------------------------------------------------------------------------

Stop the cultural destruction of Tibet







---------------------------------------------------------------------------
Stephen M. Smith, Professor of Biomedical Engineering
Associate Director,  Oxford University FMRIB Centre

FMRIB, JR Hospital, Headington, Oxford  OX3 9DU, UK
+44 (0) 1865 222726  (fax 222717)
[log in to unmask]    http://www.fmrib.ox.ac.uk/~steve
---------------------------------------------------------------------------

Stop the cultural destruction of Tibet








---------------------------------------------------------------------------
Stephen M. Smith, Professor of Biomedical Engineering
Associate Director,  Oxford University FMRIB Centre

FMRIB, JR Hospital, Headington, Oxford  OX3 9DU, UK
+44 (0) 1865 222726  (fax 222717)
[log in to unmask]    http://www.fmrib.ox.ac.uk/~steve
---------------------------------------------------------------------------

Stop the cultural destruction of Tibet







--
Ben Trotter
Health Science Specialist
VA Boston Healthcare System
Translational Research Center for Traumatic Brain Injury and Stress Disorders (TRACTS)




--

Ben Trotter

Health Science Specialist

VA Boston Healthcare System

Translational Research Center for Traumatic Brain Injury and Stress Disorders (TRACTS)