I ran the mcflirt program on the data, using the default middle volume as a reference, and with the sbref as a reference. Both came out fine. I'm thinking the problem lies with how FLIRT is registering each volume to the reference image, since its registering them independently of each other. How would I run the HCP motion correction using the middle timepoint instead of either the sbref or the mean of the first 10 images? -G
-----Original Message----- From: Harms, Michael [mailto:[email protected]] Sent: Wednesday, October 29, 2014 10:45 AM To: Book, Gregory; Harms, Michael; [email protected] Subject: Re: [HCP-Users] GenericfMRIVolumeProcessingPipelineBatch motion correction Matt can confirm, but I think the paddingsize option is just to give a little lee-way if the edge of the brain happens to approach the limits of the FOV. Can you try running the HCP motion correction with the middle time point of the series as the motion correction target? And conversely, run 'mcflirt' using the SBRef as the target (using the -reffile option of 'mcflirt')? thanks, -MH -- Michael Harms, Ph.D. ----------------------------------------------------------- Conte Center for the Neuroscience of Mental Disorders Washington University School of Medicine Department of Psychiatry, Box 8134 660 South Euclid Ave. Tel: 314-747-6173 St. Louis, MO 63110 Email: [email protected] On 10/29/14 9:12 AM, "Book, Gregory" <[email protected]> wrote: >Mcflirt correction looked fine. Also, running the pipeline without the >SBref image did not change anything. I noticed that a) the 'motion' in >the final timeseries is only rotation, not translation b) the rotation >appears to be constant: 1 unit of rotation in one direction, then 1 >unit in the opposite direction. > >What does the "-paddingsize 1" option do in >HCP/global/scripts/mcflirt_acc.sh? > >-Greg > > >-----Original Message----- >From: Harms, Michael [mailto:[email protected]] >Sent: Tuesday, October 28, 2014 1:28 PM >To: Book, Gregory; Harms, Michael; [email protected] >Subject: Re: [HCP-Users] GenericfMRIVolumeProcessingPipelineBatch >motion correction > > >So, what did the result from 'mcflirt' motion correction look like? >Was that well-corrected? > >I addition to running the HCP Pipeline without the SBRef (i.e., using >the first 10 frames as the motion correction target), it would be >informative to run using the middle time point as the motion correction >target (which is what 'mcflirt' is doing internally). That would help >separate whether the "improvement" is specific to using 'mcflirt', or >if it is more a function of the precise motion correction target used in this >case. > >cheers, >-MH > >-- >Michael Harms, Ph.D. > >----------------------------------------------------------- >Conte Center for the Neuroscience of Mental Disorders Washington >University School of Medicine Department of Psychiatry, Box 8134 >660 South Euclid Ave. Tel: 314-747-6173 >St. Louis, MO 63110 Email: [email protected] > > > > >On 10/28/14 12:19 PM, "Book, Gregory" <[email protected]> wrote: > >>Hi Michael, >>The animated gif has the raw timeseries >>(SubjID/unprocessed/3T/resting/analysis_3T_resting.nii.gz) on top and >>the end result of the HCP processing on the bottom >>(SubjID/MNINonLinear/Results/resting/resting.nii.gz). Some of the big >>motions are from volumes 450-600. The voxel size of the raw image is >>3x3x3 and the final resolution set in the >>GenericfMRIVolumeProcessingPipeline script is 3x3x3. >> >>I can try running it again without the sbref image and see what happens. >>-G >> >> >>-----Original Message----- >>From: Harms, Michael [mailto:[email protected]] >>Sent: Tuesday, October 28, 2014 11:40 AM >>To: Book, Gregory; Greg Burgess; Xu, Junqian >>Subject: Re: [HCP-Users] GenericfMRIVolumeProcessingPipelineBatch >>motion correction >> >> >>Hi Greg, >>I'm a little confused by what you are showing in your gif. Is the >>"original" (top) the uncorrected (raw) time series, and the "final" >>(bottom) the result following 'mcflirt' motion correction? If so, why >>is there no frontal lobe susceptibility artifact present in the bottom >>set? >> >>Or, is the top the result from 'mcflirt', and the bottom the result >>from the HCP Pipeline using the SBRef as the Scout? If that is the >>case, I think it would be informative if you could run the data >>through the HCP Pipeline, but not supply an explicit motion correction >>reference image, in which case (as Greg Burgess noted) the >>mcflirt_acc.sh script will default to using the average of the first >>10 frames as the motion correction target. >> >>Also, when you say that the SBRef looks fine, did you overlay the >>SBRef and the BOLD timeseries, and compare the two directly? >> >>cheers, >>-MH >> >>-- >>Michael Harms, Ph.D. >> >>----------------------------------------------------------- >>Conte Center for the Neuroscience of Mental Disorders Washington >>University School of Medicine Department of Psychiatry, Box 8134 >>660 South Euclid Ave. Tel: 314-747-6173 >>St. Louis, MO 63110 Email: [email protected] >> >> >> >> >>On 10/28/14 7:45 AM, "Book, Gregory" <[email protected]> wrote: >> >>>Hi Greg, >>>I ran some more subjects and I checked the resulting image for one of >>>them. This subject had 0.6mm total displacement over the 900 volumes, >>>no spikes, all smooth constant displacement through the timeseries. I >>>used mcflirt to do that registration. In this image >>>http://olinnidb.org/overlay.gif the final 4D image has motion that >>>the original, raw 4D image does not. The original image is on top, >>>the final image on the bottom. The final image moves around more than >>>the raw image, so I'm wondering if this is really an effect of motion >>>or something else in our data? Our SBRef images look fine. >>>Also does it matter that the processed image is moving. Can it still >>>be used for stats, or is this something we need to fix before >>>attempting stats? >>>-Greg >>> >>>-----Original Message----- >>>From: Greg Burgess [mailto:[email protected]] >>>Sent: Saturday, October 25, 2014 11:25 AM >>>To: Xu, Junqian >>>Cc: Book, Gregory; HCP Users >>>Subject: Re: [HCP-Users] GenericfMRIVolumeProcessingPipelineBatch >>>motion correction >>> >>>I agree with Mike and Gordon. Our best guess right now is that the >>>motion correction registration target (i.e., SBRef) is corrupted, and >>>that is affecting the efficacy of motion correction. Previous testing >>>in healthy normal adults suggested that the SBRef was the best motion >>>correction target. But, we've seen that the SBRef can be corrupted by >>>motion during the SBRef collection (immediately prior to the MB scan >>>volumes) in high motion individuals (e.g., kids, clinical populations). >>>In those cases, it's possible that a different motion correction >>>target would yield better results. >>> >>>The mcflirt_acc.sh script in the HCP pipelines allows for alternate >>>"Scout" images (like the mean image or mid-volume), or in the absence >>>of a motion correction reference image the scripts will create a >>>reference image from the average of the first 10 frames. >>> >>>Even with a good motion correction target, large motions may not be >>>completely corrected. From your image, it appears that all of the >>>other frames were adequately corrected. There was no absolute >>>displacement that was uncorrected. Only the timepoints of large >>>displacement were inadequately corrected. To salvage data of this >>>sort, you should seriously consider using frame censoring (aka >>>"scrubbing") or motion outlier regressors (a la fsl_motion_outliers) >>>in your subsequent analysis. >>> >>>--Greg >>> >>>____________________________________________________________________ >>>Greg Burgess, Ph.D. >>>Staff Scientist, Human Connectome Project Washington University >>>School of Medicine Department of Anatomy and Neurobiology >>>Phone: 314-362-7864 >>>Email: [email protected] >>> >>>On Oct 24, 2014, at 1:10 PM, Xu, Junqian <[email protected]> wrote: >>> >>>> Greg, >>>> >>>> We've observed very similar issue in our Sinai non-compliant >>>>subject data. I briefly discussed the issue with Greg Burgess at WU, >>>>which didn't lead to a conclusive solution. I think it may be >>>>worthwhile for us to put the troublesome motion correction data >>>>together and cross-check our examination methods to get to the bottom of >>>>this issue. >>>> >>>> Gordon >>>> >>>>> On Oct 24, 2014, at 9:36 AM, Book, Gregory >>>>><[email protected]> wrote: >>>>> >>>>> I processed some of our fMRI own data through the HCP pipelines >>>>>and now I'm looking at the >>>>>AnalysisDir/MNINonLinear/Results/taskname/taskname.nii.gz file. I'm >>>>>assuming this is the 4D file which should be motion corrected, >>>>>undistorted, and skull stripped. And that this file should be able >>>>>to be used directly in stats processing without any further steps? >>>>> >>>>> However, I still see significant motion when viewing the 4D file >>>>>in a cine view. The brain mask is constant, but the image under the >>>>>mask moves. Did the mcflirt step not work, or is this normal? >>>>> >>>>> The animated .gif can be seen here: >>>>>http://olinnidb.org/preview.gif The major motion occurs around volumes 150 >>>>>and 200-250. >>>>> -G >>>>> >>>>> _________________________________________________ >>>>> Gregory Book >>>>> Senior Technology Manager >>>>> Olin Neuropsychiatry Research Center, Institute of Living, >>>>> Hartford Hospital >>>>> 200 Retreat Avenue >>>>> Hartford, CT 06106 >>>>> Tel: 860-545-7267 Fax: 860-545-7797 [email protected] >>>>> http://nidb.sourceforge.net >>>>> >>>>> >>>>> This e-mail message, including any attachments, is for the sole >>>>>use of the intended recipient(s) and may contain confidential and >>>>>privileged information. Any unauthorized review, use, disclosure, >>>>>or distribution is prohibited. If you are not the intended >>>>>recipient, or an employee or agent responsible for delivering the >>>>>message to the intended recipient, please contact the sender by >>>>>reply e-mail and destroy all copies of the original message, >>>>>including any attachments. >>>>> _______________________________________________ >>>>> HCP-Users mailing list >>>>> [email protected] >>>>> http://lists.humanconnectome.org/mailman/listinfo/hcp-users >>>>> >>>> >>>> _______________________________________________ >>>> HCP-Users mailing list >>>> [email protected] >>>> http://lists.humanconnectome.org/mailman/listinfo/hcp-users >>>> >>> >>> >>>_______________________________________________ >>>HCP-Users mailing list >>>[email protected] >>>http://lists.humanconnectome.org/mailman/listinfo/hcp-users >> >> >>________________________________ >>The materials in this message are private and may contain Protected >>Healthcare Information or other information of a sensitive nature. If >>you are not the intended recipient, be advised that any unauthorized >>use, disclosure, copying or the taking of any action in reliance on >>the contents of this information is strictly prohibited. If you have >>received this email in error, please immediately notify the sender via >>telephone or return mail. >> >>This e-mail message, including any attachments, is for the sole use of >>the intended recipient(s) and may contain confidential and privileged >>information. Any unauthorized review, use, disclosure, or distribution >>is prohibited. If you are not the intended recipient, or an employee >>or agent responsible for delivering the message to the intended >>recipient, please contact the sender by reply e-mail and destroy all >>copies of the original message, including any attachments. >> >>_______________________________________________ >>HCP-Users mailing list >>[email protected] >>http://lists.humanconnectome.org/mailman/listinfo/hcp-users > > >________________________________ >The materials in this message are private and may contain Protected >Healthcare Information or other information of a sensitive nature. If >you are not the intended recipient, be advised that any unauthorized >use, disclosure, copying or the taking of any action in reliance on the >contents of this information is strictly prohibited. If you have >received this email in error, please immediately notify the sender via >telephone or return mail. > >This e-mail message, including any attachments, is for the sole use of >the intended recipient(s) and may contain confidential and privileged >information. Any unauthorized review, use, disclosure, or distribution >is prohibited. If you are not the intended recipient, or an employee or >agent responsible for delivering the message to the intended recipient, >please contact the sender by reply e-mail and destroy all copies of the >original message, including any attachments. > >_______________________________________________ >HCP-Users mailing list >[email protected] >http://lists.humanconnectome.org/mailman/listinfo/hcp-users ________________________________ The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail. This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message, including any attachments. _______________________________________________ HCP-Users mailing list [email protected] http://lists.humanconnectome.org/mailman/listinfo/hcp-users
