Would it be possible for you to try the freeview build from FS v7:
https://surfer.nmr.mgh.harvard.edu/fswiki/UpdateFreeview
Best,
Ruopeng
On Oct 16, 2020, at 2:47 PM, Álvaro Deleglise
mailto:alvarodelegl...@gmail.com>> wrote:
External Email - Use Caution
Hi everybody,
I've just insta
External Email - Use Caution
Hi everybody,
I've just installed FreeSurfer v6 in my ubuntu 20.04 SO, but I can't open
freeview due to PETSC errors. I executed "freeview" in the console, and
then the following messages appear:
[0]PETSC ERROR:
11:56 PM
To: freesurfer@nmr.mgh.harvard.edu
Subject: [Freesurfer] Petsc Error in Freesurfer v6.0
Hello Freesurfer Developers,
I've just installed Freesurfer v6.0 and attempted to run the commands printed
below in order to test the installation:
freeview -v \
bert/mri/T1.mgz \
ber
This problem has been resolved by installing Freesurfer v6.0 on a Ubuntu 16.04
64-bit guest OS with "fixed disk space" instead of "Dynamically allocated".
Michael
The opinions, conclusions and other information expressed in the above message,
or contained within attachments to the above messa
Hello Freesurfer Developers,
I've just installed Freesurfer v6.0 and attempted to run the commands printed
below in order to test the installation:
freeview -v \
bert/mri/T1.mgz \
bert/mri/wm.mgz \
bert/mri/brainmask.mgz \
bert/mri/aseg.mgz:colormap=lut:opacity=0.2 \
-f \
Hi Lilla,
Yes, sadly the problem still persists. The strangest part is that the same
error occurred when I tried to process bert (mri_cvs_register --mov bert)
using the VirtualBox Ubuntu package for FS on Windows. My only guess (as
suggested by one of the other users) is that it's a problem
Hi David,
Have you downloaded the updates of mri_cvs_register from
http://surfer.nmr.mgh.harvard.edu/fswiki/ReleaseNotes ? We found some bugs
in the orginial 5.1 release and put the fixed versions at the above.
Let me know if that still does not solve the problem.
--Lilla
On Tue, 21 Jun 20
Hi
I posted a couple days ago about a PETSC ERROR with while running
mri_cvs_register but I seem to be having a more general problem. I'm
receiving the same error on two 10.6.7 macs as well as on a Windows running
virtualbox, both while processing my own subjects and FS5.1 bert. I'm using
the comma
