Search Documentation

Search Documentation

Owens

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.

Owens

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:

Gateway

OSC clients who are affiliated with Ohio State can deploy their own endpoint on a server using OSU subscriptions. Please follow the steps below:

Manage users on a project

The PI of a project can manage the users on their projects. Note, that PIs are not automatically added as authorized users under their project(s).

Managing users on the project includes inviting, adding and removing users to the project as well as increasing a user's privileges on a project so that they can assist with the management of it.

Owens, Pitzer

This article discusses memory tuning strategies for VASP.

Data Distribution

Typically the first approach for memory sensitive VASP issues is to tweak the data distribution (via NCORE or NPAR). The information at https://www.vasp.at/wiki/index.php/NPAR covers a variety of machines. OSC has fast communications via Infiniband. 

Owens, Pitzer

This article focuses on debugging strategies for C/C++ codes, but many are applicable to other languages as well.

Rubber Duck Debugging

This approach is a great starting point. Say you have written some code, and it does not do what you expect it to do. You have stared at it for a few minutes, but you cannot seem to spot the problem.

Ascend
Beginning April 30, 2025, all College of Medicine (CoM) projects without a separate MOU established with OSC will be limited to running exclusively on the Ascend cluster, specifically on the nextgen partition. All CoM jobs run on Ascend’s nextgen partition at zero cost, with priority scheduling.
Pitzer

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

Pitzer

In late 2018, OSC installed 260 Intel® Xeon® 'Skylake' processor-based nodes as the original Pitzer cluster. In September 2020, OSC installed additional 398 Intel® Xeon® 'Cascade Lake' processor-based nodes as part of a Pitzer Expansion cluster.

Pages