External Email - Use Caution
_______________________________________________Hi Jim,I am sorry I missed your message. Are your questions still relevant?Apologies, Lilla
From: freesurfer-bounces@nmr.mgh.harvard.edu <freesurfer-bounces@nmr.mgh.harvard.edu> on behalf of James Hengenius <james.hengenius@gmail.com>
Sent: Friday, December 13, 2024 2:49 PM
To: Freesurfer support list <freesurfer@nmr.mgh.harvard.edu>
Subject: [Freesurfer] Importing surface meshes from 3rd party cortical surface reconstruction tools for analysis in fsaverage template spaceExternal Email - Use Caution
Hi,
I'm working with infant (0-30 month) MR data, and iBEAT (MailScanner has detected a possible fraud attempt from "secure-web.cisco.com" claiming to be https://www.nature.com/articles/s41596-023-00806-x) is currently doing a better job than Infant FreeSurfer (MailScanner has detected a possible fraud attempt from "secure-web.cisco.com" claiming to be https://www.sciencedirect.com/science/article/pii/S1053811920304328) at cortical surface recon in this age range. However, I have custom surface ROI atlases on the fsaverage template and would very much like to leverage FreeSurfer's stats tools to map iBEAT subject surfaces to the template and extract stats from my custom ROIs.
To do so, I need to
- Bring my iBEAT VTK surfaces (~47K vertices per hemisphere) into FreeSurfer (mris_convert?)
- Resample the meshes to FS surface resolution (~12.5K vertices per hemi)
- Compute curvature stats on the iBEAT surfaces
- Use mris_surf2surf (or equivalent) to map the resampled iBEAT surface to the fsaverage template using curvature
- Compute/extract anatomical stats from the regions equivalent to the ROIs in my template space atlas.
All of the above are presenting challenges.
So far, I tried using mris_convert to bring the VTK into FS format, but when I tried using mris_anatomical_stats, I get errors. Note that I also ran InfantFS on the data, and that I copied the converted (but not downsampled) VTK pial surface from iBEAT to $SUBJECTS_DIR/$subjid/surf/lh.ibeat.pial
> mris_anatomical_stats -log test.ibeat.log sub-0001 lh ibeat.pial
outputting results to test.ibeat.log...
reading volume /scratch/t/tpaus/jhengeni/iBEAT/surface_remapping/sub-0001/sub-0001/mri/wm.mgz...
reading input surface /scratch/t/tpaus/jhengeni/iBEAT/surface_remapping/sub-0001/sub-0001/surf/lh.ibeat.pial...
Using TH3 vertex volume calc
Total face volume 58098.7
Total vertex volume 57390.1 (mask=0)
reading input pial surface /scratch/t/tpaus/jhengeni/iBEAT/surface_remapping/sub-0001/sub-0001/surf/lh.pial...
error: mrisReadTriangleFile opened /scratch/t/tpaus/jhengeni/iBEAT/surface_remapping/sub-0001/sub-0001/surf/lh.pial okay but surface doesn't match /scratch/t/tpaus/jhengeni/iBEAT/surface_remapping/sub-0001/sub-0001/surf/lh.ibeat.pial. nvertices:46854 != mris->nvertices:12240 || nfaces:93704 != mris->nfaces:24476
error: mrisReadTriangleFile failed.
error: mris_anatomical_stats: could not read surface file /scratch/t/tpaus/jhengeni/iBEAT/surface_remapping/sub-0001/sub-0001/surf/lh.pial
It appears this approach is failing due to a difference in meshes (the iBEAT mesh is at a different resolution, with more elements, than the lh.pial from InfantFS).
Any tips for this and the other steps would be a big help!
Thanks,Jim H.--
Jim Hengenius
Research AssociatePaus Research GroupCHU Sainte-Justine Research CentreMy Google Calendar
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
MailScanner has detected a possible fraud attempt from "secure-web.cisco.com" claiming to be 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 Mass General Brigham Compliance HelpLine at MailScanner has detected a possible fraud attempt from "secure-web.cisco.com" claiming to be https://www.massgeneralbrigham.org/complianceline <MailScanner has detected a possible fraud attempt from "secure-web.cisco.com" claiming to be https://www.massgeneralbrigham.org/complianceline> .