Search Documentation

Search Documentation


MyOSC now supports multi-factor authentication (MFA).

User opt-in

Users can now opt-in to using multi-factor authentication in MyOSC.

On a user's profile page, there will be a button 'enable duo mfa'

Screen Shot 2021-06-17 at 3.06.37 PM.png


We have licensed applications such as ansys, abaqus, and Schrodinger. These applications have a license server with a limited number of licenses, and you need to check out the licenses when you use the software each time. One problem is that the job scheduler, Slurm, doesn't communicate with the license server. As a result, a job can be launched even there are not enough licenses available, and it fails due to insufficient licenses. 

Service agreement

  • Used to group projects together.
    • A PI may have multiple service agreements, but it is preferred to limit the amount to one.
  • Reference billing information.
  • Allocate credits and discounts. 
  • Apply custom rates.
  • Set up automatically (must have a service agreement to have a project).
    • If you have had a project with OSC, you already have a service agreement.

Globus is a reliable, high-performance file transfer platform allowing users to transfer large amounts of data seamlessly between systems. It aims to make transfers a "click-and-forget" process by setting up configuration details in the background and automating fault recovery.  

Globus can be used for both file transfers between OSC and:

Owens, Pitzer

Trinity represents a novel method for the efficient and robust de novo reconstruction of transcriptomes from RNA-seq data.

Availability and Restrictions

The following versions of Trinity are available on OSC clusters:


This document is obsoleted and kept as a reference to previous Owens programming environment. Please refer to here for the latest version.

Securely transferring files at OSC

Files containing personal health information (PHI) must be encrypted when they are stored (at rest) and when they are transferred between networked systems (in transit).

Transferring files securely to OSC involves understanding which commands/applications to use and which directory to use.

Keep protected data in proper locations

Providing access to protected data locations

PHI data transferred to OSC will be set with permissions to restrict access to only project users. Project users are determined by group membership. For example, project PEX1234 has a protected data location at /fs/ess/PEX1234 and only users in the group PEX1234 may access data in that dir.

See access control list how-to for more information on how it works.


As we migrate to Slurm from Torque/Moab, there will be necessary software environment changes.

Decommissioning old MVAPICH2 versions

Old MVAPICH2 including mvapich2/2.1mvapich2/2.2 and its variants do not support Slurm very well due to its life span, so we will remove the following versions: