Freesurfer November 2025

freesurfer@nmr.mgh.harvard.edu

32 participants
40 discussions

Postdoctoral fellowship program within the Center for Cognitive and Behavioral Brain Imaging at the Ohio State University
by Adam Gorka 06 Nov '25

06 Nov '25

External Email - Use Caution Dear Colleagues, The Center for Cognitive and Behavioral Brain Imaging (CCBBI) at the Ohio State University is pleased to announce its Postdoctoral fellowship program. CCBBI is an interdisciplinary research facility located in the Department of Psychology at The Ohio State University. In alignment with its mission to advance neuroimaging research and train the next generation of scientists, CCBBI is pleased to announce the inaugural cohort of its Postdoctoral Fellows Program. This competitive two-year fellowship provides salary and benefits (including health insurance) to outstanding early-career scientists. The program is designed as a collaborative investment between CCBBI and participating faculty mentors. Year 1 salary and benefits are fully supported by CCBBI. For Year 2, fellows are expected to continue under the sponsorship of a CCBBI Faculty Fellow. Priority will be given to applicants whose faculty mentors can provide matching funds for Year 2, though applicants without confirmed cost-match support will also be considered based on scientific merit, sponsor fit, and alignment with CCBBI’s mission. The fellowship supports scholars who wish to pursue independent research at CCBBI while contributing to the center’s dynamic and interdisciplinary scientific community at The Ohio State University. *Eligibility Criteria* - Doctoral degree in Psychology, Neuroscience, or a closely related field, earned within the past two years. For candidates who received their degree before this period, please contact CCBBI to discuss the specifics of your circumstances (ccbbi.service(a)osu.edu) - As the goal of this program is to recruit new talent to Ohio State, current graduate students or postdoctoral scholars already working at Ohio State are not eligible. - Sponsorship from CCBBI faculty who will serve as the primary mentor. CCBBI Faculty Affiliates are strongly encouraged to consider a CCBBI Faculty Fellow as a co-mentor. - Faculty cost-match for Year 2 is preferred but not required; priority will be given to mentors who can provide matching funds. - Evidence of superior academic achievement (such as honors or other academic designation, peer-reviewed publications, invited presentations). - Dedication to a research-focused career, with preference given to individuals aiming to pursue academic pathways. *Fellowship Details* The fellowship offers a competitive annual salary of $61,008 plus benefits, with funding available to begin before *August 1, 2026*. Fellows will dedicate 90% of their time to pursuing independent research within a CCBBI-affiliated lab. The remaining 10% of their time will be devoted to professional development through CCBBI activities, including engaging in community outreach, hosting distinguished invited speakers, and contributing to the center’s signature Research Day conference. Fellows will also be encouraged to attend the annual meeting for the Organization for Human Brain Mapping, and all travel costs will be covered by CCBBI. This is a two-year position, structured as follows: - Year 1: Fully funded by CCBBI - Year 2: Continued support anticipated through the sponsoring faculty mentor (cost-match preferred but not required). A progress report will be required at the end of Year 1 to evaluate research progress and confirm Year 2 funding arrangements. *Application Guidelines* Applicants should submit all required materials as a single PDF file to ccbbi.service(a)osu.edu. Letters of recommendation, including one from the faculty mentor, must be sent directly by the recommenders to ccbbi.service(a)osu.edu. All application materials, including letters of recommendation, must be received by *December 15, 2025*. Final decisions will be announced by the end of *January 2026*. 1. *Cover Letter* 2. *Curriculum Vita* 3. *Personal Statement (2-page limit)* Describe your research interests, career goals, and how the CCBBI Postdoctoral Fellowship will support your professional development. The statement should include a summary of your prior training and research experiences, your motivation for pursuing postdoctoral work at CCBBI and the sponsor’s lab, and the ways in which your research aligns with the mission of the center. 4. *Research Plan (3-page limit, with the following sections) * Applicants must submit a research statement that is no more than 3 pages (excluding references) and formatted in 11-point Arial font, single-spaced, with 0.5-inch margins. References should be included at the end and do not count toward the page limit. The research plan should include the following sections: • Aims, Significance, and Innovation (1 page) • Approach and Feasibility (2 pages) • References (no page limit) 5. *Two letters of recommendation* 6. *Nomination letter from CCBBI Faculty Mentor (and co-mentor, if applicable)* Letter should describe the expected impact of the applicant on the sponsor’s scholarly program and the likely impact on scholarship in the discipline. Please also confirm the mentor’s intent to provide matching funds for Year 2. 7. *Up to three peer-reviewed publications* Best, Adam Gorka Ph.D. Research Assistant Professor CCBBI/Psychology Department The Ohio State University

1 0

Re: T1 + DTI for thalamus segmentation
by fsbuild 06 Nov '25

06 Nov '25

External Email - Use Caution You need to install the Matlab R2019b (inside the freesurfer distribution) using the fs_install_mcr script we provide in order for freesurfer commands to reference the Matlab libmwm* libraries.  See the section SETUP A MATLAB DISTRIBUTION under the URL,https://secure-web.cisco.com/1MwJU4ffnWRIUhCWZFkXCcFIUb9Rtul3l-BDi7QFgT… R. On Nov 6, 2025, at 05:23, Antonio Di Renzo <antoniomp777(a)hotmail.it> wrote:

1 0

T1 + DTI for thalamus segmentation
by Antonio Di Renzo 06 Nov '25

06 Nov '25

External Email - Use Caution Messers Freesurfer developers, I am using the joint segmentation of thalamic nuclei from T1 scan and DTI, but unfortunately I did not achieve results. I installed: Freesurfer 7.4.1, OS Ubuntu 22.04.5 jammy and VM Oracle 7.0.6 r155176. - Bayesian Tool Bash: export TUTORIAL_DATA=/home/vboxuser/SIEMENS export SUBJECTS_DIR=$TUTORIAL_DATA/GRUPPO_1_6 cd $SUBJECTS_DIR # Subject's data are stored in subj_01 folder source $FREESURFER_HOME/SetUpFreeSurfer.sh export MCRROOT=/usr/local/MATLAB/MATLAB_Runtime/v97 export LD_LIBRARY_PATH=$MCRROOT/runtime/glnxa64:$MCRROOT/bin/glnxa64:$MCRROOT/sys/os/glnxa64:$MCRROOT/sys/opengl/lib/glnxa64:$LD_LIBRARY_PATH # Run segmentation for subj_01 using the simplified -s option /home/vboxuser/freesurfer/ThalamicNucleiDTI/linux_x86_64/run_SegmentThalamicNuclei_DTI.sh $MCRROOT -s subj_01 Answer: /home/vboxuser/freesurfer/ThalamicNucleiDTI/linux_x86_64/run_SegmentThalamicNuclei_DTI.sh $MCRROOT -s subj_01 ------------------------------------------ Setting up environment variables --- LD_LIBRARY_PATH is .:/usr/local/MATLAB/MATLAB_Runtime/v97/runtime/glnxa64:/usr/local/MATLAB/MATLAB_Runtime/v97/bin/glnxa64:/usr/local/MATLAB/MATLAB_Runtime/v97/sys/os/glnxa64:/usr/local/MATLAB/MATLAB_Runtime/v97/sys/opengl/lib/glnxa64 THIS IS THE NEW COMPILED VERSION 2====================================================== subj_01, DTI model DSWbeta. ====================================================== ====================================================== Error while running segmentation. Saving error struct. ====================================================== Error using TS_fnc_thalamus_seg_gem_joint (line 250) The value of 'ASEGsharedParamsPath' is invalid. It must satisfy the function: @(x)exist(x,'file'). Error in TS_fnc_jointSegmentationWrapper (line 64) MATLAB:InputParser:ArgumentFailedValidation -CNN tool Bash: CNN segmentation does work, previous steps were performed accurately and without errors. mri_segment_thalamic_nuclei_dti_cnn --t1 $SUBJECTS_DIR/subj_01/mri/norm.dwispace.mgz --aseg $SUBJECTS_DIR/subj_01/mri/aseg.dwispace.mgz --fa $SUBJECTS_DIR/subj_01/dmri/dtifit_FA.nii.gz --v1 $SUBJECTS_DIR/subj_01/dmri/dtifit_V1.nii.gz --o $SUBJECTS_DIR/subj_01/dmri/segthal.nii.gz --vol $SUBJECTS_DIR/subj_01/dmri/segthal_vol.csv --threads 1 Answer: Illegal instruction (core dumped) How can I do to solve these issues? Thank you in advance, Antonio

2 2

Segmentation fault with mri_mc
by Santtu Söderholm (TAU) 06 Nov '25

06 Nov '25

External Email - Use Caution TUNI Luottamuksellinen - Confidential (3Y) Hello. I recently posted an issue<https://secure-web.cisco.com/1Hy-RfOdIvu4nbqHlECVajVLOAwycAIp37KT5MwNG6iO9M…> on the FreeSurfer GitHub page, related to mri_mc segfaulting when given an aseg.mgz file created with FreeSurfer 8.1.0 recon-all as input. If this is something you might be interested to fix, I can provide you with the input data if necessary. –Santtu Söderholm

1 0

Postdoctoral Scholar Positions
by Craggs, Jason 04 Nov '25

04 Nov '25

External Email - Use Caution Dear Colleagues, The Innovation in Mental Health (iMH) Lab<https://secure-web.cisco.com/1uIXSQhQwPtiGxUTHWJnpAyifGrry8Uw1OjDkGs3kswOy0…> at University of South Florida is hiring two Postdoctoral Scholars to support a National Institute of Mental Health-funded nationwide randomized clinical trial examining the efficacy of a telehealth-based virtual reality clinic for adults with specific phobias. Postdoctoral Fellows (2) * Will serve as trial therapists, conducting intakes and delivering exposure therapy via either traditional telehealth approaches or our telehealth-based Virtual Reality clinic per established protocols. * Will have the opportunity to author/co-author manuscripts on digital mental health solutions using existing or newly collected data, if desired. * Apply here<https://secure-web.cisco.com/1Byp_lBue6KG6xCAEQLxoOteu4WZK4B4r_01WE_Xx8-QiT…> (https://secure-web.cisco.com/1Byp_lBue6KG6xCAEQLxoOteu4WZK4B4r_01WE_Xx8-QiT…) These are excellent opportunities to join a lab advancing digital mental health care. Please share widely with interested candidates. With best regards, Jason --------------------------------- Jason G Craggs, Ph.D. Assistant Professor SHP/Physical Therapy University of Missouri 801 Clark Hall Columbia, MO 65211-4250 Phone: 573-884-9345 http://secure-web.cisco.com/1eem70kqVFfR779S9tLWT0wHW4D6NPRIgKI4XXKfoP2QYh2… https://secure-web.cisco.com/1Ki2A_muKI1H5q7YNLx6ErVhIHFH9NC4tsWEL7wRNy0heD… https://secure-web.cisco.com/16aHgRR5EoM4sSm_tJPg5tN59QalwTgc2VVkcmFAkRRd0N…

1 0

Re: CC segmentation fault
by fsbuild 04 Nov '25

04 Nov '25

External Email - Use Caution We did not test 8.1.0 on Tahoe since it was not available to the public at the time of release, and this is listed on the download page,https://secure-web.cisco.com/1rfkB_Axztd9_0N5DEtIEbpY7KHdLK0Q8mmjMU2hD… testing has been done on …Mac OS: 12.X (Monterey), 13.X (Ventura), 14.X (Sonoma), 15.X (Sequoia) with separate Intel and arm64 installers. … and not …Please note no testing has been done on MacOS 26 (Tahoe) scheduled to be released in 12/2025. It reads like you got the same error running an older version of MacOS.  If so please let us know what version of MacOS you were running prior to Tahoe.  You may run into other issues by running 8.1.0 on Tahoe.  I would consider reverting back to your previous version of MacOS if you made a backup, e.g., with Carbon Copy Cloner or some other utility. - R. On Nov 4, 2025, at 04:35, Hao Wang (PGR) <H.Wang118(a)newcastle.ac.uk> wrote:        External Email - Use Caution        Hi Freesurfer Developers, I’m attempting to run recon-all but keep on coming across this same error: mri_cc -aseg aseg.auto_noCCseg.mgz -o aseg.auto.mgz -lta transforms/cc_up.lta 1047will read input aseg from aseg.auto_noCCseg.mgzwriting aseg with cc labels to aseg.auto.mgzwill write lta as transforms/cc_up.ltaSegmentation faultERROR: mri_cc -aseg aseg.auto_noCCseg.mgz -o aseg.auto.mgz -lta transforms/cc_up.lta 1047 recon-all -s 1047 exited with ERRORS at Wed Oct 29 18:32:30 GMT 2025 I found a couple reports of people encountering the same error, with some suggesting that upgrading macOS resolved the issue. Unfortunately, that solution didn’t work in my case. The problem closely matches the one described in this post and this post, where the file “aseg.auto_noCCseg.mgz”  is only 16 bytes in size. Similarly, when I checked “synthseg.vol.csv” in the “stats” folder, the reported volumes for all segments were 0. FreeSurfer version: freesurfer-macOS-darwin_arm64-8.1.0-20250718-f30dfedPlatform: macOS Tahoe 26.0.1uname -a: Darwin 22SCompL011.local 25.0.0 Darwin Kernel Version 25.0.0: Wed Sep 17 21:41:45 PDT 2025; root:xnu-12377.1.9~141/RELEASE_ARM64_T6000 arm64recon-all.log: see attached <recon-all.log>_______________________________________________Freesurfer mailing list -- freesurfer(a)nmr.mgh.harvard.eduTo unsubscribe send an email to freesurfer-leave@nmr.mgh.harvard.eduhttps://mail.nmr.mgh.harvard.edu/mailman3/lists/freesurfer@nmr.mgh.harvard.edu/

2 1

CC segmentation fault
by Hao Wang (PGR) 04 Nov '25

04 Nov '25

External Email - Use Caution Hi Freesurfer Developers, I’m attempting to run recon-all but keep on coming across this same error: mri_cc -aseg aseg.auto_noCCseg.mgz -o aseg.auto.mgz -lta transforms/cc_up.lta 1047 will read input aseg from aseg.auto_noCCseg.mgz writing aseg with cc labels to aseg.auto.mgz will write lta as transforms/cc_up.lta Segmentation fault ERROR: mri_cc -aseg aseg.auto_noCCseg.mgz -o aseg.auto.mgz -lta transforms/cc_up.lta 1047 recon-all -s 1047 exited with ERRORS at Wed Oct 29 18:32:30 GMT 2025 I found a couple reports of people encountering the same error, with some suggesting that upgrading macOS resolved the issue. Unfortunately, that solution didn’t work in my case. The problem closely matches the one described in this post<https://secure-web.cisco.com/1eUJH1QOVis9V-ja_XistwYUH99s1WkkKGscZLAnWqIcpX…> and this post<https://secure-web.cisco.com/1em4eF9GNBoGc5vVMCfPLPX9WS5q43YwfPAfj41wlBnIw_…>, where the file “aseg.auto_noCCseg.mgz” is only 16 bytes in size. Similarly, when I checked “synthseg.vol.csv” in the “stats” folder, the reported volumes for all segments were 0. 1. FreeSurfer version: freesurfer-macOS-darwin_arm64-8.1.0-20250718-f30dfed 2. Platform: macOS Tahoe 26.0.1 3. uname -a: Darwin 22SCompL011.local 25.0.0 Darwin Kernel Version 25.0.0: Wed Sep 17 21:41:45 PDT 2025; root:xnu-12377.1.9~141/RELEASE_ARM64_T6000 arm64 4. recon-all.log: see attached

1 0

Re: Different output data
by fsbuild 03 Nov '25

03 Nov '25

External Email - Use Caution The freesurfer download and release page, https://secure-web.cisco.com/1m4Xp1On93_NmEn7Cxw8FyoPqk6laiThpewSNU4ieoINqb… - contains the following notice, Important Note: When processing a group of subjects for your study, it is essential to process all your subjects with the same version of FreeSurfer, on the same OS platform and vendor, and for safety, even the same version of the OS. While we continue to work to ensure that results match across platforms, there are none-the-less system-level libraries that are OS dependent. An exception to this rule is that you may view and edit files across any platform or version, and run some post-processing tools (outside the recon-all stream) if you check with us first (for instance you may run the longitudinal processing with newer versions). Results are expected to differ in the recon-all output if you run the same subject with the same freesurfer release on two different vendors operating system; likewise it can also happen across 2 different versions of the same vendors operating system.  When the OS changes the system libraries, then the floating point math output can also change. An example of files that can differ in the recon-all output for the same subject processed with the same freesurfer release across 2 different versions of the same vendors OS are listed below. - R. different: mri/aparc.a2009s+aseg.mgzdifferent: mri/aparc+aseg.mgzdifferent: mri/aparc.DKTatlas+aseg.mgzsame: mri/aseg.auto.mgzsame: mri/aseg.auto_noCCseg.mgzdifferent: mri/aseg.mgzdifferent: mri/aseg.presurf.hypos.mgzsame: mri/aseg.presurf.mgzdifferent: mri/brain.finalsurfs.mgzsame: mri/brainmask..mgzdifferent: mri/brain.mgzdifferent: mri/filled.mgzdifferent: mri/lh.ribbon.mgzsame: mri/norm.mgzsame: mri/nu.mgzsame: mri/orig.mgzsame: mri/rawavg.mgzdifferent: mri/rh.ribbon.mgzdifferent: mri/ribbon.mgzdifferent: mri/surface.defects.mgzsame: mri/T1.mgzdifferent: mri/wm.asegedit.mgzdifferent: mri/wm.mgzdifferent: mri/wmparc.mgzdifferent: mri/wm.seg.mgzdifferent: surf/lh..fsaverage.sphere.regdifferent: surf/lh.inflateddifferent: surf/lh.inflated..nofixdifferent: surf/lh.origdifferent: surf/lh.orig.nofixdifferent: surf/lh.pialdifferent: surf/lh.pial.T1different: surf/lh.qsphere.nofixdifferent: surf/lh.smoothwmdifferent: surf/lh.smoothwm.nofixdifferent: surf/lh.spheredifferent: surf/lh.sphere.regdifferent: surf/lh.whitedifferent: surf/lh..white.preaparcdifferent: surf/rh.fsaverage.sphere.regdifferent: surf/rh.inflateddifferent: surf/rh.inflated.nofixdifferent: surf/rh.origdifferent: surf/rh.orig.nofixdifferent: surf/rh.pialdifferent: surf/rh.pial.T1different: surf/rh.qsphere.nofixdifferent: surf/rh.smoothwmdifferent: surf/rh.smoothwm.nofixdifferent: surf/rh.spheredifferent: surf/rh.sphere.regdifferent: surf/rh..whitedifferent: surf/rh.white.preaparcdifferent: surf/lh.areadifferent: surf/lh.area.middifferent: surf/lh.area.pialdifferent: surf/lh.avg_curvdifferent: surf/lh.curvdifferent: surf/lh.curv.pialdifferent: surf/lh.defect_bordersdifferent: surf/lh.defect_chulldifferent: surf/lh.defect_labelsdifferent: surf/lh.inflated.Hdifferent: surf/lh.inflated.Kdifferent: surf/lh.jacobian_whitedifferent: surf/lh.smoothwm.BE.crvdifferent: surf/lh.smoothwm.C.crvdifferent: surf/lh..smoothwm.FI.crvdifferent: surf/lh.smoothwm.H.crvdifferent: surf/lh.smoothwm.K1.crvdifferent: surf/lh.smoothwm.K2.crvdifferent: surf/lh.smoothwm.K.crvdifferent: surf/lh.smoothwm.S.crvdifferent: surf/lh.sulcdifferent: surf/lh.thicknessdifferent: surf/lh.volumedifferent: surf/lh.w-g.pct.mghdifferent: surf/lh.white.Hdifferent: surf/lh.white.Kdifferent: surf/lh.white.preaparc.Hdifferent: surf/lh.white.preaparc.Kdifferent: surf/rh.areadifferent: surf/rh.area.middifferent: surf/rh.area.pialdifferent: surf/rh..avg_curvdifferent: surf/rh.curvdifferent: surf/rh.curv.pialdifferent: surf/rh.defect_bordersdifferent: surf/rh.defect_chulldifferent: surf/rh.defect_labelsdifferent: surf/rh.inflated.Hdifferent: surf/rh.inflated.Kdifferent: surf/rh.jacobian_whitedifferent: surf/rh.smoothwm.BE.crvdifferent: surf/rh.smoothwm.C.crvdifferent: surf/rh.smoothwm.FI.crvdifferent: surf/rh.smoothwm..H.crvdifferent: surf/rh.smoothwm.K1.crvdifferent: surf/rh.smoothwm.K2.crvdifferent: surf/rh.smoothwm.K.crvdifferent: surf/rh.smoothwm.S.crvdifferent: surf/rh.sulcdifferent: surf/rh.thicknessdifferent: surf/rh.volumedifferent: surf/rh.w-g..pct.mghdifferent: surf/rh.white.Hdifferent: surf/rh.white.Kdifferent: surf/rh.white.preaparc..Hdifferent: surf/rh.white.preaparc.Kdifferent: label/lh.aparc.a2009s.annotdifferent: label/lh.aparc.annotdifferent: label/lh.aparc.DKTatlas.annotdifferent: label/lh.BA_exvivo.annotdifferent: label/lh.BA_exvivo.thresh.annotdifferent: label/lh.mpm.vpnl.annotdifferent: label/rh.aparc.a2009s.annotdifferent: label/rh.aparc.annotdifferent: label/rh.aparc.DKTatlas..annotdifferent: label/rh.BA_exvivo.annotdifferent: label/rh.BA_exvivo.thresh.annotdifferent: label/rh.mpm.vpnl.annot On Nov 3, 2025, at 06:44, Felipe da Silveira Minuceli <felipe.minuceli(a)unifesp.br> wrote:        External Email - Use Caution        Hello, My name is Felipe and I'm a medical student from Brazil. My research involves using Freesurfer to process neuroanatomical MRIs from several individuals. I'm collaborating with a PhD student and comparing my processed images with his. We use the same version of Freesurfer (7.4.1) and the same processing command (recon-all), but different Linux-based software and computers. However, our output data is slightly different (brain segmentation volume, surface holes, WM hypointensities, and estimated total intracranial volume) I'd like to know why this is happening? Should we get the same output data, or is this correct? Can I control other variables to get the same output data? Thank you, --  Felipe MinuceliGraduando de Medicina(11) 97483-9774 ---- É obrigatória a utilização do e-mail @unifesp em todas as correspondências oficiais, institucionais e no acesso aos equipamentos e sistemas da Universidade Federal de São Paulo, conforme a portaria Reitoria n. 1182/2022 que define a Política de e-mail institucional da Unifesp._______________________________________________ Freesurfer mailing list -- freesurfer(a)nmr.mgh.harvard.edu To unsubscribe send an email to freesurfer-leave(a)nmr.mgh.harvard.edu https://secure-web.cisco.com/1AU7FaE3hPm6x46WzqcypCUmynJsb3RD7QRvTHgCpH-zp9…

1 0

Help configuring trac-all with reverse polarity b0s
by Mudarris, M.A.A. (Mohammed) 03 Nov '25

03 Nov '25

External Email - Use Caution Hi all, I’m running trac-all for a longitudinal study (2 sessions per subject) using BIDS-formatted DWI data. My sequence includes the following scans per session: * pre_dwi_b0_AP * dwi_AP (first volume is also b0_AP) * b0_post_dwi_AP * b0_post_dwi_PA (reverse polarity) I want to use reverse polarity distortion correction (dob0 = 2) and FSL's eddy (doeddy = 2). My dmrirc includes: set pedir = ( AP AP AP PA ). I’ve tried the following: 1. merging AP b0s with dwi and keeping PA separate, using dcmlist, boplist, and b0mlist, but trac-all doesn’t seem to recognize the reverse polarity b0. 2. I also tried merging all into one 4D file — still no luck. Any advice on how to structure the files and configure dmrirc properly for topup to work? Thanks! Best wishes, Mohammed Mudarris, M.Sc. PhD Candidate | Health, Medical, and Neuropsychology Unit | Leiden University | Classified as Internal | Intern

1 0

Different output data
by Felipe da Silveira Minuceli 03 Nov '25

03 Nov '25

External Email - Use Caution Hello, My name is Felipe and I'm a medical student from Brazil. My research involves using Freesurfer to process neuroanatomical MRIs from several individuals. I'm collaborating with a PhD student and comparing my processed images with his. We use the same version of Freesurfer (7.4.1) and the same processing command (recon-all), but different Linux-based software and computers. However, our output data is slightly different (brain segmentation volume, surface holes, WM hypointensities, and estimated total intracranial volume) I'd like to know why this is happening? Should we get the same output data, or is this correct? Can I control other variables to get the same output data? Thank you, -- *Felipe Minuceli* Graduando de Medicina (11) 97483-9774 -- ---- É obrigatória a utilização do e-mail @unifesp em todas as correspondências oficiais, institucionais e no acesso aos equipamentos e sistemas da Universidade Federal de São Paulo, conforme a portaria Reitoria n. 1182/2022 <https://secure-web.cisco.com/1kAOZ_Li0vGoS3yzuDmxkOHQDsACM95jKIXTGbx_Na3sSv…> que define a Política de e-mail institucional da Unifesp. <https://secure-web.cisco.com/16uqmyCDJWb27fvVgYmzmvQW94WsJn-xM4ywLW20nJJv6A…>

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Freesurfer November 2025