Remote Observing on the GBT

• Remote Observing Guidelines for Approved Projects
• VNC Setup Instructions
  • What is VNC (Virtual Network Connection)?
  • Why is VNC Useful for GBT Remote Observing?
  • How Do I Get the Necessary Software?
  • How Do I Set up VNC?
    • How do I Provide a VNC Password?
    • How Do I Set Up a Window Manager?
  • How Do I Establish a VNC Session?
  • How Do I Start a VNC Viewer on My Local Machine?
  • I Need Some Troubleshooting Information
  • What Special Features Does the VNC Viewer Window Have?
  • How Do I Close My VNC Session
  • Any Additional VNC Resources?

Remote Observing Guidelines for Approved Projects

Permission to observe remotely must be explicitly granted by Carl Bignell, the Telescope Scheduler, at least two weeks prior to the observing run. Permission will be granted based on the appropriateness of the project and the demonstrated experience of the observer. Guidelines for approved remote observing projects are as follows.

• Consult with the staff support astronomer at least two weeks prior to observing time.
• Provide the staff support astronomer with your telephone contact numbers (work, home, and cell) and agree in advance your location during the observations.
• Prepare ASTRID observing scripts in advance
• Contact the telescope operator 30 minutes before the start of your setup time. The number to call is 304-456-2346 or the Operator's direct line at 304-456-2341. x2346 connects to a speaker phone and is the preferred number to use. Provide the operator with all the appropriate contact information in case they need to contact you during the run.
• We strongly recommend VNC network displays of observing applications. Suggested VNC setup procedures are provided below.
• Start up your observing applications immediately after contacting the operator. These usually include
  
  cleo
  
  Open at least the 'Talk & Draw' windows, then any other cleo application you need. You can use Talk & Draw to communicate with the operator during the run and after you have finished with the phone.
  
  astrid
gbtidl
  
  Or another data reduction program to be used

• At the start of your observing time, again call the telescope operator at 304-456-2346, who will put you on a speaker phone. The line should stay open at least through the setup period. (The backup line in case x2346 is busy is the Operator's direct line at 304-456-2341. This line does not have a speaker phone, however.)
• When your observing time starts and the operator gives you permission, you should use Astrid to load your configuration and start observing.

VNC Setup Instructions

The example below uses the computer titania.gbt.nrao.edu for the VNC server. Titania is currently the computer usually available to host VNC sessions. As our computer infrastructure changes, this might not be always the case. You should always ask the operator for the name of the computer you should use and substitute that computer's name for titania's in the instructions below.

What is VNC (Virtual Network Connection)?

VNC allows remote connections from a client computer to a server, creating a virtual desktop (desktop image) of the server screen on the client computer screen. The user of the client computer can work almost as if he or she were sitting in front of the screen of the remote computer. VNC continuously compresses and transfers screen shots from the server to the client which makes this a much quicker experience than normal X-forwarding, especially for complicated, line-drawn windows.

Why is VNC Useful for GBT Remote Observing?

VNC allows the remote GBT observer to connect to a computer in the GBT control room (e.g. ariel, titania, naiad) from the observer's home/work machine in order to observe. Once the VNC session is set up, the remote observer can open astrid, cleo, gbtidl, etc. and perform other functions just as if he or she were actually in the control room sitting in front of the remote computer's screen.

How Do I Get the Necessary Software?

VNC comes with most Linux distributions and is easily set up. Mac and Windows users should download and install a VNC Viewer.

How Do I Set up VNC?

If this is your first session ever with VNC, you need to setup a VNC server password and specify what window manager you would like.

How do I Provide a VNC Password?

Choose a password that is different from your NRAO Linux account password as you may later wish to share this password with others who can then observe your VNC session. For example, if you are having difficulties during a remote observing session, you might wish to share your VNC password with a Green Bank staff member who can access your virtual desktop and suggest solutions to your problems.

To create a VNC server password, you must log into an NRAO computer. The first steps for Linux and MacOS users is different than those for Windows users:

Once you are logged into the NRAO computer, and regardless of your remote computer:

• In the terminal window on the remote (NRAO) computer, type at the Linux prompt:
  
  vncpasswd
  
  
• Enter your chosen VNC server password. Remember, this password should be different from your NRAO Linux account password as it will be shared with support staff when you require assistance.

How Do I Set Up a Window Manager?

By default, you will be given TWM as a window manager for VNC sessions. If you would like FVWM (recomended) or KDE, you can perform the following steps:

Once you are logged into the NRAO computer, and regardless of your remote computer:

• In the terminal window on the remote (NRAO) computer, type at the Linux prompt:
  
  mkdir ~/.vnc
  
  If you have already used VNC in the past, this step is not necessary and you will get a message stating that the 'file' already exists. This is normal.
• Select your desired window manager. If you want to use the fvwm window manager (recomended), at the Linux prompt, type:
  
  cp ~rmaddale/.vnc/xstartup_fvwm ~/.vnc/xstartup
  
  If you want to use the kde window manager, at the Linux prompt, type:
  
  cp ~rmaddale/.vnc/xstartup_kde ~/.vnc/xstartup
  
  

How Do I Establish a VNC Session?

IMPORTANT! Please do not start more than one VNC server at a time! There is only a limited total number of sessions and ports available at any time. Likewise, don't forget to end your VNC server session when you are finished observing. For instructions on ending your VNC server session, please read closing your VNC server session.

Each time you observe remotely with the GBT, you will need to follow these instructions.

To set up a session at the remote machine, you must first log into an NRAO computer. The first steps for Linux and MacOS users is different than those for Windows users:

Once you are logged into the NRAO computer, and regardless of your remote computer:

• In the terminal window on the remote (NRAO) computer, type at the Linux prompt:
  
  ssh titania.gbt.nrao.edu :
  
  If you are not using an SSH agent, you will be asked to enter your NRAO Linux account username and password.
• At the Linux prompt on titania, type:
  
  vncserver
  
  
  • You can also run vncserver with color depth or size options: For example
    
    vncserver [ -geometry e.g. 2048x1024 ] [ -depth 8 ]
    
    
  • These options allow you to specify an alternate screen geometry or color depth. The first number for the geometry is the screen width which we advise should be 2x wider than the size of your local monitor. Choose a screen height that is 1024 or larger, so as to accomodate the typical observing applications. If you have a monitor that is more than 1024 pixels high, choose a screen height that is slightly smaller than the native height of your local monitor.
  • Choose 8-bit color to speed up the transfer of displays in the VNC session. Sometimes, it isn't necessary to start with VNC server with the -depth options since your viewer may assume defaults that might actually work better without this switch.
  • If this is your first session in Green Bank, you will be asked which password should protect your future sessions. As noted above, choose a password that is different from your Linux account password as you may later wish to share this password with others who can then observe your VNC session. For example, if you are having difficulties during a remote observing session, you might wish to share your VNC password with a Green Bank staff member who can access your virtual desktop and suggest solutions to your problems.
• Once you have typed vncserver, the system will reply (e.g.) New 'titania:2 (USERNAME)' desktop is titania:2 In this case, your VNC session number is 2. Remember this number since you will need it later. In the instructions below, the VNC session number is designated as n.
• Leave this connection open to the server. Later, it will be used to kill processes on titania associated with the VNC session.

How Do I Start a VNC Viewer on My Local Machine?

You will need a VNC viewer in order to view the session on your local machine (work/home).

I Need Some Troubleshooting Information

There have been times when a local port is taken by another user or another VNC session. In these rare cases, the recommended port forwarding won't work. To determine if a port is used, the Windows and Linux command,

   netstat -a

will list all used ports. In these cases, the tunnel has to be changed to 590m:ssh.gb.nrao.edu:590n where 590m is some unused port somewhere above 5900. And, whereever we have localhost:n in the above instructions, substitute localhost:m.

If you would like to check if you are already running a VNC Servers (really, there should be only one), use any terminal that is logged into an NRAO computer and type:

   ls ~YOURLOGIN/.vnc | grep .pid

What Special Features Does the VNC Viewer Window Have?

• Depressing the left mouse button inside the main VNC Viewer window brings up a menu, allowing you, for example, to open another xterm.
• Minimizing a window - Click on the upper left part of a window.
• Resizing a window – Use the icon at the upper right of a window
• To configure your VNC Viewer, press F8 and a menu should appear

How Do I Close My VNC Session

IMPORTANT!!! If you stop using vncviewer but don't kill the server, the sessions stays alive. If you run vncviewer later (the next day for example) or from a different computer you can continue where you left off. There is however only a limited total number of sessions and ports available at any time. Unless you know you will be using the session again within a few hours, please do not leave a vncserver running more than is necessary. Also, please do not start more than one VNC server at a time.

To stop the session, close your vncviewer. You'll need a terminal window that is logged into an NRAO computer.

Once you are logged into the NRAO computer, and regardless of your remote computer:

• In the terminal window on the remote (NRAO) computer, type at the Linux prompt:
  
  ssh titania.gbt.nrao.edu
  
  
• Type:
  
  vncserver -kill :N
  
  where N is the VNC server number.

Any Additional VNC Resources?

A short guide to VNC for Window's users is available.

We would like to thank Joeri van Leeuwen (UBC), Tom Troland (U. Kentucky), and Jeff Mangum (NRAO CV) who kindly provided the entire content of these instructions. We appreciate the time they took to make VNC easier for all remote observers.

Version 1.2 May 8, 2006
Version 1.1 September 6, 2005
Version 1.0 January 28, 2005

The instructions for "Remote Observing on the GBT" have moved.

The new location is: http://www.gb.nrao.edu/gbt/remoteobserving.shtml

• Once you have typed vncserver, the system will reply (e.g.) New 'titania:2 (USERNAME)' desktop is titania:2 In this case, your VNC session number is 2. Remember this number since you will need it later. In the instructions below, the VNC session number is designated as N.

• Once you have typed vncserver, the system will reply (e.g.) New 'titania:2 (USERNAME)' desktop is titania:2 In this case, your VNC session number is 2. Remember this number since you will need it later. In the instructions below, the VNC session number is designated as n.

• • • Connection > SSH > Tunnels – Remove any previously used ports with the Remove button. For Source port enter 590N, where N is the VNC session number reported in the first PuTTY window (the VNC server). For Destination, enter titania.gbt.nrao.edu:590N Then choose Add, then Open.

• • • Connection > SSH > Tunnels – Remove any previously used ports with the Remove button. For Source port enter 590n, where n is the VNC session number reported in the first PuTTY window (the VNC server). For Destination, enter titania.gbt.nrao.edu:590n Then choose Add, then Open.

• • As Server, enter localhost:N, where N is the VNC session number, as always.

• • As Server, enter localhost:n, where n is the VNC session number, as always.

• • • Type in a terminal on your local computer:
      
      ssh -N -C -L 590N:titania.gbt.nrao.edu:590N YOURLOGIN@ssh.gb.nrao.edu &
      
      
    • Type in a terminal on your local computer:
      
      vncviewer -Shared localhost:N
      
      

• • • Type in a terminal on your local computer:
      
      ssh -N -C -L 590n:titania.gbt.nrao.edu:590n YOURLOGIN@ssh.gb.nrao.edu &
      
      
    • Type in a terminal on your local computer:
      
      vncviewer -Shared localhost:n
      
      

• Type in a terminal on your local computer:
  
  ssh -N -C -L 5900:titania.gbt.nrao.edu:590N YOURLOGIN@ssh.gb.nrao.edu
  
  

• Type in a terminal on your local computer:
  
  ssh -N -C -L 590n:titania.gbt.nrao.edu:590n YOURLOGIN@ssh.gb.nrao.edu
  
  

• • Set Host to localhost, set Display to 0, enter your password, check Remember Password, and check Allow other clients to connect.

• • Set Host to localhost, set Display to n, enter your password, check Remember Password, and check Allow other clients to connect.

There have been times when a local port is taken by another user or another VNC session. In these rare cases, the recommended port forwarding won't work. To determine if a port is used, the Windows and Linux command,

   netstat -a

will list all used ports. In these cases, the tunnel has to be changed to 590M:ssh.gb.nrao.edu:590N where 590M is some unused port somewhere above 5900. And, whereever we have localhost:N in the above instructions, substitute localhost:M.

There have been times when a local port is taken by another user or another VNC session. In these rare cases, the recommended port forwarding won't work. To determine if a port is used, the Windows and Linux command,

   netstat -a

will list all used ports. In these cases, the tunnel has to be changed to 590m:ssh.gb.nrao.edu:590n where 590m is some unused port somewhere above 5900. And, whereever we have localhost:n in the above instructions, substitute localhost:m.

• Type in a different terminal on your local computer:
  
  vncviewer > display > open -- =localhost:N
  
  

• In a different terminal on your local computer, start "Chicken of the VNC":
  
  vncviewer
  
  
  • Within "Chicken of the VNC", go to: "Connection" and then "Open Connection"
  • Set Host to localhost, set Display to 0, enter your password, check Remember Password, and check Allow other clients to connect.
  • Hit the "Connect" button.
    
    

• Type in a terminal on your local computer:
  
  ssh -N -C -L 5900:titania.gbt.nrao.edu:590N YOURLOGIN@ssh.gb.nrao.edu &
  
  
• Type in a terminal on your local computer:
  
  vncviewer > display > open -- =localhost:N
  
  

• Type in a terminal on your local computer:
  
  ssh -N -C -L 5900:titania.gbt.nrao.edu:590N YOURLOGIN@ssh.gb.nrao.edu
  
  
• Type in a different terminal on your local computer:
  
  vncviewer > display > open -- =localhost:N
  
  

• • You can also run vncserver with color depth or size options: For example
    
    vncserver [ -geometry e.g. 1000x700 ] [ -depth 8 ]
    
    
  • These options allow you to specify an alternate screen geometry or color depth. The first number for the geometry is the screen width which we advise should be 2x wider than the size of your local monitor. Choose a screen height that is slightly smaller than the native height of your local monitor. Choose 8-bit color to speed up the transfer of displays in the VNC session.
  • Sometimes, it isn't necessary to start with VNC server with the = -depth= options since your viewer may assume defaults that might actually work better without this switch.

• • You can also run vncserver with color depth or size options: For example
    
    vncserver [ -geometry e.g. 2048x1024 ] [ -depth 8 ]
    
    
  • These options allow you to specify an alternate screen geometry or color depth. The first number for the geometry is the screen width which we advise should be 2x wider than the size of your local monitor. Choose a screen height that is 1024 or larger, so as to accomodate the typical observing applications. If you have a monitor that is more than 1024 pixels high, choose a screen height that is slightly smaller than the native height of your local monitor.
  • Choose 8-bit color to speed up the transfer of displays in the VNC session. Sometimes, it isn't necessary to start with VNC server with the -depth options since your viewer may assume defaults that might actually work better without this switch.

• • • Session – Host Name is ssh.gb.nrao.edu. (If ssh.gb.nrao.edu is already listed among the Saved Sessions, click on it and choose Load to place that name in the Host Name section of the window.)

• • • Session – Host Name is ssh.gb.nrao.edu. (If ssh.gb.nrao.edu is already listed among the Saved Sessions, click on it and choose Load to place that name in the Host Name section of the window.)

• • • Connection > SSH > Tunnels – Remove any previously used ports with the Remove button. For Source port enter 590N, where N is the VNC session number reported in the first PuTTY window (the VNC server). For Destination, enter titania.gbt.nrao.edu:590N Then choose Add, then Open.

• • • Connection > SSH > Tunnels – Remove any previously used ports with the Remove button. For Source port enter 590N, where N is the VNC session number reported in the first PuTTY window (the VNC server). For Destination, enter titania.gbt.nrao.edu:590N Then choose Add, then Open.

• • As Server, enter localhost:N, where N is the VNC session number, as always.

• • As Server, enter localhost:N, where N is the VNC session number, as always.

• Start up your observing applications immediately after contacting the operator. These usually include

      cleo
         open at least the 'Talk & Draw' windows, then any other cleo application you need.  You can use "Talk & Draw" to communicate with the operator during the run and after you have finished with the phone.
      astrid
      gbtidl, or other data reduction program to be used

• Start up your observing applications immediately after contacting the operator. These usually include
  
  cleo
  
  Open at least the 'Talk & Draw' windows, then any other cleo application you need. You can use Talk & Draw to communicate with the operator during the run and after you have finished with the phone.
  
  astrid
gbtidl
  
  Or another data reduction program to be used

For Mac users, "Chicken of the VNC" is a good VNC client and is available from http://sourceforge.net/projects/cotvnc..

For Mac users, "Chicken of the VNC" is a good VNC client and is available from http://sourceforge.net/projects/cotvnc.

• Type in a terminal on your local computer: ssh ssh.gb.nrao.edu
  • If you are not using an SSH agent, you will be asked to enter your NRAO Linux account username and password..

• Type in a terminal on your local computer:
  
  ssh ssh.gb.nrao.edu
  
  If you are not using an SSH agent, you will be asked to enter your NRAO Linux account username and password.

• In the terminal window on the remote (NRAO) computer, type at the Linux prompt: vncpasswd

• In the terminal window on the remote (NRAO) computer, type at the Linux prompt:
  
  vncpasswd
  
  

By default, you will be given TWM as a window manager for VNC sessions. If you would like KDE, you can perform the following steps:

By default, you will be given TWM as a window manager for VNC sessions. If you would like FVWM (recomended) or KDE, you can perform the following steps:

• Type in a terminal on your local computer: ssh ssh.gb.nrao.edu
  • If you are not using an SSH agent, you will be asked to enter your NRAO Linux account username and password..

• Type in a terminal on your local computer:
  
  ssh ssh.gb.nrao.edu
  
  If you are not using an SSH agent, you will be asked to enter your NRAO Linux account username and password.

• In the terminal window on the remote (NRAO) computer, type at the Linux prompt: mkdir ~/.vnc
  • If you have already used VNC in the past, this step is not necessary and you will get a message stating that the 'file' already exists. This is normal.
• At the Linux prompt, type: cp ~rmaddale/.vnc/xstartup_kde ~/.vnc/xstartup

• In the terminal window on the remote (NRAO) computer, type at the Linux prompt:
  
  mkdir ~/.vnc
  
  If you have already used VNC in the past, this step is not necessary and you will get a message stating that the 'file' already exists. This is normal.
• Select your desired window manager. If you want to use the fvwm window manager (recomended), at the Linux prompt, type:
  
  cp ~rmaddale/.vnc/xstartup_fvwm ~/.vnc/xstartup
  
  If you want to use the kde window manager, at the Linux prompt, type:
  
  cp ~rmaddale/.vnc/xstartup_kde ~/.vnc/xstartup
  
  

• In the PuTTY terminal window to ssh.gb.nrao.edu, log in to your NRAO Linux account..

• In the PuTTY terminal window to ssh.gb.nrao.edu, log in to your NRAO Linux account.

• Type in a terminal on your local computer: ssh ssh.gb.nrao.edu
  • If you are not using an SSH agent, you will be asked to enter your NRAO Linux account username and password..

• Type in a terminal on your local computer:
  
  ssh ssh.gb.nrao.edu
  
  If you are not using an SSH agent, you will be asked to enter your NRAO Linux account username and password.

• In the terminal window on the remote (NRAO) computer, type at the Linux prompt: ssh titania.gbt.nrao.edu
  • If you are not using an SSH agent, you will be asked to enter your NRAO Linux account username and password.
• At the Linux prompt on titania, type: vncserver
  • You can also run vncserver with color depth or size options: For example vncserver [ -geometry e.g. 1000x700 ] [ -depth 8 ]

• In the terminal window on the remote (NRAO) computer, type at the Linux prompt:
  
  ssh titania.gbt.nrao.edu :
  
  If you are not using an SSH agent, you will be asked to enter your NRAO Linux account username and password.
• At the Linux prompt on titania, type:
  
  vncserver
  
  
  • You can also run vncserver with color depth or size options: For example
    
    vncserver [ -geometry e.g. 1000x700 ] [ -depth 8 ]
    
    

• Type in a terminal on your local computer: vncviewer -Shared -via YOURLOGIN@ssh.gb.nrao.edu titania.gbt.nrao.edu:N

• Type in a terminal on your local computer:
  
     vncviewer -Shared -via YOURLOGIN@ssh.gb.nrao.edu titania.gbt.nrao.edu:N
  
  

• • • Type in a terminal on your local computer: ssh -N -C -L 590N:titania.gbt.nrao.edu:590N YOURLOGIN@ssh.gb.nrao.edu &
    • Type in a terminal on your local computer: vncviewer -Shared localhost:N
• The VNC Viewer window to titania will now appear. In this window you can start astrid, start cleo, open xterms, etc. almost as if you were sitting in front of a titania screen..

• • • Type in a terminal on your local computer:
      
      ssh -N -C -L 590N:titania.gbt.nrao.edu:590N YOURLOGIN@ssh.gb.nrao.edu &
      
      
    • Type in a terminal on your local computer:
      
      vncviewer -Shared localhost:N
      
      
• The VNC Viewer window to titania will now appear. In this window you can start astrid, start cleo, open xterms, etc. almost as if you were sitting in front of a titania screen.

• Type in a terminal on your local computer: = ssh -N -C -L 5900:titania.gbt.nrao.edu:590N YOURLOGIN@ssh.gb.nrao.edu &=
• Type in a terminal on your local computer: vncviewer > display > open -- localhost:N

• Type in a terminal on your local computer:
  
  ssh -N -C -L 5900:titania.gbt.nrao.edu:590N YOURLOGIN@ssh.gb.nrao.edu &
  
  
• Type in a terminal on your local computer:
  
  vncviewer > display > open -- =localhost:N
  
  

There have been times when a local port is taken by another user or another VNC session. In these rare cases, the recommended port forwarding won't work. To determine if a port is used, the Windows and Linux command, netstat -a, will list all used ports. In these cases, the tunnel has to be changed to 590M:ssh.gb.nrao.edu:590N where 590M is some unused port somewhere above 5900. And, whereever we have localhost:N in the above instructions, substitute localhost:M.

There have been times when a local port is taken by another user or another VNC session. In these rare cases, the recommended port forwarding won't work. To determine if a port is used, the Windows and Linux command,

   netstat -a

will list all used ports. In these cases, the tunnel has to be changed to 590M:ssh.gb.nrao.edu:590N where 590M is some unused port somewhere above 5900. And, whereever we have localhost:N in the above instructions, substitute localhost:M.

If you would like to check if you are already running a VNC Servers (really, there should be only one), use any terminal that is logged into an NRAO computer and type: ls ~YOURLOGIN/.vnc | grep .pid

If you would like to check if you are already running a VNC Servers (really, there should be only one), use any terminal that is logged into an NRAO computer and type:

   ls ~YOURLOGIN/.vnc | grep .pid

• In the PuTTY terminal window to ssh.gb.nrao.edu, log in to your NRAO Linux account..

• In the PuTTY terminal window to ssh.gb.nrao.edu, log in to your NRAO Linux account.

• Type in a terminal on your local computer: ssh ssh.gb.nrao.edu
  • If you are not using an SSH agent, you will be asked to enter your NRAO Linux account username and password..

• Type in a terminal on your local computer:
  
  ssh ssh.gb.nrao.edu
  
  If you are not using an SSH agent, you will be asked to enter your NRAO Linux account username and password.

• In the terminal window on the remote (NRAO) computer, type at the Linux prompt: ssh titania.gbt.nrao.edu
• Type: vncserver -kill :N where N is the VNC server number.

• In the terminal window on the remote (NRAO) computer, type at the Linux prompt:
  
  ssh titania.gbt.nrao.edu
  
  
• Type:
  
  vncserver -kill :N
  
  where N is the VNC server number.

Remote Observing on the GBT

Remote Observing on the GBT

FOR *APPROVED* PROJECTS ONLY

Permission to observe remotely must be explicitly granted by the Telescope Scheduler at least two weeks prior to the observing run. Permission will be granted based on the appropriateness of the project and the demonstrated experience of the observer. Guidelines for approved remote observing projects are as follows.

TOC: No TOC in "Observing.GbtRemoteObserving"

• Consult with the staff support astronomer at least two weeks prior to observing time.

Remote Observing Guidelines for Approved Projects

• Provide the staff support astronomer with your telephone contact numbers (work, home, and cell) and agree in advance your location during the observations.

Permission to observe remotely must be explicitly granted by Carl Bignell, the Telescope Scheduler, at least two weeks prior to the observing run. Permission will be granted based on the appropriateness of the project and the demonstrated experience of the observer. Guidelines for approved remote observing projects are as follows.

• Consult with the staff support astronomer at least two weeks prior to observing time.
• Provide the staff support astronomer with your telephone contact numbers (work, home, and cell) and agree in advance your location during the observations.

• Contact the telescope operator 30 minutes before the start of your setup time. The number to call is 304-456-2346 or the Operator's direct line at 304-456-2341. x2346 connects to a speaker phone and is the preferred number to use.

• We recommend VNC network displays of observing applications. Suggested VNC setup procedures are provided below.

• Start up your applications immediately after contacting the operator. These usually include

• Contact the telescope operator 30 minutes before the start of your setup time. The number to call is 304-456-2346 or the Operator's direct line at 304-456-2341. x2346 connects to a speaker phone and is the preferred number to use. Provide the operator with all the appropriate contact information in case they need to contact you during the run.
• We strongly recommend VNC network displays of observing applications. Suggested VNC setup procedures are provided below.
• Start up your observing applications immediately after contacting the operator. These usually include

open the 'status' and the 'Talk & Draw' windows (at least)

open at least the 'Talk & Draw' windows, then any other cleo application you need. You can use "Talk & Draw" to communicate with the operator during the run and after you have finished with the phone.

• At the start of your observing time, again call the telescope operator at 304-456-2346, who will put you on a speaker phone. The line should stay open at least through the setup period. (The backup line in case x2346 is busy is the Operator's direct line at 304-456-2341. This line does not have a speaker phone, however.)
• When your observing time starts and the operator gives you permission, you should use Astrid to load your configuration and start observing.

• At the start of your observing time, call the telescope operator at 304-456-2346, who will put you on a speaker phone. The line should stay open at least through the setup period. (The backup line in case x2346 is busy is the Operator's direct line at 304-456-2341. This line does not have a speaker phone, however.)

• When your observing time starts and the operator gives you permission, you should use Astrid to load your configuration and start observing.

VNC Setup Instructions

The example below uses the computer titania.gbt.nrao.edu for the VNC server. Titania is currently the computer usually available to host VNC sessions. As our computer infrastructure changes, this might not be always the case. You should always ask the operator for the name of the computer you should use and substitute that computer's name for titania's in the instructions below.

What is VNC (Virtual Network Connection)?

VNC comes with most Linux distributions and is easily set up. Mac and Windows users should download and install a VNC Viewer (e.g., Tight VNC, http://www.tightvnc.com).

VNC allows remote connections from a client computer to a server, creating a virtual desktop (desktop image) of the server screen on the client computer screen. The user of the client computer can work almost as if he or she were sitting in front of the screen of the remote computer. VNC continuously compresses and transfers screen shots from the server to the client which makes this a much quicker experience than normal X-forwarding, especially for complicated, line-drawn windows.

The example below uses the computer titania.gbt.nrao.edu for the VNC server. Titania is currently the computer usually available to host VNC sessions. Since this might not be always the case, you should ask the operator for the name of the computer you should actually use and substitute that computer's name in the following instructions.

Why is VNC Useful for GBT Remote Observing?

To set up a session at the remote machine (titania)

     ssh titania.gbt.nrao.edu
     vncserver
        If this is your first session ever on titania, you will now be
          asked which password should protect your future sessions ]
       Remember the number vncserver returns, e.g.: 
          New 'X' desktop is titania:3 --> N=3
       You can also run vncserver with color depth or size options: For example
          vncserver [ -geometry e.g. 1000x700 ] [ -depth 8 ]

To view the session on your local machine (work/home)

VNC allows the remote GBT observer to connect to a computer in the GBT control room (e.g. ariel, titania, naiad) from the observer's home/work machine in order to observe. Once the VNC session is set up, the remote observer can open astrid, cleo, gbtidl, etc. and perform other functions just as if he or she were actually in the control room sitting in front of the remote computer's screen.

Linux: vncviewer -via YOURLOGIN@ssh.gb.nrao.edu titania:N Replace "N" with the desktop number from the previous step and YOURLOGIN with the name of your NRAO account. Enter your normal gb password (unless you have ssh keys set up) Enter your vncserver password

If your Linux version does not support the -via option you might want to install Tight VNC (http://www.tightvnc.com) or use the following equivalent to -via: ssh -f -L 590N:titania:590N YOURLOGIN@ssh.gb.nrao.edu sleep 14400 vncviewer localhost:N Mac: ssh -f -L 590N:titania:590N YOURLOGIN@ssh.gb.nrao.edu sleep 14400 Set the number of seconds to sleep to be longer than your session ) vncviewer > display > open -- localhost:N Windows: * In Putty (or other SSH client): Session > Host name = ssh.gb.nrao.edu Session > Protocol = ssh Connection > Auto-login username = YOURLOGIN Connection > Tunnels > Remove previously used ports Add new Tunnel (Replace "N" with the desktop number from above): Source port = 590N Destination = titania:590N Start your normal GB SSH login

• • • Start VNCviewer with: localhost:N type your vncserver password

To stop the session, close your vncviewer and then execute:

     ssh titania.gbt.nrao.edu
     vncserver -kill :N

How Do I Get the Necessary Software?

VNC comes with most Linux distributions and is easily set up. Mac and Windows users should download and install a VNC Viewer.

How Do I Set up VNC?

If this is your first session ever with VNC, you need to setup a VNC server password and specify what window manager you would like.

How do I Provide a VNC Password?

Choose a password that is different from your NRAO Linux account password as you may later wish to share this password with others who can then observe your VNC session. For example, if you are having difficulties during a remote observing session, you might wish to share your VNC password with a Green Bank staff member who can access your virtual desktop and suggest solutions to your problems.

To create a VNC server password, you must log into an NRAO computer. The first steps for Linux and MacOS users is different than those for Windows users:

Once you are logged into the NRAO computer, and regardless of your remote computer:

• In the terminal window on the remote (NRAO) computer, type at the Linux prompt: vncpasswd
• Enter your chosen VNC server password. Remember, this password should be different from your NRAO Linux account password as it will be shared with support staff when you require assistance.

How Do I Set Up a Window Manager?

By default, you will be given TWM as a window manager for VNC sessions. If you would like KDE, you can perform the following steps:

Once you are logged into the NRAO computer, and regardless of your remote computer:

• In the terminal window on the remote (NRAO) computer, type at the Linux prompt: mkdir ~/.vnc
  • If you have already used VNC in the past, this step is not necessary and you will get a message stating that the 'file' already exists. This is normal.
• At the Linux prompt, type: cp ~rmaddale/.vnc/xstartup_kde ~/.vnc/xstartup

How Do I Establish a VNC Session?

IMPORTANT! Please do not start more than one VNC server at a time! There is only a limited total number of sessions and ports available at any time. Likewise, don't forget to end your VNC server session when you are finished observing. For instructions on ending your VNC server session, please read closing your VNC server session.

Each time you observe remotely with the GBT, you will need to follow these instructions.

To set up a session at the remote machine, you must first log into an NRAO computer. The first steps for Linux and MacOS users is different than those for Windows users:

Once you are logged into the NRAO computer, and regardless of your remote computer:

• In the terminal window on the remote (NRAO) computer, type at the Linux prompt: ssh titania.gbt.nrao.edu
  • If you are not using an SSH agent, you will be asked to enter your NRAO Linux account username and password.
• At the Linux prompt on titania, type: vncserver
  • You can also run vncserver with color depth or size options: For example vncserver [ -geometry e.g. 1000x700 ] [ -depth 8 ]
    • These options allow you to specify an alternate screen geometry or color depth. The first number for the geometry is the screen width which we advise should be 2x wider than the size of your local monitor. Choose a screen height that is slightly smaller than the native height of your local monitor. Choose 8-bit color to speed up the transfer of displays in the VNC session.
    • Sometimes, it isn't necessary to start with VNC server with the = -depth= options since your viewer may assume defaults that might actually work better without this switch.
  • If this is your first session in Green Bank, you will be asked which password should protect your future sessions. As noted above, choose a password that is different from your Linux account password as you may later wish to share this password with others who can then observe your VNC session. For example, if you are having difficulties during a remote observing session, you might wish to share your VNC password with a Green Bank staff member who can access your virtual desktop and suggest solutions to your problems.
• Once you have typed vncserver, the system will reply (e.g.) New 'titania:2 (USERNAME)' desktop is titania:2 In this case, your VNC session number is 2. Remember this number since you will need it later. In the instructions below, the VNC session number is designated as N.
• Leave this connection open to the server. Later, it will be used to kill processes on titania associated with the VNC session.

How Do I Start a VNC Viewer on My Local Machine?

You will need a VNC viewer in order to view the session on your local machine (work/home).

I Need Some Troubleshooting Information

There have been times when a local port is taken by another user or another VNC session. In these rare cases, the recommended port forwarding won't work. To determine if a port is used, the Windows and Linux command, netstat -a, will list all used ports. In these cases, the tunnel has to be changed to 590M:ssh.gb.nrao.edu:590N where 590M is some unused port somewhere above 5900. And, whereever we have localhost:N in the above instructions, substitute localhost:M.

If you would like to check if you are already running a VNC Servers (really, there should be only one), use any terminal that is logged into an NRAO computer and type: ls ~YOURLOGIN/.vnc | grep .pid

What Special Features Does the VNC Viewer Window Have?

• Depressing the left mouse button inside the main VNC Viewer window brings up a menu, allowing you, for example, to open another xterm.
• Minimizing a window - Click on the upper left part of a window.
• Resizing a window – Use the icon at the upper right of a window
• To configure your VNC Viewer, press F8 and a menu should appear

How Do I Close My VNC Session

IMPORTANT!!! If you stop using vncviewer but don't kill the server, the sessions stays alive. If you run vncviewer later (the next day for example) or from a different computer you can continue where you left off. There is however only a limited total number of sessions and ports available at any time. Unless you know you will be using the session again within a few hours, please do not leave a vncserver running more than is necessary. Also, please do not start more than one VNC server at a time.

To stop the session, close your vncviewer. You'll need a terminal window that is logged into an NRAO computer.

Once you are logged into the NRAO computer, and regardless of your remote computer:

• In the terminal window on the remote (NRAO) computer, type at the Linux prompt: ssh titania.gbt.nrao.edu
• Type: vncserver -kill :N where N is the VNC server number.

Any Additional VNC Resources?

A short guide to VNC for Window's users is available.

We would like to thank Joeri van Leeuwen (UBC), Tom Troland (U. Kentucky), and Jeff Mangum (NRAO CV) who kindly provided the entire content of these instructions. We appreciate the time they took to make VNC easier for all remote observers.

Version 1.2 May 8, 2006
Version 1.1 September 6, 2005
Version 1.0 January 28, 2005

If you stop using vncviewer but don't kill the server, the sessions stays alive. If you run vncviewer later (the next day for example) or from a different computer you can continue where you left off. There is however only a limited total number of sessions available at any time (as there is only a limited number of ports). Unless you know you will be using the session again within 24 hours, please do not leave a vncserver running more than is necessary.

Version 1.0 January 28, 2005 Version 1.1 Septembet 6, 2005 VErsion 1.2 May 8, 2006

%META:FILEATTACHMENT{name="FirstPutty.jpg" attr="h" comment="First Putty Window" date="1147882080" path="C:\Documents and Settings\ashelton\My Documents\My Pictures\Remote Observing\FirstPutty.jpg" size="60079" user="AmyShelton" version="1.1"}% %META:FILEATTACHMENT{name="FirstPuttyServer.jpg" attr="h" comment="First Putty Window - Server" date="1147882097" path="C:\Documents and Settings\ashelton\My Documents\My Pictures\Remote Observing\FirstPuttyServer.jpg" size="67530" user="AmyShelton" version="1.1"}% %META:FILEATTACHMENT{name="SecondPutty.jpg" attr="h" comment="Second Putty Window" date="1147882113" path="C:\Documents and Settings\ashelton\My Documents\My Pictures\Remote Observing\SecondPutty.jpg" size="59883" user="AmyShelton" version="1.1"}% %META:FILEATTACHMENT{name="SecondPuttyConfiguration.jpg" attr="h" comment="Second Putty Window - Configuration" date="1147882128" path="C:\Documents and Settings\ashelton\My Documents\My Pictures\Remote Observing\SecondPuttyConfiguration.jpg" size="51355" user="AmyShelton" version="1.1"}% %META:FILEATTACHMENT{name="SecondPuttyTunnel.jpg" attr="h" comment="Second Putty Window - Tunnel" date="1147882145" path="C:\Documents and Settings\ashelton\My Documents\My Pictures\Remote Observing\SecondPuttyTunnel.jpg" size="53520" user="AmyShelton" version="1.1"}% %META:FILEATTACHMENT{name="SecondPuttyTunnel2.jpg" attr="h" comment="Second Putty Window - Tunnel #2" date="1147882158" path="C:\Documents and Settings\ashelton\My Documents\My Pictures\Remote Observing\SecondPuttyTunnel2.jpg" size="53809" user="AmyShelton" version="1.1"}% %META:FILEATTACHMENT{name="Tunnel.jpg" attr="h" comment="Tunnel" date="1147882176" path="C:\Documents and Settings\ashelton\My Documents\My Pictures\Remote Observing\Tunnel.jpg" size="59013" user="AmyShelton" version="1.1"}% %META:FILEATTACHMENT{name="Viewer.jpg" attr="h" comment="VNC Viewer" date="1147882195" path="C:\Documents and Settings\ashelton\My Documents\My Pictures\Remote Observing\Viewer.jpg" size="15857" user="AmyShelton" version="1.1"}% %META:FILEATTACHMENT{name="ViewerPassword.jpg" attr="h" comment="Viewer Password Window" date="1147882214" path="C:\Documents and Settings\ashelton\My Documents\My Pictures\Remote Observing\ViewerPassword.jpg" size="14873" user="AmyShelton" version="1.1"}% %META:FILEATTACHMENT{name="ViewerSession.jpg" attr="h" comment="View Screen Shot" date="1147882233" path="C:\Documents and Settings\ashelton\My Documents\My Pictures\Remote Observing\ViewerSession.jpg" size="90865" user="AmyShelton" version="1.1"}% %META:FILEATTACHMENT{name="FirstPuttyKill.jpg" attr="h" comment="First Putty Window - Kill" date="1147882248" path="C:\Documents and Settings\ashelton\My Documents\My Pictures\Remote Observing\FirstPuttyKill.jpg" size="60855" user="AmyShelton" version="1.1"}% %META:FILEATTACHMENT{name="ROShort.pdf" attr="h" comment="Windows Short Instructions" date="1147882280" path="C:\Documents and Settings\ashelton\My Documents\ROShort.pdf" size="28322" user="AmyShelton" version="1.1"}%

FOR *APPROVED* PROJECTS ONLY

Permission to observe remotely must be explicitly granted by the Telescope Scheduler at least two

o Consult with the staff support astronomer at least two weeks prior to observing time.

• Consult with the staff support astronomer at least two weeks prior to observing time.

o Provide the staff support astronomer with your telephone contact numbers (work and home) and agree in advance your location during the observations.

• Provide the staff support astronomer with your telephone contact numbers (work, home, and cell) and agree in advance your location during the observations.

o Prepare observing scripts in advance (Astrid which encompasses Turtle, config tool and gfm)

• Prepare ASTRID observing scripts in advance

o Contact the telescope operator 30 minutes before the start of your setup time.

• Contact the telescope operator 30 minutes before the start of your setup time. The number to call is 304-456-2346 or the Operator's direct line at 304-456-2341. x2346 connects to a speaker phone and is the preferred number to use.

o We recommend VNC network displays of observing applications. Suggested VNC setup procedures (courtesy Joeri van Leeuwen) are provided below. Or, you may want to download and use VNCTool, a CLEO application. See http://www.gb.nrao.edu/~rmaddale/GBT/CLEOManual/applications/vncTool.html for documentaion on VNCTool and to download VNCTool.

• We recommend VNC network displays of observing applications. Suggested VNC setup procedures are provided below.

o Start up your applications immediately after contacting the operator. These usually include

• Start up your applications immediately after contacting the operator. These usually include

o At the start of your observing time, call the telescope operator at 304-456-2346, who will put you on a speaker phone. The line should stay open at least through the setup period. (The backup line in case x2346 is busy is the Operator's direct line at 304-456-2341. This line does not have a speaker phone, however.)

• At the start of your observing time, call the telescope operator at 304-456-2346, who will put you on a speaker phone. The line should stay open at least through the setup period. (The backup line in case x2346 is busy is the Operator's direct line at 304-456-2341. This line does not have a speaker phone, however.)

o When your observing time starts and the operator gives you permission, you should use Astrid to load your configuration and start observing.

• When your observing time starts and the operator gives you permission, you should use Astrid to load your configuration and start observing.

VErsion 1.2 May 8, 2006

VNC setup procedures (courtesy Joeri van Leeuwen) are provided below.

VNC setup procedures (courtesy Joeri van Leeuwen) are provided below. Or, you may want to download and use VNCTool, a CLEO application. See http://www.gb.nrao.edu/~rmaddale/GBT/CLEOManual/applications/vncTool.html for documentaion on VNCTool and to download VNCTool.

Astrid

astrid

load your configuration script in config_tool. You may also start GO or ask the operator to run it on your behalf (this is often more efficient for remote access).

you should use Astrid to load your configuration and start observing.

experience than normal X-forwarding. VNC comes with most Linux distributions and is easily set up:

experience than normal X-forwarding.

VNC comes with most Linux distributions and is easily set up. Mac and Windows users should download and install a VNC Viewer (e.g., Tight VNC, http://www.tightvnc.com).

The example below uses the computer titania.gbt.nrao.edu for the VNC server. Titania is currently the computer usually available to host VNC sessions. Since this might not be always the case, you should ask the operator for the name of the computer you should actually use and substitute that computer's name in the following instructions.

ssh to titania

ssh titania.gbt.nrao.edu

[ if this is your first session ever on titania, you will now be

If this is your first session ever on titania, you will now be

remember the number vncserver returns, e.g.:

Remember the number vncserver returns, e.g.:

you can also run vncserver with color depth or size options:

You can also run vncserver with color depth or size options: For example

(replace "N" and "YOURLOGIN")

enter your normal gb password (unless you have ssh keys set up) enter your vncserver password off you go.

Replace "N" with the desktop number from the previous step and YOURLOGIN with the name of your NRAO account. Enter your normal gb password (unless you have ssh keys set up) Enter your vncserver password

If your Linux version does not support the -via option you might want to install Tight VNC (http://www.tightvnc.com) or use the following equivalent to -via: ssh -f -L 590N:titania:590N YOURLOGIN@ssh.gb.nrao.edu sleep 14400 vncviewer localhost:N

( download a vncviewer for mac )

( set the number of seconds to sleep to be longer than your session )

Set the number of seconds to sleep to be longer than your session )

off you go.

( download putty and tightvnc ) * In Putty:

* In Putty (or other SSH client):

Add new Tunnel (Replace "N" with the desktop number from above):

Press Add. Press Open Use your normal GB SSH login

Start your normal GB SSH login

• • • In VNCviewer open:

• • • Start VNCviewer with:

off you go

To stop the session broadcast ssh to titania vncserver -kill :X

If your Linux version does not support the -via option you might want to install TightVNC? or use the Mac setup:

To stop the session, close your vncviewer and then execute:

ssh -f -L 590N:titania:590N YOURLOGIN@ssh.gb.nrao.edu sleep 14400 vncviewer localhost:N

ssh titania.gbt.nrao.edu vncserver -kill :N

If you stop using vncviewer the sessions stays alive, so if you run vncviewer later (the next day for example) you can continue where you quit. There is however only a limited total number of sessions available at any time (as there is only a limited number of ports) so do kill your session unless you know you will be using the session again within a few days.

If you stop using vncviewer but don't kill the server, the sessions stays alive. If you run vncviewer later (the next day for example) or from a different computer you can continue where you left off. There is however only a limited total number of sessions available at any time (as there is only a limited number of ports). Unless you know you will be using the session again within 24 hours, please do not leave a vncserver running more than is necessary.

Version 1.1 Septembet 6, 2005

o Prepare observing scripts in advance (config, GO and/or Scheduling Blocks to be executed with Turtle [if you are a beta-tester])

o Prepare observing scripts in advance (Astrid which encompasses Turtle, config tool and gfm)

o Start up your applications (except for GO) immediately after contacting

o Start up your applications immediately after contacting

gfm and/or iards config_tool dish, gbtidl, or other data reduction program to be used

Astrid gbtidl, or other data reduction program to be used

%META:TOPICINFO{author="CarlBignell" date="1106940360" format="1.0" version="1.1"}% %META:TOPICPARENT{name="GbtObservingPolicies"}%

   cleo
      open the 'status' and the 'Talk & Draw' windows (at least)
   gfm and/or iards
   config_tool
   dish, gbtidl, or other data reduction program to be used

     ssh to titania
     vncserver
     [ if this is your first session ever on titania, you will now be
       asked which password should protect your future sessions ]
     remember the number vncserver returns, e.g.:
       New 'X' desktop is titania:3 --> N=3
     you can also run vncserver with color depth or size options:
     vncserver [ -geometry e.g. 1000x700 ] [ -depth 8 ]

     (replace "N" and "YOURLOGIN")
     Linux:
        vncviewer -via YOURLOGIN@ssh.gb.nrao.edu titania:N
        enter your normal gb password (unless you have ssh keys set up)
        enter your vncserver password
        off you go.
     Mac: