Hi guys!

We would like to install the latest and greatest FreeSurfer on the processing 
cluster used by the CNDA at Washington University.  We're thinking about 
installing the 5.3.0-HCP, and then over that, the released 5.3.0 patches.  
We're looking for verification that doing the install this way makes sense and 
that these two code sets don't conflict in any way.

We know that the 5.3.0-HCP version updates the mris_make_surfaces, however, the 
patches do not include that update, which is why we are thinking about starting 
with 5.3.0-HCP as the base install.  Note that this is being done on CentOS 6.x

The currently available patches seem to include:

mni152reg
mri_mcsim
mri_segstats
recon-all
tksurfer-sess
tksurferfv

Is that a complete list or did we miss some binaries/scripts?

Also, it seems that the 'patch' binaries are dynamically linked, while the 
release binaries are statically linked.  Besides dependency issues, could this 
cause an issue with results consistency, etc. if other system libraries get 
updated?

Thanks, guys.  Hope all is well.

Matt House, Jenny Gurney and John Flavin @WU in STL

________________________________

The material in this message is private and may contain Protected Healthcare 
Information (PHI). 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.
_______________________________________________
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 Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.

Reply via email to