Build a searchable database for Correlator data in the pyerrors format.
Find a file
Justus Kuhlmann 7275fdd4f3
All checks were successful
Mypy / mypy (pull_request) Successful in 1m11s
Pytest / pytest (3.12) (pull_request) Successful in 1m28s
Pytest / pytest (3.13) (pull_request) Successful in 1m17s
Pytest / pytest (3.14) (pull_request) Successful in 1m12s
Ruff / ruff (pull_request) Successful in 1m3s
remove unnecessary output when results are empty
2026-04-08 17:28:54 +02:00
.github/workflows remove pip cache 2026-03-20 17:25:44 +01:00
corrlib remove unnecessary output when results are empty 2026-04-08 17:28:54 +02:00
examples add example toml-file 2025-11-20 17:14:12 +01:00
tests add test for project alias lookup 2026-03-23 18:26:17 +01: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

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.