Radiocarbon Date Calibration and Analysis
This package provides tools for calibrating radiocarbon dates, calculating Summed Probability Distributions (SPDs), and performing statistical tests on SPDs using simulated data (Timpson et al. 2014).
Functionality is similar to that provided by the R package rcarbon (Crema et al. 2016, 2017).
Features
- Radiocarbon Date Calibration: Calibrate individual or multiple radiocarbon dates using calibration curves (e.g., IntCal20, ShCal20).
- Summed Probability Distributions (SPDs): Calculate SPDs for a collection of radiocarbon dates.
- Simulated SPDs: Generate simulated SPDs to test hypotheses or assess the significance of observed SPDs.
- Statistical Testing: Compare observed SPDs with simulated SPDs to identify significant deviations.
- Visualization: Plot calibrated dates, SPDs, and confidence intervals.
Installation
To install the package, you can use the following command:
pip install radiocarbon
Usage
Calibrating Radiocarbon Dates
from radiocarbon import Date, Dates
# Create a single radiocarbon date
date = Date(c14age=3000, c14sd=30, curve="intcal20").calibrate()
# Calibrate multiple dates
dates = Dates(c14ages=[3000, 3200, 3100], c14sds=[30, 25, 35], curves=["intcal20", "intcal20", "shcal20"]).calibrate()
# Plot a single calibrated date
date.plot()
Supposing you have a CSV file with radiocarbon dates, you can read the file and calibrate the dates as follows:
import pandas as pd
from radiocarbon import Dates
# Read dates from a CSV file
df = pd.read_csv("dates.csv")
# Create a Dates object from the DataFrame
dates = Dates.from_df(df, "c14age", "c14sd", "curve").calibrate()
Calculating Summed Probability Distributions (SPDs)
from radiocarbon import SPD
# Create an SPD from a collection of dates
spd = SPD(dates).sum()
# Plot the SPD
spd.plot()
Simulating SPDs and Testing
from radiocarbon import SPDTest
# Test an observed SPD against simulations
spd_test = SPDTest(spd, date_range=(3000, 3500)).run_test(n_iter=1000, model="uniform")
spd_test.plot()
Metadata
Release files for radiocarbon 0.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| radiocarbon-0.5.0.tar.gz | 340.3 kB | Without provenance | Details for radiocarbon-0.5.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| radiocarbon-0.5.0-py3-none-any.whl | Python 3 | none | any | Details for radiocarbon-0.5.0-py3-none-any.whl |
Total release size: 677.4 kB
Release files / radiocarbon-0.5.0.tar.gz
| Download URL | radiocarbon-0.5.0.tar.gz |
|---|---|
| Size | 340.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
076e3f70e30f173278554284d2cc62cdd90de289814a8719b52deeefdcb17efe
|
|
BLAKE2b-256 checksum How to use checksums |
1a43d8eb62b51e80a99af312e6f410264aba132baa838d50adf8df889d874f51
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.3
|
Release files / radiocarbon-0.5.0-py3-none-any.whl
| Download URL | radiocarbon-0.5.0-py3-none-any.whl |
|---|---|
| Size | 337.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1c30f2536c893d26e3d243380464d4adbd6f7f26507f318c7b96016ceacfcabe
|
|
BLAKE2b-256 checksum How to use checksums |
d32a1382b17598320e492976b293abc7eae93172b8a13623e2975fd2f3e6facd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.3
|
Security for radiocarbon 0.5.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.