dplR: Dendrochronology Program Library in R

Canonical link: https://rscholar.com/pkg/dplR

Andy Bunn • Mikko Korpela • Franco Biondi • Filipe Campelo • Pierre Mérian • Fares Qeadan • Christian Zang • Allan Buras • Alice Cecile • Manfred Mudelsee • Michael Schulz • Stefan Klesse • David Frank • Ronald Visser • Ed Cook • Kevin Anchukaitis • View description and downloads View dependencies GitHub project

2007 Published

0 Citations

16 Authors

71 Revisions

1.7.9 Version

GPL-2 License

Referenced by ⇅	Year
wiad: Wood Image Analysis and Dataset (Version 0.0.1.0)	2021
MtreeRing: A Shiny Application for Automatic Measurements of Tree-Ring Widths on Digital Images (Version 1.4.5)	2018
dendroNetwork: Create Networks of Dendrochronological Series using Pairwise Similarity (Version 0.5.5)	2024
dendroTools: Linear and Nonlinear Methods for Analyzing Daily and Monthly Dendroclimatological Data (Version 1.2.16)	2017
detrendeR: A Graphical User Interface (GUI) to Visualize and Analyze Dendrochronological Data (Version 1.0.5)	2011
dfoliatR: Detection and Analysis of Insect Defoliation Signals in Tree Rings (Version 0.3.0)	2020
measuRing: Detection and Control of Tree-Ring Widths on Scanned Image Sections (Version 0.5.2)	2014
TRADER: Tree Ring Analysis of Disturbance Events in R (Version 1.2-6)	2015
dendroNetwork Similarity: (Version )	0
dfoliatR Rings: (Version )	0
fPortfolio: Rmetrics - Portfolio Selection and Optimization (Version 4023.84)	2005
iadf: Analysis of Intra Annual Density Fluctuations (Version 0.1.3)	2017
mbr: Mass Balance Reconstruction (Version 0.0.1)	2021
measuRing Sections: (Version )	0
pointRes: Analyzing Pointer Years and Components of Resilience (Version 2.0.2)	2015
xRing: Identify and Measure Tree Rings on X-Ray Micro-Density Profiles (Version 0.1.2)	2018

RPKG Scholar presents a tabulation of an author's contribution in the development of R packages stored in the Comprehensive R Archive Network (CRAN). Within this site, we consider package dependencies (suggests,imports,depends,enhances) as citations because we believe that using one's package to develop another is tantamount to citing the author of the package being imported, suggested or enhanced.