Build a searchable database for Correlator data in the pyerrors format.
Find a file
Justus Kuhlmann 54006f46f5
Some checks failed
Mypy / mypy (push) Failing after 3s
Pytest / pytest (3.12) (push) Failing after 1s
Pytest / pytest (3.13) (push) Failing after 2s
Pytest / pytest (3.14) (push) Failing after 2s
Ruff / ruff (push) Failing after 2s
comment retruns of extract t0 and t1
2026-02-12 16:24:40 +01:00
.github/workflows Merge pull request 'test/mypy' (#11) from test/mypy into develop 2025-12-02 12:45:07 +01:00
corrlib comment retruns of extract t0 and t1 2026-02-12 16:24:40 +01:00
examples add example toml-file 2025-11-20 17:14:12 +01:00
tests assert more vars in config 2025-12-04 14:46:16 +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.