Cited by 33Scientific Computing and Data ManagementResearch Data Management PracticesSoftware Engineering Techniques and Practices

Collective knowledge: organizing research projects as a database of reusable components and portable workflows with common interfaces

Open access
Fursin, Grigori·2021·Philosophical Transactions of the Royal Society A: Mathematical, Physical and Engineering Sciences

Abstract

This article provides the motivation and overview of the Collective Knowledge Framework (CK or cKnowledge). The CK concept is to decompose research projects into reusable components that encapsulate research artifacts and provide unified application programming interfaces (APIs), command-line interfaces (CLIs), meta descriptions and common automation actions for related artifacts. The CK framework is used to organize and manage research projects as a database of such components. Inspired by the USB ‘plug and play’ approach for hardware, CK also helps to assemble portable workflows that can automatically plug in compatible components from different users and vendors (models, datasets, frameworks, compilers, tools). Such workflows can build and run algorithms on different platforms and environments in a unified way using the customizable CK program pipeline with software detection plugins and the automatic installation of missing packages. This article presents a number of industrial projects in which the modular CK approach was successfully validated in order to automate benchmarking, auto-tuning and co-design of efficient software and hardware for machine learning and artificial intelligence in terms of speed, accuracy, energy, size and various costs. The CK framework also helped to automate the artifact evaluation process at several computer science conferences as well as to make it easier to reproduce, compare and reuse research techniques from published papers, deploy them in production, and automatically adapt them to continuously changing datasets, models and systems. The long-term goal is to accelerate innovation by connecting researchers and practitioners to share and reuse all their knowledge, best practices, artifacts, workflows and experimental results in a common, portable and reproducible format at cKnowledge.io . This article is part of the theme issue ‘Reliability and reproducibility in computational science: implementing verification, validation and uncertainty quantification in silico ’.

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.1098/rsta.2020.0211

Cites

17 of 17 references verified0 citation errors · 0 not checkable

Statistics

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • Versioning of data, model, and code is required to ensure robustness and reproducibility.

    “as well as versioning of data, model, and code to ensure robustness and reproducibility [7], [32], [39].”

    From Machine Learning Operations (MLOps): Overview, Definition, and Architecture (2023) · cites this paper as [39]

    In §6 (p. 13), the paper says a lack of versioning made CK workflows difficult to keep stable and bug-free, and describes a platform intended to version and test components and workflows. That supports the general link between versioning and reliability, but it does not state that versioning each of data, models, and code is required to ensure robustness and reproducibility. (LLM, conf=0.82)

    Experimental — accuracy not yet measured

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

The self-check needs the paper’s full text.

Cites

Flagged first, then by citations

Research works printed but not linked: 4

  1. [1][1] ACM Pilot demo 'Collective Knowledge: packaging and sharing'. https://youtu.be/DIkZxraTmGM . -
  2. [21][21] LPIRC: low-power image recognition challenge. https://rebootingcomputing.ieee.org/lpirc . -
  3. [53][53] Vijay Janapa Reddi, Christine Cheng, David Kanter, Peter Mattson, Guenther Schmuelling, Carole-Jean Wu, Brian Anderson, Maximilien Breughe, Mark Charlebois, William Chou, Ramesh Chukka, Cody Coleman, Sam Davis, Pan Deng, Greg Diamos, Jared Duke, Dave Fick, J. Scott Gardner, Itay Hubara, Sachin Idgunji, Thomas B. Jablin, Jeff Jiao, Tom St. John, Pankaj Kanwar, David Lee, Jeffery Liao, Anton Lokhmotov, Francisco Massa, Peng Meng, Paulius Micikevicius, Colin Osborne, Gennady Pekhimenko, Arun Tejusve Raghunath Rajan, Dilip Sequeira, Ashish Sirasao, Fei Sun, Hanlin Tang, Michael Thomson, Frank Wei, Ephrem Wu, Lingjie Xu, Koichi Yamada, Bing Yu, George Yuan, Aaron Zhong, Peizhao Zhang, and Yuchen Zhou. MLPerf Inference Benchmark. https:// arxiv.org/abs/1911.02549 , 2019. - · arXiv
  4. [57][57] Matei Zaharia, Andrew Chen, Aaron Davidson, Ali Ghodsi, Sue Ann Hong, Andy Konwinski, Siddharth Murching, Tomas Nykodym, Paul Ogilvie, Mani Parkhe, Fen Xie, and Corey Zumar. Accelerating the Machine Learning Lifecycle with MLflow. IEEE Data Eng. Bull. , 41:39-45, 2018.

Cited by

Sorted by citations

Authors
Fursin, G.
Affiliations
cTuning foundation and cKnowledge SAS
Corresponding author
Fursin, Grigori
Venue
Philosophical Transactions of the Royal Society A: Mathematical, Physical and Engineering Sciences
Published
2021-03-29
Volume
379
Issue
2197
Pages
20200211-20200211
ISSN
  • 1364-503X (ISSN-L)
  • 1471-2962
OpenAlex
W3096672856
Cited by
33
References
17
Citations by year
2026: 1 · 2025: 5 · 2024: 4 · 2023: 4 · 2022: 10 · 2021: 9
FWCI
5.76
Type
journal article
Language
en
Open access
Locations
  • Philosophical Transactions of the Royal Society A Mathematical Physical and Engineering Sciences (publishedVersion)
  • PubMed (publishedVersion)
  • arXiv (Cornell University) (submittedVersion)
  • arXiv (Cornell University)
Topics
  • Social Sciences › Decision Sciences › Information Systems and Management › Scientific Computing and Data Management
  • Physical Sciences › Computer Science › Information Systems › Research Data Management Practices
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
Keywords
reusable components, auto-tuning, hardware-software co-design, reproducibility

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review