CRAN Package Check Results for Package hisse

Last updated on 2024-11-30 09:49:18 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 2.1.11 51.56 373.20 424.76 NOTE
r-devel-linux-x86_64-debian-gcc 2.1.11 34.65 235.04 269.69 NOTE
r-devel-linux-x86_64-fedora-clang 2.1.11 694.95 NOTE
r-devel-linux-x86_64-fedora-gcc 2.1.11 719.22 NOTE
r-devel-windows-x86_64 2.1.11 56.00 395.00 451.00 NOTE
r-patched-linux-x86_64 2.1.11 52.90 340.79 393.69 NOTE
r-release-linux-x86_64 2.1.11 55.44 346.21 401.65 NOTE
r-release-macos-arm64 2.1.11 166.00 NOTE
r-release-macos-x86_64 2.1.11 257.00 NOTE
r-release-windows-x86_64 2.1.11 60.00 400.00 460.00 NOTE
r-oldrel-macos-arm64 2.1.11 190.00 OK
r-oldrel-macos-x86_64 2.1.11 287.00 OK
r-oldrel-windows-x86_64 2.1.11 71.00 464.00 535.00 OK

Check Details

Version: 2.1.11
Check: Rd files
Result: NOTE checkRd: (-1) generateMiSSEGreedyCombinations.Rd:25: Lost braces 25 | Estimating extinction rates is hard. This affects all diversification models (even if all you want and look at is speciation rate, extinction rate estimates still affect what this is as they affect the likelihood). It is most noticeable in MiSSE with eps, the extinction fraction (extinction rate divided by speciation rate). One option, following Magallon & Sanderson (2001), is to set extinction fraction at set values. By default, we use theirs, 0 (meaning a Yule model - no extinction) or 0.9 (a lot of extinction, though still less than paleontoligists find). You can set your own in \code{fixed.eps.tries}. If you only want to use fixed values, and not estimate, get rid of the NA, as well. However, don't \dQuote{cheat} -- if you use a range of values for fixed.eps, it's basically doing a search for this, though the default AICc calculation doesn't dQuote{know} this to penalize it for another parameter. | ^ checkRd: (-1) generateMiSSEGreedyCombinations.Rd:27: Lost braces 27 | HiSSE and thus MiSSE assume that a taxon has a particular hidden state (though they recognize that there can be uncertainty in which state it actually has). Thus, they're written to assume that we dQuote{paint} these states on the tree and a given state affects both turnover and eps. So if turnover has four hidden states, eps has four hidden states. They can be constrained: the easiest way is to have, say, turnover having an independent rate for each hidden state and eps having the same rate for all the hidden states. If \code{vary.both} is set to FALSE, all models are of this sort: if turnover varies, eps is constant across all hidden states, or vice versa. Jeremy Beaulieu prefers this. If \code{vary.both} is set to TRUE, both can vary: for example, there could be five hidden states for both turnover and eps, but turnover lets each of these have a different rate, but eps only allows three values (so that eps_A and eps_D might be forced to be equal, and eps_B and eps_E might be forced to be equal). Brian O'Meara would consider allowing this, while cautioning you about the risks of too many parameters. | ^ Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-devel-windows-x86_64, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64