Open Community Runtime

Announcement

• OCR v1.1.0 released ! Links

Goal

The goal of the Open Community Runtime (OCR) project is to propose, implement, and evaluate a runtime framework and API that:

• Is representative of future execution models
• Can express large amounts of parallelism in a task-based model
• Can explicitly capture logical dependences and data movements
• Can be targeted by multiple high-level programming systems
• Can be mapped efficiently on to future extreme scale platforms
• Is available as an open-source testbed

Audience

In its current state, the project aims to release a prototype implementation of a reference API by September 2015, while making work-in-pogress transparently visible at the git location mentioned below. As such, the project is mostly geared towards early adopters among application developers who would like to provide feedback on the runtime model and API, higher-level language/models implementers who are interested in determining if their model can map to OCR, hardware developers who would like to experiment with OCR as a proxy for an exascale runtime, and runtime developers who are interested in using and/or contributing to OCR.

Value of the OCR project

The OCR project is creating an application building framework that explores new methods of high-core-count programming with an initial focus on HPC applications. The project aims to explore, among other things:

• Expressiveness: how can application programmers express their applications in a hardware-agnostic manner; i.e.: how can they express the intrinsic parallelism and locality in an application as opposed to the mapping on to a particular kind of hardware?
• Scheduling and data placement: what tuning hints and adaptive heuristics can enable locality-aware scheduling and data-placement on an exascale system?
• Introspection: how can a runtime system improve its execution characteristics by monitoring itself?
• Resiliency: how can a runtime system deal with failures in an exascale system?

The OCR project aims to propose a low-level API to address the challenges of exascale programming and is meant to be targeted by higher-level abstractions. Early implementations of higher-level abstractions that target OCR include the CnC programming model, the HTA programming model, the RStream compiler, the Habanero-C library, and the Habanero-UPC++ library.

Timeline

The OCR software is available under the BSD open source license.

• Initial unveiling at SC 2012
• v0.8 was introduced at SC 2013 with a significant rewrite to increase modularity and enable more community participation
• v0.9 will be presented at SC 2014 with several updates (including support for execution on distributed-memory clusters)
• v1.0 released on May 31, 2015
• v1.0.2 released on April 5, 2016
• v1.1.0 released on April 5, 2016

Quick Start Instructions

To get the OCR v1.1.0 release:

1. Download the OCR v1.1.0 Specification
2. Clone the repository using git

   git clone https://xstack.exascale-tech.com/git/public/ocr.git ocr
   git clone https://xstack.exascale-tech.com/git/public/apps.git apps
   

3. Follow OCR installation instructions located under ocr/INSTALL.make

To get the latest, in development, version of OCR:

1. Clone the repository using git

   git clone https://xstack.exascale-tech.com/git/public/ocr.git
   cd ocr
   git checkout dev/master
   

2. Follow OCR installation instructions located under ocr/INSTALL.make

Links

• Quick-start web page to download, build, and run the OCR code on some sample applications
• Getting started with OCR
• OCR v1.1.0 Specification
• OCR Documentation: Specification and guides/how-to documents are online, along with best-practices information
• OCR Source Code: The OCR source code is available as a git repository to be cloned
• Applications: Many applications and common HPC kernels are included in the git code repository
• Productivity Environments: Support for productivity environments, including CNC, RStream, Habanero C, and HTA
• Legacy Support: Legacy C environment support and an MPI implementation are included for easier code migration
• Mailing lists are available here