Skip to content

usnistgov/corr

Repository files navigation

CoRR logo

CoRR NIST Public Instance Slack Reathedocs Youtube Playlist License

CoRR Sumatra Integration Status CoRR ReproZip Integration Status CoRR CDE Integration Status CoRR PFHub Integration Status CoRR Noworkflow Integration Status CoRR Maestrowf Integration Status CoRR Aiida Integration Status CoRR Panda Integration Status

Overview

The Cloud of Reproducible Records (CoRR) is a web platform for storing and viewing metadata and data associated with simulation records for reproducibility and beyond. It is designed as a gateway for execution management tools that aim in capturing software executions. The need of those records for recalls, reproducibility, education, provenance and posterity is so critical now more than ever.

The platform is composed of five components. A database component which stores the meta-data about the diverse entities in relationship within the platform. An api component which identifies and allow software management tools to interact with the platform. A cloud component dedicated for the frontend component access to the meta-data and records. A storage component that handles non meta-data files management.

The CoRR platform is programming language agnostic, recording style and process independent. Instead of focusing in these specifics, the platform comes at a higher level by providing a unified gateway for execution management tools. They are the ones who handle these specifics. The platform focuses on networking records and scientists. Thus, making the long term survival of research reproducibility its core goal.

A CoRR instance is composed of five micro-services. The database micro-service which is a mongodb database combined with a python shared library corrdb for distributed entities models to the other micro-services. The api micro-service (corrapi) which is a restfull service that is the interface dedicated to execution management tools. The cloud micro-service which is a second restfull service (corrcloud) dedicated to the view micro-service (corrview) which is the frontend exposed to web users. Finally a nginx service takes care of unifying the access to the corrcloud, corrapi and corrview. Information on how to launch a CoRR instance is provided in LAUNCH.mdHow to use and also in videos (click on the corr youtube badge above.).

Citation