The hardware and bandwidth for this mirror is donated by dogado GmbH, the Webhosting and Full Service-Cloud Provider. Check out our Wordpress Tutorial.
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[@]dogado.de.
message()
not via
cat()
. This is the right thing to do.bdII*
family) in versions prior to 0.5 was not
correctly specified.P
which only “partitions” the fitted coefficients between
multiple predators.emdII
. Hopefully
this name better reflects its heritage.real77*
family was internally
consistent, but not terribly well specified. It is probable that the old
specification made curves difficult to fit and generated non-sensical
‘q’ parameters.real77*
family has now been fully deprecated and
removed from FRAIR. Trying to use these functions will throw an
error.flexp
and flexpnr
) have been added as a
replacement.hassIIInr
, which better reflects that it is a
Non-Replacement model.hassIIIr*
function directly will
pass through to hassIIInr
, with a warning.hassIIIr
is no longer recognised by
frair_responses()
, so attempting to fit this model in the
FRAIR framework will throw an error.Bythotrephes
Data
bythotrephes
dataset. It
describes Bythotrephes spp. (water fleas) preying on prey items
of different sizes.print.frboot
removing an unnecessary
extra line break. Yep. Big stuff!tozero
argument of lines.frfit
,
lines.frboot
and drawpoly.frboot
are TRUE,
these functions try to plot to zero. If that results in an undefined
value for the fitted response, then it draws to 1e-04 instead and a
warning is thrown. Note this does not guarantee all bootstrapped fits
will be defined at this value either.get
calls are scoped to
‘package:frair’. This means it’s no longer possible (whether
accidentally or deliberately) to ‘overwrite’ FRAIR functions with those
in the global namespace. This “functionality”” might return in the
future alongside some formal documentation for extending FRAIR.boot
does not use
::
. The reason is that in the (fairly likely) scenario that
users go digging into the structure of the frboot objects and call
obj$fit
directly, the boot::boot
in the call
confuses print.boot
and it reports some pretty crazy
stuff!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.
Health stats visible at Monitor.