On 4/13/19 12:05 PM, Iñaki Ucar wrote:
On Sat, 13 Apr 2019 at 03:51, Kevin Ushey wrote:
I think it's worth saying that mclapply() works as documented
Mostly, yes. But it says nothing about fork's copy-on-write and memory
overcommitment, and that this means that it may work nicely or fail
spect
In current definition of function 'stopifnot' in stop.R in R 3.6.0 beta
(https://svn.r-project.org/R/branches/R-3-6-branch/src/library/base/R/stop.R)
or R devel (https://svn.r-project.org/R/trunk/src/library/base/R/stop.R), if
'exprs' is specified, cl[[1]] is quote(stopifnot) . To be more robust
integrate(f, xmin, xmax) will have problems when f(x) is 0 over large parts
of (xmin,xmax). It doesn't have any clues to where the non-zero regions
are. It computes f(x) at 21 points at each step and if all of those are
zero (or some other constant?) for a few steps, it calls it a day. If you
ca
Dear all,
This is the first time I am posting to the r-devel list. On
StackOverflow, they suggested that the strange behaviour of integrate()
was more bug-like. I am providing a short version of the question (full
one with plots: https://stackoverflow.com/q/55639401).
Suppose one wants integ
