Build a searchable database for Correlator data in the pyerrors format.

Python 100%

Find a file

Justus Kuhlmann 50fb204cb1 All checks were successful Mypy / mypy (push) Successful in 1m11s Details Pytest / pytest (3.12) (push) Successful in 1m22s Details Pytest / pytest (3.14) (push) Successful in 1m15s Details Pytest / pytest (3.13) (push) Successful in 1m14s Details Ruff / ruff (push) Successful in 1m2s Details HOTFIX: enable r_start, r_sto, r_step params for t0 and t1		2026-05-08 11:32:04 +02:00
.github/workflows	remove pip cache	2026-03-20 17:25:44 +01:00
corrlib	HOTFIX: enable r_start, r_sto, r_step params for t0 and t1	2026-05-08 11:32:04 +02:00
examples	add example toml-file	2025-11-20 17:14:12 +01:00
tests	stramline, add tests for path_format check	2026-05-06 20:10:45 +02:00
.gitignore	add .coverage	2025-12-01 19:09:05 +01:00
pyproject.toml	add mypy	2025-12-02 12:36:03 +01:00
README.md	add README	2024-06-21 14:14:02 +00:00
TODO.md	Finish first version of cache	2025-05-13 09:45:00 +00:00
uv.lock	add mypy	2025-12-02 12:36:03 +01:00

README.md

Pyerrors backlog

With this tool, we aim at making it easy to backlog correlation functions that can be read with pyerrors. This is done in a reproducible way using datalad. In principle, a dataset is created, that is automatically administered by the backlogger, in which data from differnt projects are held together. Everything is catalogued by a searchable SQL database, which holds the paths to the respective measurements. The original projects can be linked to the dataset and the data may be imported using wrapper functions around the read methonds of pyerrors.