ord-data

Getting the Data

The datasets live under data/ and are stored with Git LFS. LFS reads are redirected to the Hugging Face mirror via .lfsconfig, so dataset objects are fetched from Hugging Face's CDN rather than from GitHub's shared (and limited) LFS bandwidth. This is automatic — you do not need to configure anything.

Option 1: Clone the repository

git clone https://github.com/open-reaction-database/ord-data.git

With Git LFS installed, this pulls every dataset object from the Hugging Face mirror and gives you the full Git history with the data in place.

Option 2: Download only the data (a subset, or without Git history)

pip install -r scripts/requirements.txt
python scripts/download_from_huggingface.py

The script mirrors the data/ directory from the Hugging Face dataset into your local checkout. Pass --allow-pattern 'data/4d/*.pb.gz' (repeatable) to download only a subset, or --output-dir <path> to write somewhere other than the repository root. To skip LFS entirely during the clone and fetch the data afterward:

GIT_LFS_SKIP_SMUDGE=1 git clone https://github.com/open-reaction-database/ord-data.git
cd ord-data
python scripts/download_from_huggingface.py

You can also browse and download datasets directly from the Hugging Face dataset page.

For how this LFS / Hugging Face mirror setup works (and what it means for contributors), see Git LFS and the Hugging Face mirror below.

Data Manipulation

The ord-data repository contains the Open Reaction Database (ORD) in Google's Protobuf binary format, which is stored in the data directory. Currently, all the data are stored in e.g. *.pb.gz format (compressed Protobuf binary files) for the sake of efficiency. The user can convert the data into human readable text format, *.pb.txt.

# import requirements
from ord_schema.message_helpers import load_message, write_message
from ord_schema.proto import dataset_pb2

# load the binary ord file
dataset = load_message("input_fname.pb.gz", dataset_pb2.Dataset)
# save the ord file as human readable text
write_message(dataset, "output_fname.pbtxt")

We can also convert ORD data into JSON format.

# import requirements
import json

from ord_schema.message_helpers import load_message, write_message
from ord_schema.proto import dataset_pb2
from google.protobuf.json_format import MessageToJson

input_fname = "sample_file.pb.gz"
dataset = load_message(
    input_fname,
    dataset_pb2.Dataset,
)

# take one reaction message from the dataset for example
rxn = dataset.reactions[0]
rxn_json = json.loads(
    MessageToJson(
        message=rxn,
        including_default_value_fields=False,
        preserving_proto_field_name=True,
        indent=2,
        sort_keys=False,
        use_integers_for_enums=False,
        descriptor_pool=None,
        float_precision=None,
        ensure_ascii=True,
    )
)

print(f"We have converted the {input_fname} to JSON format shown as below, \n{rxn_json}")

Git LFS and the Hugging Face mirror

Dataset files under data/ are stored with Git LFS. Clone and fork traffic was dominating GitHub's shared LFS bandwidth quota, so the repository is configured to keep that traffic off GitHub while leaving GitHub authoritative for the data:

• Reads come from Hugging Face. .lfsconfig points lfs.url at the Hugging Face mirror, so clones and forks fetch LFS objects from HF's CDN instead of GitHub.
• GitHub remains the source of truth. LFS objects are always written to GitHub (storage there is fine; only download bandwidth was the problem), and the mirror workflow copies them to Hugging Face after every merge to main. Hugging Face is purely a read replica — every object is always retrievable from GitHub.
• LFS is scoped to data/ (see .gitattributes). A new dataset staged at the repository root is an ordinary Git file, so submissions can be pushed from a fork with no LFS configuration; the submission workflow turns the file into an LFS object when it moves it into data/.

For contributors

• Submitting a new dataset: nothing special is required — stage your file at the repository root and open a PR (see CONTRIBUTING.md and the Submission Workflow).

• Editing a file that already lives under data/ from a fork: that file is an LFS object, so point LFS uploads at your own fork once before pushing (you cannot write to the canonical repository's LFS store):

  git config lfs.pushurl https://github.com/<your-username>/ord-data.git/info/lfs
  

For maintainers (CI)

Freshly pushed objects are not on the Hugging Face mirror until the post-merge mirror job runs, so CI and the mirror override the read endpoint back to GitHub at runtime (git config lfs.url …):

• validation.yml pulls only each matrix shard's objects from GitHub, sparsely, instead of the whole dataset in every job.
• submission.yml reads from GitHub so fork and branch submissions are validated before their bytes reach Hugging Face.
• huggingface_mirror.yml reads the to-be-mirrored objects from GitHub.

Contributing

Please see the Submission Workflow documentation. Make sure to review the license and terms of use.

Maintainer notes

Skipping the Update submission step

The submission workflow's Update submission step runs process_dataset.py --update --cleanup to assign reaction/dataset IDs and timestamps to newly submitted files and rewrite them to the canonical on-disk format. For maintainer PRs that touch dataset files but should not be re-processed this way — e.g., format conversions or mass migrations of already-finalized data — apply the skip-update-submission label to the PR. The validation side of the workflow still runs.