Is there temp or scratch storage available?

Yes, the top-level /scratch directory on our batch nodes is the same as using /tmp. On our interactive nodes, /scratch is a separate 1TB shared storage space.

Top level scratch space is world-writeable and -readable (Unix 1777 permissions). User created directories are only owner writeable/readable (1700) or owner/group (2770) if you are a member of a research group.

In either case, if you need several gigabytes of storage, please request a project directory.

Please note:

  • Do not store any Confidential Information in scratch/temp.
  • Any files written to scratch/temp will be deleted after 2-4 weeks.
  • Do not use the scratch space for permanent storage.
  • Each server has a separate scratch/temp. If you need shared space for a distributed batch job, please request a project directory.

How do I use compressed data with R?

R supports two primary ways of accessing compressed data. This allows you to keep your data files on disk compressed saving space, and often time (since the file I/O saved by compression is often more expensive than the cpu cycles it uses).

If you are storing your data in native format, simply use the compress option of save:

tst.df=as.data.frame(cbind(1:10,2:11)) # just some testing data save(tst.df,file="test.Rbin", compress=T) # save a compressed R file

You can use load as normal, to read the compressed files:


To access any other kind of file with compression, simply use gzfile("") around the file name:

write.table(tst.df,gzfile("test.dat.gz")) # write a compressed file read.table(gzfile("test.dat.gz"),row.names=1)# read it back in

Files compressed using the gzfile method can also be compressed and uncompressed using the UNIX gzip and gunzip commands (respectively).

My Stata batch job keeps running even after a fatal error!

When running a Stata .do file on the batch cluster via condor_submit_util, you have to add some additional arguments in order to get your job to stop when Stata encounters an unrecoverable error (which is probably the behavior you want).

The command line below runs Stata with the example file my_dofile.do:

@condor_submit_util --executable /usr/local/bin/stata-se --arguments '-b /my_dofile.do' --noinput

How do I automate actions when connecting to the RCE?

To configure your user account such that every time you connect to the RCE, some action is performed:

  1. Write a script that performs the desired action. The scripting languages available in the RCE include BASH, (/bin/bash), multiple versions of Python (/usr/bin/python) and Perl (/usr/bin/perl).

  2. Copy this script to the directory ~/.rce/startup with the command cp [scriptname] ~/.rce/startup/. If the directory does not exist, create it with the command mkdir -p ~/.rce/startup.

  3. Make sure the permissions on your script permit execution; to ensure that this is the case, run the command chmod +x ~/.rce/startup/[scriptname].

Your script is run every time you connect to the RCE.

Note: Be sure to test your script; a misbehaving script can prevent you from being able to connect to the RCE! In particular, your script must not require any keyboard input or other interaction with the user; it will not be able to communicate with you while it is running, and you will not be able to connect to the RCE while your script sits waiting for input.

Firefox or Thunderbird won't start!

The error Firefox is already running usually indicates that you must remove lock files before you can launch Firefox. To resolve this problem:

  • If you are working inside the HMDC RCE navigate to ApplicationsRCE UtilitiesClear Firefox Locks or Clear Thunderbird Locks. Then, try launching Firefox or Thunderbird again.

  • If you are not working inside the HMDC RCE, type the following command via a terminal to delete the Firefox lockfiles: rm -f ~/.mozilla/firefox/*.default/{lock,.parentlock}

What are the technical specifications of the RCE?

The RCE is divided into three parts:

  1. Login nodes: These servers provide a graphical or command line interface to the meat and potatoes of the RCE, the Interactive and Batch cluster. It operates like a personal desktop environment, but is not meant for running jobs.
  2. Interactive cluster: Run memory intensive jobs on these COD (compute-on-demand) nodes that require user interaction.
    • Size: 8 homogenous servers
    • CPU: Intel Xeon E5_2630 with 12 cores (24 counting hyper-threading) @ 2.3 Ghz
    • Memory: 250 GB each (2 TB total)
  3. Batch cluster: For jobs that do not require babysitting, and speed is king.
    • Size: 5 homogenous servers
    • CPU: Intel Xeon E5_2690 with 16 cores (32 counting hyper-threading) @ 2.9 Ghz
    • Memory: 125 GB each (1 TB total)
    • Each batch job process is allocated 1 CPU core and 4GB of RAM

Also see running multi-threaded jobs for more information.

Disk space options are as follows:

  • Home directories are allocated 500 MB. We do not increase this space, but you may request a project directory.
  • Project directories are available in storage sizes suited to each particular researcher. Please contact us to request storage space. Fees may be applicable to sizes over a certain amount. To read about using your storage space, please see:
  • 1 TB of shared scratch space is available to all users on our interactive cluster. Top level scratch space is world-writeable and -readable (Unix 1777 permissions). User created directories are only owner writeable/readable (1700) or owner/group (2770) if you are a member of a research group. Do not use the scratch space for permanent storage.

Why can't I connect to login.hmdc.harvard.edu?

We have retired the login.hmdc.harvard.edu name in favor of the other name for the Kennedy RCE login nodes, kennedy.fas.harvard.edu. If you are a KSG user you can login to kennedy.fas.harvard.edu. These nodes are exclusively for KSG students, staff and faculty.

Why does my screen lock frequently? Can I disable screen lock?

The RCE is a service that is remotely accessible, and many users work with sensitive data. Since we cannot guarantee the security of the physical environment around the user's computer, we are required to follow the Harvard information security policy for application availability which indicates that the screen lock timeout should "only be a few minutes."

The Harvard policy mandating screen lock is HEISP 2.6: http://security.harvard.edu/book/26-limit-application-availability-time

How do I copy/paste from a RCE terminal?

If you are running a RCE desktop session from a Windows client, you are probably used to using ctrl+c for copying and ctrl+v for pasting. Terminals remap these functions to shift+ctrl+c and shift+ctrl+v, respectively. The ctrl key is used for specific operations, such as terminating command-line operations (ctrl+c). You can also right-click in the terminal to copy and paste.

How do I stop windows from jumping to the foreground?

The default window behavior in the RCE uses the focus-follows-mouse model, in which the user selects windows by merely pointing at them, and the selected window jumps to the foreground.  To change this behavior go to:

Applications → RCE Utilities → Change Windows Focus Behavior

The focus policy change is immediate.