This means you need to remove your interactive jobs that were tied to your nx session.
To resolve this:
If you are running into an error starting a new RCE job due to too many CPU's in use, you need to terminate your jobs that were tied to an old nx session. The commands that are highlighted below should enable you to remove these old jobs.
2) Run this command to see your jobs: condor_q -pool cod6-head.priv $USER -- Schedd: HMDC.firstname.lastname@example.org : <10.0.0.251:38284> ID OWNER SUBMITTED RUN_TIME ST PRI SIZE CMD 5098.0 cperry 9/10 10:46 0+00:00:26 R 0 0.0 mathematica-14086.
3) Remove your job, using the ID from the last command:
The RCE is free to use for qualified individuals in the pursuit of social science research, within certain limits.
If your needs exceed the capacities of the shared RCE environment, we can work with you to establish dedicated RCE resources for your exclusive use. If you are planning a large project, please contact us prior to your grant application so that we can assist in budgetary estimation.
If your question is not answered here on our RCE support website, you may also find the information you need on our User Services website, which covers topics relating to the HMDC RCE and other services provided by the IQSS Technology Services group.
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.
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).
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:
To configure your user account such that every time you connect to the RCE, some action is performed:
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).
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.
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.