Compute Resources


The Shared Compute Cluster (SCC) has four login nodes: through One of them,, is dedicated to BUMC users. Details of the compute cluster are available here (link). Additionally, resources dedicated to BUMC users will soon be expanded to include the current RubySky cluster hardware.




The primary login node for LinGA users is SCC4. This node complies with dbGaP data security requirements. As such it can only be accessed from within BU networks. If you’re connecting remotely you first need to set up a VPN connection with BU networks. Alternatively you can first ssh to¬† or and then either ssh to scc4 or start an interactive session using qrsh/qlogin.

Usage (Different from LinGA)

Documentation for running jobs on SCC is published on IS&Ts Research Computing webpage and most of the operation is very similar to that of LinGA’s current environment. Please reference the Running Jobs on the SCC page for details, but note the following differences between LinGA and SCC4.

  • Project Specification
    The documentation in Running Jobs does not state a project requirement. On SCC4 and for LinGA project related jobs, you must change your group and submit the job using “-P <projectname>”
    [user@scc4 ~]$ qsub -P linga_admin example.qsub 

  • Job Runtime Limits
    On SCC a 12-hour runtime limit is enforced on all jobs, unless specified explicitly. A runtime limit can be specified using “-l h_lt=<hh:mm:ss>”
    [user@scc4 ~]$ qsub -l h_rt=24:00:00 -P linga_admin example.qsub

  • Daily CPU Hour Limits
    In an effort to share the SCC resource effectively, projects are provided 1000 hours of CPU per year. This limit can be increased to 12000 hours (or further, with justification) by request.

  • Default Project
    On SCC, each LinGA user that did not have a default project specified was assigned to a new default project (lingadp). Users cannot run jobs using the lingadp project and must either choose a new default group (email: or manually change projects and specify the project each time. 

    To determine current group:
    [user@scc4 ~]$ id -ng

    To change groups use “newgrp <groupname>”
    [user@scc4 ~]$ newgrp linga_admin