19 Updating PEcAn Code and Bety Database
Release notes for all releases can be found here.
This page will only list any steps you have to do to upgrade an existing system. When updating PEcAn it is highly encouraged to update BETY. You can find instructions on how to do this, as well on how to update the database in the Updating BETYdb gitbook page.
19.0.1 Updating PEcAn
The latest version of PEcAn code can be obtained from the PEcAn repository on GitHub:
cd pecan # If you are not already in the PEcAn directory git pull
The PEcAn build system is based on GNU Make. The simplest way to install is to run
make from inside the PEcAn directory. This will update the documentation for all packages and install them, as well as all required dependencies.
For more control, the following
make commands are available:
make document– Use
devtools::documentto update the documentation for all package. Under the hood, this uses the
make install– Install all packages and their dependnencies using
devtools::install. By default, this only installs packages that have had their code changed and any dependent packages.
make check– Perform a rigorous check of packages using
make test– Run all unit tests (based on
testthatpackage) for all packages, using
make clean– Remove the make build cache, which is used to track which packages have changed. Cache files are stored in the
.testsubdirectories in the PEcAn main directory. Running
make cleanwill force the next invocation of
makecommands to operate on all PEcAn packages, regardless of changes.
The following are some additional
make tricks that may be useful:
Install, check, document, or test a specific package –
make .<cmd>/<pkg-dir>; e.g.
maketo run, even if package has not changed –
make -B <command>
makecommands in parallel –
make -j<ncores>; e.g.
make -j4 installto install packages using four parallel processes.
All instructions for the
make build system are contained in the
Makefile in the PEcAn root directory. For full documentation on
make, see the man pages by running
man make from a terminal.
Point of contact: Alexey Shiklomanov GitHub/Gitter: @ashiklom email: email@example.com