CERN-SSCCS Collaboration Framework

Draft: Collaboration Through Open Science and Open Source Infrastructure

Author
Affiliation

SSCCS Foundation

Published

August 5, 2026

Abstract

This draft outlines a proposed collaboration between the SSCCS Foundation and CERN. SSCCS is an independent, non-profit, public-good science foundation whose work follows the principle that has guided CERN since its founding: science is a public good, and knowledge should remain open. The document presents what SSCCS brings, proposes a concrete first engagement on the ROOT TTree I/O bottleneck in production analysis workflows, and outlines how the collaboration would proceed through CERN’s established open-source channels. This draft is the basis for discussion.

Code
Proposals
Other Formats

Institutional Alignment

SSCCS is an independent foundation operating under the SSCCS Charter, with a primary mission of advancing open structural computing. It is not accountable to any state, party, or corporation, and releases its core work under Apache 2.0. The Charter permits commercial or revenue-generating activities when consistent with its objects, but the foundation’s mission remains public-good oriented.

The proposed collaboration stays within CERN’s stated direction: “unleash the potential of open source for scientific and technological progress beyond high-energy physics.” SSCCS works precisely in that domain: open hardware on RISC-V, structural computing primitives in the Tagma coordinate space, and exhaustive verification tooling.

What SSCCS Brings

The following foundational assets are under active development, with key primitives already validated on silicon simulators and production-grade reference implementations in progress:

Asset Relevance
ExaVerif (exhaustive RISC‑V verification, 33.5M encodings in 29 ms) Exhaustive, deterministic verification for RISC‑V and radiation‑tolerant systems
Chton (zero‑serialization IO materialization) Storage format equals the memory layout; the read path has no serialization step
Tagma (hash‑less coordinate space; decoder ~300 gates) Direct coordinate addressing with a minimal decoder, suited to low‑power and constrained environments
Apache 2.0 release Unencumbered integration with open‑hardware and scientific software ecosystems

A good problem-solving starting point

The ROOT TTree I/O Bottleneck

The Problem

A well-documented pain point in high‑energy physics analysis is ROOT TTree I/O performance. In representative production workflows, hundreds of thousands of singular read requests (totaling several GB) can consume 14 hours of wall-clock time—an average throughput of tens of KB/s. Despite ongoing I/O modernization efforts (e.g., RNTuple), the structural cost remains: each read must traverse branch hierarchies and deserialize data. The root cause is not raw disk bandwidth; it is per‑request overhead, page cache thrashing from small fragmented reads, and cache invalidation under multithreaded access patterns.

The SSCCS Approach

SSCCS addresses this by replacing the read path with coordinate addressing. An event becomes a coordinate resolved to a direct offset—with no branch table, no index scan, and no hash. Filters become spatial operations over coordinate ranges, and Chton materializes the coordinate space onto media with the storage format equal to the memory layout.

The Offer to CERN

ROOT’s I/O interface stays exactly as it is. Researchers keep the TTree API they already know, and their existing analysis scripts run unchanged. Underneath, mapped data is served from the coordinate space instead of the disk. The ecosystem is not broken; only the interior is replaced.

Proposed Demonstration

We propose a bounded demonstration on CMS Open Data (MiniAOD) that reproduces the documented access pattern and reports the comparison against the ROOT baseline—establishing the collaboration on the basis of a working result, demonstrated on CERN’s own access pattern without disturbing the production ecosystem.

Status

This is a draft framework document for initial discussion. It outlines the alignment, technical assets, and a proposed starting point for collaboration. The document will be updated as the discussion develops.