We have seen surface placement issues with FreeSurfer 7.X on HCP data as well, which is why we’ve continued to recommend folks use FreeSurfer 6.X with the HCP Pipelines for now. Overall, we’ve found that getting the surface placement right is often rather finicky and FreeSurfer version dependent and has in the past required either our developer effort or FreeSurfer developer effort or both. I have several ideas on how this could be made more robust, but it may be that mris_make_surfaces is not really set up to do things of that sort.

Matt.

From: <freesurfer-bounces@nmr.mgh.harvard.edu> on behalf of Fredrik Magnussen <fredrik.magnussen@psykologi.uio.no>
Reply-To: Freesurfer support list <freesurfer@nmr.mgh.harvard.edu>
Date: Thursday, June 24, 2021 at 4:49 AM
To: "freesurfer@nmr.mgh.harvard.edu" <freesurfer@nmr.mgh.harvard.edu>
Subject: [Freesurfer] Differences in FLAIR assisted pial segmentation from FS6.0 to FS7.1

External Email - Use Caution

Dear FreeSurfer experts,

We have processed UKB data with FLAIR assisted pial segmentation using FS7.1.

The results differs quite a lot from using FLAIR assisted pial segmentation in FS6.0.

For details please see the reported issue on the freesurfer github page: MailScanner has detected a possible fraud attempt from "secure-web.cisco.com" claiming to be https://github.com/freesurfer/freesurfer/issues/849. Might be related to another issue reported here (though this is T2w assisted pial segmentation): MailScanner has detected a possible fraud attempt from "secure-web.cisco.com" claiming to be https://github.com/freesurfer/freesurfer/issues/747.

The FS pial segmentation for UKB data is prone to include dura if only T1w data is used, so assisting with FLAIR is quite detrimental.

Best regards,
Fredrik Magnussen

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.