| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
|
[wiki:Self:FreeSurferWiki top] = FreeSurfer Remote Access = |
|
| Line 8: | Line 4: |
| For simplicity, let's call the host computer (the one running freesurfer) "WORK". | For simplicity, let's call the host computer (the one running freesurfer) "WORK". |
| Line 10: | Line 6: |
| Line 30: | Line 27: |
| == 4. Run your vncserver.glx == | = 4. Run your vncserver.glx = |
| Line 37: | Line 34: |
|
Here is the attachment:vncserver.glx script if your server is not at the NMR Center (in which case you will also need [http://xf4vnc.sourceforge.net xf4vnc], to get GLX support with VNC). == 5. Run your vnc clinet == |
= 5. Run your vnc clinet = |
| Line 42: | Line 37: |
|
== ADDITIONAL NOTES: == * VNC is supposed to be optimized for sending remote screen images. Therefore, it is preferred over using X forwarding if you are not on a local intranet. * If you are using SSH tunnelling, then you have encrypted the connection, which is a good thing if whatever you are doing shouldn't be seen by others. * vncserver WILL NOT run freesurfer correctly. Only vncserver.glx will do the job. * On some machines, the colors will be funky with vncserver.glx. They will be normal with vncserver. That's just how it is. * If these instructions are not working for you, [http://www.nmr.mgh.harvard.edu/martinos/userInfo/computer/remoteAccess.php then try these]. |
= ADDITIONAL NOTES: = * - VNC is supposed to be optimized for sending remote screen images. Therefore, it is preferred over using X forwarding if you are not on a local intranet. * - If you are using SSH tunnelling, then you have encrypted the connection, which is a good thing if whatever you are doing shouldn't be seen by others. * - vncserver WILL NOT run freesurfer correctly. Only vncserver.glx will do the job. * - On some machines, the colors will be funky with vncserver.glx. They will be normal with vncserver. That's just how it is. |
Suppose you want to run freesurfer from home remotely? (this means freesurfer runs on a different computer, and the screen is forwarded to a different computer)
For simplicity, let's call the host computer (the one running freesurfer) "WORK". And the remote computer (the one viewing the copy of the screen) "HOME".
1. Get a VNC client:
To view freesurfer remotely, you need a VNC viewer program for HOME.
For linux
vncviewer
For windows
realVNC
For Mac
chicken of the VNC
All three abovementioned programs are free and available on the web.
2. Get a VNC server
You also need a vnc server on WORK. vncserver.glx and vncserver are free linux programs. Get them if you don't have them already.
3. If needed, learn about SSH tunnelling
If you are logging into a remote computer with fancy security, you may need to use SSH tunnelling. Check the internet for details about how to do this. (it is not hard)
4. Run your vncserver.glx
From the WORK computer, simply enter:
vncserver.glx
(note: password protection is available... see vncserver documentation)
5. Run your vnc clinet
From you HOME computer, run the client, and log into the WORK computer.
ADDITIONAL NOTES:
- - VNC is supposed to be optimized for sending remote screen images. Therefore, it is preferred over using X forwarding if you are not on a local intranet.
- - If you are using SSH tunnelling, then you have encrypted the connection, which is a good thing if whatever you are doing shouldn't be seen by others.
- - vncserver WILL NOT run freesurfer correctly. Only vncserver.glx will do the job.
- - On some machines, the colors will be funky with vncserver.glx. They will be normal with vncserver. That's just how it is.