PolyChron
PolyChron is a GUI application designed to facilitate the analysis and archiving of archaeological dating evidence. It supports the management of both relative and absolute dating evidence, enabling users to build multiple chronological models within a Bayesian modelling framework.
Key features include:
-
Graph-theoretic representations of stratigraphic sequences, which users can explore and edit via an intuitive point-and-click interface.
-
The ability to input prior knowledge, such as:
-
Groupings of archaeological contexts
-
Identification of residual or intrusive samples
-
Relationships between different groups
-
Using this information, PolyChron constructs a hierarchical Bayesian model and uses an MCMC (Markov Chain Monte Carlo) algorithm to estimate the posterior calendar ages of samples.
All outputs, including raw digital data (as input by the user), model representations, results, and supplementary notes are saved locally. This ensures the full site archive is preserved for future use and long-term archiving with the Archaeology Data Service.
Documentation
For full documentation including a userguide and developer reference, please see bryonymoody.github.io/PolyChron.
Installation
PolyChron is a GUI application written in python using tkinter.
If you are familiar with python, polychron can be installed using pip, and Graphviz must be installed on your system.
Requirements
polychron is a Python package which uses Graphviz for graph rendering.
Before you install polychron, you should ensure a compatible version of python is available (with pip, tkinter and ideally venv) and should install graphviz.
-
3.9-3.13
-
- which you can install manually) or through your system package manager:
- Linux
# debian, ubuntu, etc. sudo apt install graphviz # fedora, RHEL, Rocky, etc. sudo dnf install graphviz
- macOS
# using brew (if installed) brew install graphviz
- Windows
# using chocolatey (if installed) choco install graphviz --no-progress -y
- Linux
- which you can install manually) or through your system package manager:
-
- Although
tkinteris part of the Python3 standard library, it is not included in all pre-compiled python distributions. If you encounter errors related to importingtkinter, you may need to install it. - linux
# e.g. for Ubuntu/Debian apt-get install python3-tk
- macOS
# using brew (if python was installed with brew) brew install python-tk
- Although
Installing polychron from PyPI
polychron is a Python package and released versions of polychron can be installed from PyPI using pip, ideally in a virtual environment.
python3 -m pip install polychron
Installing polychron from Source
It is recommended to use a Python virtual environment (venv) or similar for installations of polychron from source, for example:
# Create and activate a venv
python3 -m venv .venv
source .venv/bin/activate
polychron can be installed from source using pip and git, using the latest development version or specific releases.
# Install the current development version
python3 -m pip install git+https://github.com/bryonymoody/PolyChron.git
# Install a tagged release or branch, in this case v0.2.1
python3 -m pip install git+https://github.com/bryonymoody/PolyChron.git@v0.2.1
Or by cloning the git repository from GitHub and installing into the current python environment.
git clone https://github.com/bryonymoody/PolyChron
cd PolyChron
python3 -m pip install .
[!TIP] If you are installing PolyChron from source as a developer, consider using an editable installation (
-e/--editable) and installing thedev,docandtestextras.python3 -m pip install -e .[dev,doc,test]
Usage
With PolyChron installed in the current python environment, it can be launched using any of the following:
# via the executable script
polychron
# or by running the installed polychron module
python3 -m polychron
License
PolyChron is released under the GPLv3 license
Contributing
If you would like to contribute towards PolyChron, please see the contributing guidelines.
Linting
Linting is handled using ruff which can be installed as part of the dev extras.
Ruff can then be invoked using:
python3 -m ruff check
# or
ruff check
Formatting
Automatic code formatting is handled using ruff which can be installed as part of the dev extras.
Ruff can then be invoked using:
python3 -m ruff fromat
# or
ruff format
This can be automatically applied on commit through pre-commit hooks
Testing
Tests are implemented using pytest, which can be installed as part of the test optional dependencies via:
python3 -m pip install .[test]
Once installed, unit tests can be executed via pytest from the root directory
python3 -m pytest
# or
pytest
Building Documentation
Documentation is built using mkdocs and some extensions.
Documentation building dependencies are included in the doc optional dependencies group.
They can be installed into the current python environment along with polychron using pip:
python3 -m pip install -e .[doc]
Once installed, documentation can be generated and viewed via a local webserver using:
python3 -m mkdocs serve
# or just
mkdocs serve
Or a static html version can be built into _site using:
python3 -m mkdocs build
# pass --no-directory-urls if you wish to view local .html files without a web server
python3 -m mkdocs build --no-directory-urls
Metadata
Release files for polychron 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| polychron-0.2.1.tar.gz | 2.8 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| polychron-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.4 MB
Release files / polychron-0.2.1.tar.gz
| Download URL | polychron-0.2.1.tar.gz |
|---|---|
| Size | 2.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
68aa268cbcb2301acbc0a4a00b99ca2ad772712cd83b264c83c95115aa188d6f
|
|
BLAKE2b-256 checksum How to use checksums |
904596a8e1cc593249d6eaec9cce49637f55b3026ceb5cdf5184860602be4929
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2025.
Transparency logRelease files / polychron-0.2.1-py3-none-any.whl
| Download URL | polychron-0.2.1-py3-none-any.whl |
|---|---|
| Size | 1.6 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
52f2ba23478f5a241df21d98db3c11f4bce72bf1fb6739ad73b0fed4b43b1122
|
|
BLAKE2b-256 checksum How to use checksums |
ef788b089ea8c5173a6ecbe81d5718c39b9f003984181b8d5825ab4571ea0b76
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2025.
Transparency log