External Email - Use Caution        

Hello FreeSurfer developers,

(This issue is described in detail at the following link: 
https://secure-web.cisco.com/19gHm_kiBwLabZG0kSzLCkZdl3RRluMPmh3eOd0r3KCWXL273Kn7fEc-N8AIruNQCFaa4FeUE3ZzCv9GRT9eapfdqdhBIXBD688oDf9L7UXDgj6WTAg5oSqlc-Q6R2Xs_APdj5bKMstfeyrHZL8AquLD4tbGuq1VDfdMB37DFs2UNZJl4oRVydgMTbV-hLDdyHykNfJtOzkgPIduXxJnJ0wXSrZ3vmmFzEfMYJHBr5MnteoVaZ83aKFB5cl_bBcWFhc6_sq2xIWJ84rBPPE467_lQfTEsbH9C-suq2aWYEA6JGtrFazCRlXu-mZ0OgjG4JWk9PBKdvDSEizrL9DT84A/https%3A%2F%2Fneurostars.org%2Ft%2Ffreesurfer-qcache-outputs-empty%2F24677)

I am preparing a surface-based morphometry analysis. I ran recon-all v7.3.2 
with qcache enabled. It completes without error and I do see the output files 
in fsaverage space at the various smoothing kernels, as expected. However, the 
fsaverage space smooth files appear to be empty, based upon trying to load 
their data with the Python package Nibabel. Some other notes:

1) When I load the QCACHE files, there are no errors in loading the file, but 
the data array returned is empty, so the files appear to be properly formatted 
morphological files.
2) When I load the native space thickness file (e.g. surf/lh.thickness), I get 
the expected full output with all data there, so I doubt it is a Nibabel issue.
3) This happens for all subjects, measurement types (e.g. area, volume, etc) 
and smoothing kernels.
4) All qcache outputs are the same file size (668.6 kb), which doesn’t seem 
like it should be right.

I am planning on running models on the data outside of Freesurfer since I have 
to deal with complex tasks such as site harmonization and general additive 
modeling, which is why I cannot proceed using the typical mris_preproc method.

Please let me know if I can provide any other helpful information in addressing 
this.

Best,
Steven

_______________________________________________
Freesurfer mailing list
Freesurfer@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 Mass General Brigham 
Compliance HelpLine at https://www.massgeneralbrigham.org/complianceline 
<https://www.massgeneralbrigham.org/complianceline> .
Please note that this e-mail is not secure (encrypted).  If you do not wish to 
continue communication over unencrypted e-mail, please notify the sender of 
this message immediately.  Continuing to send or respond to e-mail after 
receiving this message means you understand and accept this risk and wish to 
continue to communicate over unencrypted e-mail. 

Reply via email to