Changelog • BioCroField

BioCroField VERSION 0.3.0

LMA is now included in the output from biomass_table.
New crop-specific guides to harvesting and weighing are now available, along with a convenience function for creating such guides (generate_crop_guide).
The new sheets are now mentioned in the main vignette (handling_biomass_measurements).
A new vignette has been added (images_from_the_field) that illustrates parts of the harvesting and weighing process using pictures from the field.

Two new methods for estimating LAI were added to process: LAI_from_planting_density and LAI_from_measured_population. The original LAI estimate was renamed from LAI to LAI_from_LMA to better indicate the different estimates.
Allow the user to (optionally) specify plant spacing in additiong to row spacing and plant population when creating a harvest_point object. If all three are specified, a consistency check will be performed. If only two are specified, the value of the third will be calculated.
add_seed_biomass now takes planting density from the input data frame.
Renamed two other variables to make their meaning more clear:
- target_population was renamed to planting_density
- population was renamed to measured_population
PRs related to creating this version:

A bug related to partial name matching for partitioning components was detected and fixed. In short, if a value of leaf mass was not supplied but a value of leaf_litter was supplied, the leaf litter mass would be used by process when calculating LMA and other related properties, leading to errors. Now, the internal code does not use partial name matching, and the user is able to supply a different name for the leaf tissue component if it does not have the standard name of leaf.
PRs related to creating this version:
- https://github.com/biocro/BioCroField/pull/2

This is the first version of BioCroField. At this point, the package is in a state of rapid development, and not all changes will be described here.
We are reserving version 1.0.0 for a more stable and complete future release; until then, major changes should only increase the minor version number.