Analyses rarely go straight from raw data to results
Routine but essential tasks come first: checking taxonomic names, binning occurrences, reconstructing palaeogeography
This code is often rewritten from scratch for every project
This leads to duplicated effort, lost time, and ad hoc workflows that can be hard to reproduce, share, or reuse (not FAIR)
What does palaeoverse offer?
Reusable: a few clear lines replace long, bespoke scripts
Reproducible: consistent function names, arguments, and outputs
Readable: well-documented, tested, and peer-reviewed functions
Design
Three design choices shape how palaeoverse functions look and behave:
Built around occurrence data
Modular
Flexible
Built around occurrence data
Most palaeoverse functions take an occurrence data.frame as input
Each column is a different variable (e.g. identity, age, location, formation, reference)
Each row is a single record of something present at a particular place and time
That “something” is usually a taxon, but not always (in the reefs dataset, each row is a fossil reef)
Occurrence data.frame
r_number
name
formation
system
series
interval
biota_main
biota_sec
lng
lat
country
authors
title
year
1
Tilkideligi Tepe
Triassic
Upper Triassic
lower Norian
Calcisponges
Stromatoporoids
30.3833
37.0333
Turkey
Riedel, P.
Riffbiotope im Karn und Nor (Obertrias) der Tethys: Entwicklung, Einschnitte und Diversitatsmuster. -
1990
2
Hydra
Pantokrator Limestone
Triassic
Upper Triassic
upper Carnian
Corals
Calcisponges
23.6333
37.3833
Greece
Schafer, P., Senowbari-Daryan, B.
The Upper Triassic Pantokrator Limestone of Hydra (Greece): An example of a prograding reef complex. -
1982
3
Shiraho, W-Pacific
Neogene
Holocene
Recent
Corals
Algae
124.2500
24.3333
Pacific
Kayanne, H., Suzuki, A. & Saito, H.
Diurnal changes in the partial pressure of carbon dioxide in coral reef water. -
1995
Modular
Each function in palaeoverse does one job well. You can use one on its own, or chain several together into a full workflow:
# Load library and datalibrary(palaeoverse)data(tetrapods)# Get time binsbins <-time_bins(interval ="Phanerozoic", rank ="stage")# Bin databin_time(tetrapods, bins = bins, method ="mid")# Pipe togethertetrapods |>bin_time(bins =time_bins(interval ="Phanerozoic", rank ="stage"), method ="mid")
Flexible
palaeoverse functions are not tied to a specific source (e.g. Paleobiology Database). Column names are provided as arguments, not fixed requirements:
# Load library and datalibrary(palaeoverse)data(tetrapods)# Get unique speciestetrapods |>tax_unique(genus ="genus", family ="family", order ="order", class ="class", name ="accepted_name")
Applications
Exploring and summarising data
Cleaning and harmonising data
Preparing data for analyses
Exploring and summarising data
palaeoverse includes functions to help users explore and understand their data better, such as calculating temporal and geographic ranges:
# Load library and datalibrary(palaeoverse)data(tetrapods)# Estimate temporal range of taxatetrapods |># Drop NAssubset(!is.na(order)) |># Plot temporal rangetax_range_time(name ="order", plot =TRUE)
Temporal range
Temporal range of Carboniferous to Early Triassic tetrapods.
Cleaning and harmonising data
palaeoverse includes functions to support the cleaning and harmonising of data such as removing duplicates and checking taxonomic names:
# Load library and datalibrary(palaeoverse)data(tetrapods)# Check for potential misspellingstax_check(tetrapods, name ="genus")$synonyms
group greater lesser count_greater count_lesser
1 D Dvinosaurus Dinosaurus 23 2
2 V Varanopus Varanops 5 3
Preparing data for analyses
palaeoverse includes functions to prepare data for analyses, such as estimating palaeocoordinates and binning data:
# Load library and datalibrary(palaeoverse)data(reefs)# Generate equal-area latitudinal binsbins <-lat_bins_area(n =12)head(bins, n =3)
bin min mid max area area_prop
1 1 56.44269 73.22135 90.00000 4.250537e+13 0.08333333
2 2 41.81031 49.12650 56.44269 4.250537e+13 0.08333333
3 3 30.00000 35.90516 41.81031 4.250537e+13 0.08333333
# Bin databinned_reefs <-bin_lat(reefs, bins = bins)
So, what is palaeoverse?
Think of palaeoverse as the bridge between raw occurrence data and the analytical methods you want to apply.
Getting help
Everyone gets stuck with new tools, and knowing where to look for help is a key skill
palaeoverse has several layers of support, from built-in documentation to community help