Yea, that is actually a feature in the new version
On 07/02/2014 02:17 PM, Joshua S wrote: > Hi all, > I was following the group analysis tutorial when I got an error when > trying to view the uncorrected significance map with freeview. I used > the command "freeview -f > $SUBJECTS_DIR/fsaverage/surf/lh.inflated:annot=aparc.annot:overlay=lh.gender_age.glmdir/lh-Avg-thickness-age-Cor/sig.mgh:overlay_threshold=4,5 > > -viewport 3d". I removed the annot_outline=1, because it gave an > error. Sig.mgh would not load, and I would get the attached image. I > tried to manually add sig.mgh through add surface, but the program > immediatley closed, and I got the message in the attached error.log. > Text below. > > Thank you for any help, > Josh > Did not find any volume geometry information in the surface > �Tgreading colortable from annotation file... > colortable with 36 entries read (originally > /autofs/space/terrier_001/users/nicks/freesurfer/average/colortable_desikan_killiany.txt) > colortable with 36 entries read (originally > /autofs/space/terrier_001/users/nicks/freesurfer/average/colortable_desikan_killiany.txt) > Did not find color table in track volume. > [0]PETSC ERROR: > ------------------------------------------------------------------------ > [0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation, > probably memory access out of range > [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger > [0]PETSC ERROR: or see > http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[0]PETSC > > ERROR: or try http://valgrind.org on linux or man libgmalloc on Apple > to find memory corruption errors > [0]PETSC ERROR: configure using --with-debugging=yes, recompile, link, > and run > [0]PETSC ERROR: to get more information on the crash. > [0]PETSC ERROR: --------------------- Error Message > ------------------------------------ > [0]PETSC ERROR: Signal received! > [0]PETSC ERROR: > ------------------------------------------------------------------------ > [0]PETSC ERROR: Petsc Release Version 2.3.3, Patch 13, Thu May 15 > 17:29:26 CDT 2008 HG revision: 4466c6289a0922df26e20626fd4a0b4dd03c8124 > [0]PETSC ERROR: See docs/changes/index.html for recent updates. > [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. > [0]PETSC ERROR: See docs/index.html for manual pages. > [0]PETSC ERROR: > ------------------------------------------------------------------------ > [0]PETSC ERROR: Unknown Name on a linux-gnu named > farklemt.nmr.mgh.harvard.edu <http://farklemt.nmr.mgh.harvard.edu> by > dc325 Wed Jul 2 11:35:56 2014 > [0]PETSC ERROR: Libraries linked from > /autofs/space/lyon_006/pubsw/Linux2-2.3-x86_64/packages/petsc/2.3.3-p13/src/petsc-2.3.3-p13/lib/linux-gnu-c-opt > [0]PETSC ERROR: Configure run at Tue Aug 10 15:01:59 2010 > [0]PETSC ERROR: Configure options --with-debugging=no --with-cc=gcc > --with-fc=g77 --download-f-blas-lapack=0 --download-mpich=1 > --with-mpi=1 --with-x=0 --with-gnu-copyright-code=0 --with-shared=0 > COPTFLAGS=-O3 CXXOPTFLAGS=-O3 FOPTFLAGS=-O3 > [0]PETSC ERROR: > ------------------------------------------------------------------------ > [0]PETSC ERROR: User provided function() line 0 in unknown directory > unknown file > [unset]: aborting job: > application called MPI_Abort(MPI_COMM_WORLD, 59) - process 0 > > > > _______________________________________________ > Freesurfer mailing list > Freesurfer@nmr.mgh.harvard.edu > https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer -- Douglas N. Greve, Ph.D. MGH-NMR Center gr...@nmr.mgh.harvard.edu Phone Number: 617-724-2358 Fax: 617-726-7422 Bugs: surfer.nmr.mgh.harvard.edu/fswiki/BugReporting FileDrop: https://gate.nmr.mgh.harvard.edu/filedrop2 www.nmr.mgh.harvard.edu/facility/filedrop/index.html Outgoing: ftp://surfer.nmr.mgh.harvard.edu/transfer/outgoing/flat/greve/ _______________________________________________ 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.