Virtual Network Computing (VNC) nodes allow users to connect remotely to a graphical desktop environment running on our systems.
Attention: From September 24th 2018 the default login for CCV users will be the Red Hat 7 system. Please refer to the Red Hat 7 user manual
To connect to the CentOS 6 system VNC use
desktop6.ccv.brown.edu as the server name
Using VNC, you can run applications and scripting languages like Matlab, Mathematica, Maple, python, perl, or the R statistical package (shown on the left) on our high-performance and large-memory systems. You also have fast access to CCV's local high performance file system so that you can access and analyze large data files without having to copy them to your own system.
To use the CCV VNC client, you will first need to install Java. The VNC client supports Java versions 7, 8, 9 and 10, we recommend versions 8 and 9. Java can be downloaded from the java.com website. Note that you only need the Java Runtime Environment (JRE) to use the client.
We have a new VNC client that integrates with our scheduling system to create dedicated, persistent VNC sessions that are tied to a single user.
Download the jar file above. This file will work on all platforms.
Ensure you have a recent version of the Java JDK or JRE. These can be found on Oracle's Java Download Page .
If Java has been installed correctly you can now run CCV_VNC_2.x.jar by double clicking on it. On MAC, you may need to first right click on the jar and chose "Open", and give the jar permission to run.
In the "Username" and "Password" field, enter your Oscar username and password. The server should remain "desktop.ccv.brown.edu". Press "Connect."
On the window that pops up, select the memory/CPU parameters for your personal VNC session.
Your VNC session should appear. If you see a window saying your job was queued, it means there were not enough free resources to start your job and it was placed into the scheduling queue. You'll continue to get that message until your VNC job actually starts. You can monitor the progress of your job in the queue using normal scheduler commands.
Once your VNC session starts, you should see your desktop. There are two new buttons on the menubar at the top, Suspend VNC session and End VNC session.
When you are finished with your VNC session, click the "EXIT" button, you now have two choices:
Disconnect from VNC session closes the client but leaves your VNC session running. When you log in again, you will be automatically forwarded to your existing VNC session.
Kill VNC session closes the client and stops your VNC session from running.
Note: Closing the VNC window will only disconnect from the VNC session, it will not kill it.
Sessions are limited to 7 days for all user, depending on resources selected. After this time, the session will expire. If you need to run programs that will exceed these limits, you can use "interact -X" to launch an interactive job on another node.