Science Score: 44.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
✓CITATION.cff file
Found CITATION.cff file -
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
○DOI references
-
○Academic publication links
-
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (14.2%) to scientific vocabulary
Repository
Prototype software for manipulating DAGs
Basic Info
- Host: GitHub
- Owner: bryonymoody
- License: gpl-3.0
- Language: Python
- Default Branch: main
- Size: 5.95 MB
Statistics
- Stars: 1
- Watchers: 2
- Forks: 0
- Open Issues: 101
- Releases: 0
Metadata Files
README.md
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
sh # debian, ubuntu, etc. sudo apt install graphviz # fedora, RHEL, Rocky, etc. sudo dnf install graphviz - macOS
sh # using brew (if installed) brew install graphviz - Windows
pwsh # 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
bash # e.g. for Ubuntu/Debian apt-get install python3-tk - macOS
sh # 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.
bash
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:
```bash
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.
```bash
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.0
python3 -m pip install git+https://github.com/bryonymoody/PolyChron.git@v0.2.0 ```
Or by cloning the git repository from GitHub and installing into the current python environment.
bash
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.
bash 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:
```bash
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:
```bash 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:
```bash 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:
bash
python3 -m pip install .[test]
Once installed, unit tests can be executed via pytest from the root directory
```bash 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:
bash
python3 -m pip install -e .[doc]
Once installed, documentation can be generated and viewed via a local webserver using:
```bash python3 -m mkdocs serve
or just
mkdocs serve ```
Or a static html version can be built into _site using:
```bash 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 ```
Owner
- Login: bryonymoody
- Kind: user
- Repositories: 1
- Profile: https://github.com/bryonymoody
Citation (CITATION.cff)
cff-version: 1.2.0
title: PolyChron
message: "If you use this software, please cite it using the metadata from this file. For more details on the underlying research, please see the references section."
type: software
authors:
- given-names: Bryony
family-names: Moody
email: "bryony.moody@sheffield.ac.uk"
affiliation: The University of Sheffield
orcid: "https://orcid.org/0009-0005-8601-3164"
- given-names: Peter
family-names: Heywood
email: "p.heywood@sheffield.ac.uk"
affiliation: The University of Sheffield
orcid: "https://orcid.org/0000-0001-9277-8394"
- given-names: Shreyan
family-names: Ghosh
email: "shreyanghosh27@gmail.com"
affiliation: The University of Sheffield
repository-code: "https://github.com/bryonymoody/PolyChron"
# doi:
license: GPL-3.0
references:
- type: "thesis"
authors:
- family-names: Moody
given-names: Bryony
orcid: "https://orcid.org/0009-0005-8601-3164"
title: "Semi-Automation of Bayesian Chronology Construction Using a Graph-Theoretic Approach"
url: "https://etheses.whiterose.ac.uk/id/eprint/33387/"
date-released: 2023-05-01
institution:
name: "University of Sheffield"
GitHub Events
Total
- Issues event: 137
- Delete event: 43
- Issue comment event: 31
- Member event: 2
- Push event: 185
- Pull request review comment event: 2
- Pull request review event: 7
- Pull request event: 83
- Fork event: 1
- Create event: 47
Last Year
- Issues event: 137
- Delete event: 43
- Issue comment event: 31
- Member event: 2
- Push event: 185
- Pull request review comment event: 2
- Pull request review event: 7
- Pull request event: 83
- Fork event: 1
- Create event: 47
Issues and Pull Requests
Last synced: 10 months ago
All Time
- Total issues: 112
- Total pull requests: 44
- Average time to close issues: about 1 month
- Average time to close pull requests: 11 days
- Total issue authors: 1
- Total pull request authors: 4
- Average comments per issue: 0.04
- Average comments per pull request: 0.16
- Merged pull requests: 30
- Bot issues: 0
- Bot pull requests: 1
Past Year
- Issues: 112
- Pull requests: 44
- Average time to close issues: about 1 month
- Average time to close pull requests: 11 days
- Issue authors: 1
- Pull request authors: 4
- Average comments per issue: 0.04
- Average comments per pull request: 0.16
- Merged pull requests: 30
- Bot issues: 0
- Bot pull requests: 1
Top Authors
Issue Authors
- ptheywood (112)
Pull Request Authors
- ptheywood (34)
- Shreyan2700 (4)
- bryonymoody (2)
- dependabot[bot] (1)