LogoLogo
LogoLogo
  • The Barbara K. Ostrom (1978) Bioinformatics and Computing Facility
  • Computing Resources
    • Active Data Storage
    • Archive Data Storage
    • Luria Cluster
      • FAQs
    • Other Resources
  • Bioinformatics Topics
    • Tools - A Basic Bioinformatics Toolkit
      • Getting more out of Microsoft Excel
      • Bioinformatics Applications of Unix
        • Unix commands applied to bioinformatics
        • Manipulate NGS files using UNIX commands
        • Manipulate alignment files using UNIX commands
      • Alignments and Mappers
      • Relational databases
        • Running Joins on Galaxy
      • Spotfire
    • Tasks - Bioinformatics Methods
      • UCSC Genome Bioinformatics
        • Interacting with the UCSC Genome Browser
        • Obtaining DNA sequence from the UCSC Database
        • Obtaining genomic data from the UCSC database using table browser queries
        • Filtering table browser queries
        • Performing a BLAT search
        • Creating Custom Tracks
        • UCSC Intersection Queries
        • Viewing cross-species alignments
        • Galaxy
          • Intro to Galaxy
          • Galaxy NGS Illumina QC
          • Galaxy NGS Illumina SE Mapping
          • Galaxy SNP Interval Data
        • Editing and annotation gene structures with Argo
      • GeneGO MetaCore
        • GeneGo Introduction
        • Loading Data Into GeneGO
        • Data Management in GeneGO
        • Setting Thresholds and Background Sets
        • Search And Browse Content Tab
        • Workflows and Reports Tab
        • One-click Analysis Tab
        • Building Network for Your Experimental Data
      • Functional Annotation of Gene Lists
      • Multiple Sequence Alignment
        • Clustalw2
      • Phylogenetic analysis
        • Neighbor Joining method in Phylip
      • Microarray data processing with R/Bioconductor
    • Running Jupyter notebooks on luria cluster nodes
  • Data Management
    • Globus
  • Mini Courses
    • Schedule
      • Previous Teaching
    • Introduction to Unix and KI Computational Resources
      • Basic Unix
        • Why Unix?
        • The Unix Tree
        • The Unix Terminal and Shell
        • Anatomy of a Unix Command
        • Basic Unix Commands
        • Output Redirection and Piping
        • Manual Pages
        • Access Rights
        • Unix Text Editors
          • nano
          • vi / vim
          • emacs
        • Shell Scripts
      • Software Installation
        • Module
        • Conda Environment
      • Slurm
    • Introduction to Unix
      • Why Unix?
      • The Unix Filesystem
        • The Unix Tree
        • Network Filesystems
      • The Unix Shell
        • About the Unix Shell
        • Unix Shell Manual Pages
        • Using the Unix Shell
          • Viewing the Unix Tree
          • Traversing the Unix Tree
          • Editing the Unix Tree
          • Searching the Unix Tree
      • Files
        • Viewing File Contents
        • Creating and Editing Files
        • Manipulating Files
        • Symbolic Links
        • File Ownership
          • How Unix File Ownership Works
          • Change File Ownership and Permissions
        • File Transfer (in-progress)
        • File Storage and Compression
      • Getting System Information
      • Writing Scripts
      • Schedule Scripts Using Crontab
    • Advanced Utilization of IGB Computational Resources
      • High Performance Computing Clusters
      • Slurm
        • Checking the Status of Computing Nodes
        • Submitting Jobs / Slurm Scripts
        • Interactive Sessions
      • Package Management
        • The System Package Manager
        • Environment Modules
        • Conda Environments
      • SSH Port Forwarding
        • SSH Port Forwarding Jupyter Notebooks
      • Containerization
        • Docker
          • Docker Installation
          • Running Docker Images
          • Building Docker Images
        • Singularity
          • Differences from Docker
          • Running Images in Singularity
      • Running Nextflow / nf-core Pipelines
    • Python
      • Introduction to Python for Biologists
        • Interactive Python
        • Types
          • Strings
          • Lists
          • Tuples
          • Dictionaries
        • Control Flow
        • Loops
          • For Loops
          • While Loops
        • Control Flows and Loops
        • Storing Programs for Re-use
        • Reading and Writing Files
        • Functions
      • Biopython
        • About Biopython
        • Quick Start
          • Basic Sequence Analyses
          • SeqRecord
          • Sequence IO
          • Exploration of Entrez Databases
        • Example Projects
          • Coronavirus Exploration
          • Translating a eukaryotic FASTA file of CDS entries
        • Further Resources
      • Machine Learning with Python
        • About Machine Learning
        • Hands-On
          • Project Introduction
          • Supervised Approaches
            • The Logistic Regression Model
            • K-Nearest Neighbors
          • Unsupervised Approaches
            • K-Means Clustering
          • Further Resources
      • Data Processing with Python
        • Pandas
          • About Pandas
          • Making DataFrames
          • Inspecting DataFrames
          • Slicing DataFrames
          • Selecting from DataFrames
          • Editing DataFrames
        • Matplotlib
          • About Matplotlib
          • Basic Plotting
          • Advanced Plotting
        • Seaborn
          • About Seaborn
          • Basic Plotting
          • Visualizing Statistics
          • Visualizing Proteomics Data
          • Visualizing RNAseq Data
    • R
      • Intro to R
        • Before We Start
        • Getting to Know R
        • Variables in R
        • Functions in R
        • Data Manipulation
        • Simple Statistics in R
        • Basic Plotting in R
        • Advanced Plotting in R
        • Writing Figures to a File
        • Further Resources
    • Version Control with Git
      • About Version Control
      • Setting up Git
      • Creating a Repository
      • Tracking Changes
        • Exercises
      • Exploring History
        • Exercises
      • Ignoring Things
      • Remotes in Github
      • Collaborating
      • Conflicts
      • Open Science
      • Licensing
      • Citation
      • Hosting
      • Supplemental
Powered by GitBook

MIT Resources

  • https://accessibility.mit.edu

Massachusetts Institute of Technology

On this page
  • Accessing Luria
  • Connecting to Luria
  • Data Storage
  • Transferring data to and from Luria
  • Software Packages
  • Running jobs
  • Training Session

Was this helpful?

Export as PDF
  1. Computing Resources

Luria Cluster

PreviousArchive Data StorageNextFAQs

Last updated 8 days ago

Was this helpful?

Luria.mit.edu is a Linux cluster built in 2017, with the intent of providing computing resources for life sciences workloads for the Koch Cancer Research Institute and affiliated labs and DLCs at MIT.

It has 2272 cores, across 57 nodes:

Nodes
RAM

c1-9

128GB

c10

192GB

c11-40

96GB

b1-16

768GB or 384GB

Head node

64GB

Nodes
CPU Cores
CPU Model

c1-4

32 cores

Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz

c5-40

16 cores

Intel(R) Xeon(R) CPU E5620 @ 2.40GHz

b1-16

96 cores

Intel(R) Xeon(R) Gold 6240R CPU @ 2.40GHz or 5220R CPU @ 2.20GHz

Head node

32 cores

Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz

Accessing Luria

To request a Luria account, please email to from your MIT email account with the following information:

  • Your lab affiliation.

  • What kind of work you are looking to accomplish on the Luria cluster.

  • Whether you have previous experiences in Linux and cluster computing.

Connecting to Luria

Visual Studio Code

Keep in mind that mounting your storage server over SMB only gives you access to the files in your lab's storage account and files in your home directory's ~/data folder, not files directly inside of your home directory.

You can then open any folder or workspace on Luria using by going to File > Open and edit it straight in Visual Studio Code.

SecureCRT

Enter your Kerberos password when prompted.

Windows / Linux/ MacOS Terminal

  • Run: ssh <your-kerberos-username>@luria.mit.edu

  • Enter your MIT Kerberos password when prompted.

Data Storage

Each user on Luria will have at least two storage areas: a home directory and a project directory. Both are backed up daily.

Home Directory

Each user has a home directory. The home directory is intended to save commonly used scripts, environment configuration files, and your own software. A standard user account has a storage quota of 10GB in home directory. Please do not store large data file under your home directory as it can fill up the space quickly.

Project Directory (~/data)

In your home directory, there is usually a symbolic link called data which points to your storage servers. A symbolic link (symlink) is a file that points to a different location. Symbolic links are useful for saving space, since instead of having a large directory stored into a location, such as your luria home, you can use a symbolic to point to that directory on a resource with more abundant storage.

Programs will automatically follow the symbolic link and behave as if it was actually the directory. Symlinks also serve as shortcuts to different locations in the filesystem. For example, the symbolic link called data in your homes point to your directory in your lab's storage share. This is probably one of the following:

  1. /home/<username>/data -> /net/bmc-lab2/data/lab/<lab-name>/<username>

  2. /home/<username>/data -> /net/bmc-pub14/data/<lab-name>/users/<username>

Please do not delete the data symbolic link. The project directory is intended to save all your data which resides on either bmc-pubX or bmc-labX storage servers.

Your home directory also has five hidden directories: .local, .R, .singularity, .conda, and .jupyter. These directories are specifically named and required by their respective programs to store files, configurations, images, and packages. Since these can grow quite large, these directories are linked to your storage server.

Starting in February 2024, these directories point to the following hidden directories:

  • /home/<username>/.singularity -> /home/<username>/data/.singularity

  • /home/<username>/.conda -> /home/<username>/data/.conda

  • /home/<username>/.jupyter -> /home/<username>/data/.jupyter

  • /home/<username>/.local -> /home/<username>/data/.local

  • /home/<username>/.R -> /home/<username>/data/.R

For older accounts, these directories may look somewhat different, for example:

  • /home/<username>/.singularity -> /home/<username>/data/singularity

  • /home/<username>/.conda -> /home/<username>/data/conda

  • /home/<username>/.jupyter -> /home/<username>/data/jupyter

  • /home/<username>/.local -> /home/<username>/data/local

  • /home/<username>/.R -> /home/<username>/data/R

Disk quota exceeded

If your home directory exceeds the 20G quota, you will receive the error "Disk quota exceeded" when writing to your home directory. If this happens, you should examine which directories/files take most of the space using the du command, and then move those large directories/files to your project directory ~/data located on the storage server.

$ du -shc $(ls -A)

Data Storage Cleanup and Compression

While computing on Luria is free, data storage is charged at $100/TB/year. To reduce the operational cost and better utilize the storage server, we recommend you check your data periodically - removing data that are no longer needed and compressing files that you will not need for a while. Here is an example command to compress all fastq files in the current directory and sub-directories that are older than 180 days. Please remember running it through either a batch script or interactive login to a compute node.

$ find . -name \*.fastq -mtime +180 | parallel -j16 gzip -v {}

Data Storage Archival

We don't offer tiered storage. We don't use the term cold storage as our all storage servers are active. If you have data that you don't need for a while, we can do TSM archive on MIT storage and then delete the data from our storage server. Archived data is stored in MIT TSM archive, and is no longer accessible from our cluster luria.mit.edu as well as our storage servers. If you need the data back available to luria and our storage servers, we can retrieve it from MIT TSM archive. The MIT archive is a free service, but will require two hours of our labor to retrieve it at a rate of $90/hr.

Transferring data to and from Luria

Using SCP

  • Secure Copy or SCP is a means of securely transferring computer files between a local and a remote host or between two remote hosts.

  • It is based on the Secure Shell (SSH) protocol.

  • The term SCP refers both to the protocol and the program.

  • The command line scp is one of the most common SCP program and implements the SCP protocol to transfer files.

  • The syntax of the scp command is the same as the syntax of the cp command:

Copying file(s) to luria

# copying file `myfile.txt` from your local machine
# to your home directory in luria
scp myfile.txt <user>@luria.mit.edu:~/myfile.txt

# copying folder `myfolder` from your local machine
# to your home directory in luria
scp -r myfolder <user>@luria.mit.edu:~/

Copying file(s) from luria

# copying file `myfile.txt` from luria to
# your local machine
scp user@luria.mit.edu:~/myfile.txt myfile.txt

Transferring Files Using Jupyter Notebook

Software Packages

module

module avail

While module helps you to locate software that has been loaded into LMOD, many packages installed on Luria are not configured in this way, or may be included with other packages. If a package that you are looking for doesn't show up using module , you can run the locate command to search the filesystem for packages by name.

For example, to find out if tabix is installed, run the command locate tabix. The result should show that the command tabix is available under samtools. You can then run module load samtools/1.3 to have tabix in your environment.

Software Installation

Running jobs

Slurm

Luria uses the Slurm scheduler in order to manage jobs. In order to submit a job to run on the cluster compute nodes, you will need to create a batch script for Slurm and then submit it to the scheduler. For more information, please see our separate article on Slurm.

Training Session

You must be connected to the if you are not connected to MITNet or the MIT Secure Wi-Fi.

Unfortunately, the most recent versions of Visual Studio Code's Remote-SSH plugin no longer support operating systems with older versions of glibc, which includes Luria. There's no easy way around this besides to a version from before March 2025, or by changing your workflow.

If you still want to use VSCode but do not wish to downgrade it, you can , access your storage files in VSCode through your mounted folder, and manually SSH into Luria instead of using the Remote-SSH plugin by typing ssh <your username>@luria.mit.edu into the VSCode Terminal.

To connect to Luria using Visual Studio Code, follow the instructions at When you reach the step "Connect to Host", use <your-kerberos-username>@luria.mit.edu as your host. Enter your Kerberos password when prompted.

After successfully connecting, go to the VS Code top bar, press Terminal, then New Terminal . This will open a remote shell on the Luria cluster to run commands on.

SecureCRT is available to download from To create a connection using SecureCRT, click Quick Connect, then fill in the following fields:

The Windows Terminal is available to download from the If you do not wish to download it, you can use the built-in Windows PowerShell to run the following commands. Linux and MacOS come with a terminal and SSH client built-in.

Each lab has a storage quota in the project directory. When the storage quota is exceeded for your lab, you will not be able to add more data to your storage server. As mentioned above, you will then need to do data storage cleanup and compression to free up spaces. In addition, you can send a request to to increase your storage quota with a cost object provided and/or do TSM archival of your folder(s).

You can upload and download files from the Jupyter notebook interface via your browser. Please follow .

Luria uses module to manage software and its versions, (see ). Please note that not all software/versions available on rous are installed on luria. To get a list of software packages and versions, run

See .

The Integrated Genomics and Bioinformatics core at MIT (IGB) is offering a hands-on introductory session covering Linux usage and cluster computing using KI/BioMicro computational resources. This training session is targeted to users who are new to Linux and/or cluster computing. It is currently offered every 6 weeks, and registration fee is managed using iLabs. If you are interested in the next training session or one-on-one training, please email for details.

luria-help@mit.edu
MIT VPN
downgrading VSCode
mount your lab's storage over SMB
this website.
as shown here
IS&T's website.
Microsoft app store.
luria-help@mit.edu
the instructions at this page
Managment of Software Packages with module
Installation
luria-help@mit.edu
Quick Connect settings for SecureCRT