Title: | PEcAn Functions Used for Ecological Forecasts and Reanalysis |
---|---|
Description: | The Predictive Ecosystem Carbon Analyzer (PEcAn) is a scientific workflow management tool that is designed to simplify the management of model parameterization, execution, and analysis. The goal of PEcAn is to streamline the interaction between data and models, and to improve the efficacy of scientific investigation. |
Authors: | Mike Dietze [aut], David LeBauer [aut, cre], Xiaohui Feng [aut], Dan Wang [aut], Carl Davidson [aut], Rob Kooper [aut], Shawn Serbin [aut], Ankur Desai [aut], James Simkins [aut], Chris Black [aut], Istem Fer [aut], Hamze Dookohaki [aut], Alexey Shiklomanov [aut], Elizabeth Cowdery [aut], Ann Raiho [aut], Tess McCabe [aut], Tony Gardella [aut], University of Illinois, NCSA [cph] |
Maintainer: | David LeBauer <[email protected]> |
License: | BSD_3_clause + file LICENSE |
Version: | 1.8.0.9000 |
Built: | 2024-12-17 17:26:22 UTC |
Source: | https://github.com/PecanProject/pecan |
Dates, tags, and versions of all PEcAn releases
pecan_releases
pecan_releases
Data frame with 3 columns
name used to mark the release
date released
numeric version assigned to this release
Extracted from Git tags in the PEcAn development repository
Reports the currently installed or loaded version(s) of each PEcAn package, as well as the versions expected by the specified release(s) of the PEcAn system.
pecan_version(version = max(PEcAn.all::pecan_releases$version), exact = FALSE)
pecan_version(version = max(PEcAn.all::pecan_releases$version), exact = FALSE)
version |
PEcAn release number to use for expected package versions |
exact |
Show only tags that exactly match |
When exact
= FALSE (the default), pecan_version
will show all releases
whose names contain version
as a substring.
This is mostly so that e.g. "1.4.2" finds the release tag "v1.4.2",
but since all matches are returned it can also be handy for seeing all
patches sharing a minor version number (see examples).
If more than one version of a package is installed, the output from
pecan_version()
will contain multiple rows for that package.
This can occur if you have installed different versions to different
locations in .libPaths()
, or if you've loaded a new version into your
current session by loading it from its source directory without installing
it to the R library.
If you see multiple rows unexpectedly, try
find.package(<pkgname>, verbose = TRUE)
to see where each version was found.
data frame with columns for package name, expected version(s),
installed version, and Git hash (if known).
If the sessioninfo
package is installed, an additional column reports
where each package was installed from: local, github, CRAN, etc.
pecan_version() pecan_version(c("1.4.0", "1.5.0", "1.6.0")) # multiple matches are possible when exact = FALSE pecan_version("v1.3", exact = TRUE) pecan_version("v1.3", exact = FALSE)
pecan_version() pecan_version(c("1.4.0", "1.5.0", "1.6.0")) # multiple matches are possible when exact = FALSE pecan_version("v1.3", exact = TRUE) pecan_version("v1.3", exact = FALSE)
Versions of all PEcAn packages in each release of PEcAn
pecan_version_history
pecan_version_history
Data frame with at least 33 columns (plus one more every release!)
Package name, as character
Release numbers,
each with the Git tag as the column name and numeric package versions
as the row contents.
NA means package
did not exist in this version of PEcAn.
Extracted from Git history of the PEcAn development repository
pecan_version
, which queries this table and also reports the
versions currently installed