Skip to content

PEcAn 1.3.6: Updates to support changes in BETYdb and FIA databases
Compare
Choose a tag to compare
@robkooper robkooper released this 29 Jun 06:34
· 15494 commits to master since this release
v1.3.6
9a54b13

DOI

This version focuses on more database updates.

As always you can download the VM from:
http://isda.ncsa.illinois.edu/download/index.php?project=PEcAn&sort=category

PEcAn

add sites/data

  • the script to add sites is now part of PEcAn. To add the sites data you can use pecan/scripts/add.data.sh
  • the script to add models is updated and will setup the binaries and is called pecan/scripts/add.models.sh

Both scripts can be called multiple times, but will only add the information to the database once.

pecan.xml:

  • In pecan.xml the database section now has 2 subsections, bety and fia. Any existing information that was in the database section in pecan.xml will need to be moved to the bety subsection, read.settings() will automatically update your pecan.xml to reflect this.
  • The <bety><write> option in the pecan.xml is now part of the <database><bety> section, read.settings() will automatically update your pecan.xml to reflect this.
  • The ED land use/soil/vegetation/thermal sums data files are now inputs in BETY that need to be specified as inputs.

Action Required: add ED data files to database, see #120

SipNET

  • Support for meteorology conversion from netCDF CF standard to SipNET's .clim driver files

PEcAn Web App

  • config.php now declares the fully qualified host name ($fqdn)
  • the config.php in pecan/web will have new database configuration parameters, please see config.example.php.
  • no longer needed to specify vet/soil/ed_inputs in config.php, these are now stored as inputs in BETY.
  • if the fia database is specified in config.php, the user can now select fia2ed from psscss selector.

Action Required: update pecan/web/config.php, see pecan/web/config_example for latest settings.

BETY:

To update BETY database either download a new version or update the database.

  • In the database there is now a link from a model to the dbfiles table. This allows you to have a single model, with binaries located in different places on different systems.
  • Each PFT now stores the model type associated with it, the web application will use this to find the right pfts to display for the user, and read.settings will check to see if the PFT is compatible with the model.

Action Required: add binaries to models, for example using the pecan/scripts/addmodels.sh.
Action Required: the migration of the database will add the appropriate model_type to each PFT based on the prefix of the PFT.

Assets 2