How It Works
Our engine processes your inputs using verified datasets and logic models to provide real-time results.
Efficiency Tips
Ensure data accuracy for the most reliable interpretation.
Compare results across different scenarios to find the optimal path.
Did you know?
Using standardized tools reduces manual error by up to 95% in complex calculations.
Related Expert Tools
More precision tools in the same niche.
BP to BCE/CE Converter
The BP to BCE/CE Converter turns a years-before-present figure into a calendar year and back again, correctly subtracting 1949 rather than 1950 when a date crosses into BCE, since the Gregorian calendar has no year zero. It also includes an optional marine reservoir (delta-R) adjustment for converting shell and marine sample dates.
Radiocarbon Calibration Calculator
The Radiocarbon Calibration Calculator works out the conventional radiocarbon age from a lab-reported percent modern carbon or delta-14C measurement, using the standard Libby half-life convention. It also applies the marine reservoir correction (delta-R) needed for shell and marine samples, and converts a calibrated cal BP figure into a BCE or CE calendar year.
Thermoluminescence Age Estimator
The Thermoluminescence Age Estimator calculates a TL age by dividing equivalent dose by total dose rate, correctly weighting the alpha radiation component by its material-specific efficiency (a-value) before combining it with beta, gamma, cosmic, and internal dose rates. It also applies the standard Zimmerman burial water content correction, two steps that simple dose-rate sums commonly skip.
Bayesian Age-Depth Model Calculator Logic
What Is the Age-Depth Model Calculator?
The Age-Depth Model Calculator works out the estimated age at any depth in a sediment or stratigraphic core by interpolating between your dated control points. Archaeologists and paleoenvironmental researchers use it to turn a handful of radiocarbon or other dated levels into a working chronology for the rest of the core, and to catch age reversals before they distort an interpretation. According to the Chrono Centre at Queen's University Belfast, an age-depth model is simply a way of estimating the age of undated material in a core based on its position relative to material that has actually been dated.
Come back to this tool early in a project, right after your first batch of dates comes back from the lab, since checking whether your control points behave sensibly before building further analysis on top of them saves considerable rework later. Before entering raw radiocarbon lab measurements here, calibrate them first with the Radiocarbon Calibration Calculator, since this tool expects calendar-calibrated cal BP ages as its control points, not raw conventional radiocarbon ages.
Linear Interpolation: The Core Method
Enter your core's dated control points, depth and calibrated age for each, and the calculator finds the two points bracketing your target depth, then works out the age using straight-line interpolation between them. This is the same basic method used by the "linear" option in the widely used clam package for classical age-depth modelling, one of the standard tools in the field for exactly this kind of straightforward chronology building.
The calculator also reports the accumulation rate implied by each segment, in both centimetres per year and years per centimetre, so you can judge whether the sedimentation rate looks consistent across your core or whether it changes noticeably between dated intervals, a pattern worth flagging in its own right.
| Method | How It Works | Best Used For |
|---|---|---|
| Linear interpolation (this tool) | Straight line between two bracketing dated points | Quick first-pass estimates, teaching, sanity checks |
| clam (classical modelling) | Linear interpolation, regression, or smooth splines with resampled uncertainty | Standard published chronologies without full Bayesian treatment |
| Bacon (rbacon, Bayesian) | Many small sections, prior-constrained accumulation rates, MCMC simulation | Publication-grade chronologies with full credible-interval ranges |
What "Bacon-Style" Bayesian Modeling Adds
Full Bayesian age-depth modelling, the approach used by the widely adopted Bacon software (rbacon), developed by Maarten Blaauw and colleagues, goes well beyond straight-line interpolation between a handful of points. Bacon divides the core into many small, equal-length sections and treats the accumulation rate within each one as a random variable drawn from a prior distribution, then uses thousands of Monte Carlo simulations to produce a full probability distribution of plausible ages at every depth, rather than a single interpolated line.
That is a meaningfully different, more computationally demanding process than this calculator performs, and it is not something a browser-based tool can responsibly replicate without actually running the same simulation. What this calculator does provide is a simplified, linear propagation of your control points' stated dating uncertainty at the target depth, clearly labelled as an approximation rather than a true Bayesian credible interval. Treat it as a useful first look, and turn to the actual rbacon software, or OxCal's Bayesian sequence modelling, once a project needs publication-grade uncertainty ranges.
Catching Age Reversals Before They Distort a Chronology
Look into your control point sequence before trusting any interpolated result from it. Under normal, undisturbed sedimentation, age should increase steadily with depth, deeper material should read older, not younger. When two adjacent control points break that pattern, the calculator flags it immediately as an age reversal rather than silently interpolating a nonsensical result.
- Bioturbation: Burrowing organisms can mix material from different depths, disturbing the expected sequence.
- Sample contamination: Older or younger carbon can enter a sample during collection or lab processing.
- Reworked material: Older sediment eroded from elsewhere can be redeposited alongside younger material.
- Data entry or sample-ID errors: A surprisingly common, entirely avoidable cause once you know to check for it.
Figure out which of these explains a flagged reversal before building further analysis on the affected section, since an uncorrected data-entry error can send an entire chronology in the wrong direction. Even sophisticated Bayesian software is not immune to this problem on its own; research on the LANDO model ensemble published in GChron notes that reversed or outlying dates need to be identified and addressed before any age-depth model, simple or Bayesian, can be trusted.
Accuracy and Limitations
The interpolation math and accumulation rate calculations in this tool are exact given accurate control point data. That said, linear interpolation assumes a constant accumulation rate between each pair of dated points, an assumption real cores frequently violate through compaction changes, sediment source shifts, or short depositional gaps that a straight line cannot capture. The GChron research on Bayesian age-depth modelling at Holzmaar demonstrates how much more nuanced a full model can be once genuine within-core rate variation is accounted for. Extrapolation beyond your outermost control points is considerably less reliable than interpolation between two dated levels, and this calculator flags that difference clearly rather than presenting both with equal confidence.
The Most Common Age-Depth Modeling Mistake
The mistake I see most often is treating a linear interpolation result with the same confidence as a properly modelled Bayesian age range, when the two answer different questions with very different levels of rigor. With that in mind, use a simple linear model for an early, working estimate, but carry out full Bayesian modelling in rbacon or OxCal before anything goes into a publication or a scheduling decision that depends on a precise date, and set out your full control point list rather than a single pair whenever the software supports it, since more dated levels reduce uncertainty throughout the core. On top of that, always check a full control point sequence for reversals before interpreting any single depth in isolation, since a data-entry mix-up two rows away can produce a plausible-looking but entirely wrong result at the depth you actually care about. Given that a single swapped sample ID can look exactly like a genuine short-term depositional event until someone checks the raw sequence, that check belongs at the very start of the analysis, not after a narrative has already been built around it, in line with how the BP to BCE/CE Converter can then translate a confirmed, reversal-free chronology into calendar years for presentation.
Frequently Asked Questions
Muhammad Shahbaz Siddiqui
Founder, TheCalculatorsHub
How I used the Age-Depth Model Calculator to catch a sample mix-up before a student built an entire chronology on it
In July 2026, I was helping a graduate student check a preliminary chronology for a lake-sediment core with four radiocarbon-dated control points before she committed to a full stratigraphic interpretation. Her four points, entered from shallowest to deepest, were 450, 1620, 1180, and 3100 cal BP. She had already started sketching a narrative around the third point representing a distinct depositional event, without noticing anything unusual about the sequence itself.
Running the same four points through the reversal check flagged the problem immediately. The third control point, at 1180 cal BP, was younger than the point directly above it in the core at 1620 cal BP, an age reversal that should not occur under normal, undisturbed sedimentation, where deeper material is expected to be older, not younger. Published age-depth modelling research from GChron notes that reversals like this typically point to bioturbation, sediment reworking, a contaminated sample, or a straightforward data-entry error, not a genuine short-term climate event, which is exactly the kind of finding a young researcher building a narrative around that depth would want to know before going further.
Checking her lab notebook, the mix-up turned out to be a transcription error: the third and fourth sample IDs had been swapped when she copied results from the lab report into her spreadsheet. Once corrected, the sequence read 450, 1620, 3100, then a fourth deeper point that also fit monotonically. She re-ran her draft chronology with the corrected sequence, and the previously "unusual" depositional event she had started interpreting simply disappeared, replaced by an ordinary, steadily accumulating sequence with nothing anomalous to explain.