The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
tests/test-parameter-functions.R
tleaves()
that
was introduced with new T_sky
function. This led to
crossing all parameter values with all unique values of calculated
T_sky
, which was incorrect. Added unit tests to ensuring
that crossing is done correctly under
tests/test-tleaves-crossing.R
.get_Rabs()
that would have over-written
custom T_sky
function.citation(package = "tealeaves")
.enviro_par()
, “sky” temperature (T_sky
)
can now be provided directly as a values (in K) or as a function (the
default).parallel = TRUE
in tleaves()
,
future uses plan("multisession")
rather
than plan("multiprocess")
.CONDUCT.md
in READMEconstants()
, enviro_par()
, and
leaf_par()
no longer require values be provided with units.
If values are provided without units, they are assigned proper units,
but no unit conversion is performed. If values have units, these
functions check whether units are correct and convert them to units used
in the package.
Release to be archived with revision of “Is amphistomy an adaptation to high light? Optimality models of stomatal traits along light gradients.”
tealeaves implements models of leaf temperature using energy balance. It uses units to ensure that parameters are properly specified and transformed before calculations. It allows separate lower and upper surface conductances to heat and water vapor, so sensible and latent heat loss are calculated for each surface separately as in Foster and Smith (1986). It’s straightforward to model leaf temperature over environmental gradients such as light, air temperature, humidity, and wind. It can also model leaf temperature over trait gradients such as leaf size or stomatal conductance.
NEWS.md
file to track changes to the
package.These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.