On Tue, Jan 24, 2017 at 7:06 PM, Henrik Bengtsson
wrote:
> When using multicore-forking of the parallel package, is it possible
> for a child process to know that it is a fork?
R internally uses R_isForkedChild to prevent certain operations within
the fork. However I
When using multicore-forking of the parallel package, is it possible
for a child process to know that it is a fork? Something like:
parallel::mclapply(1:10, FUN = function(i) { test_if_running_in_a_fork() })
I'm looking into ways to protect against further parallel processes
(including
Hi Cathy:
> On Jan 24, 2017, at 2:41 PM, Cathy Lee Gierke wrote:
>
> Which I likely do have wrong, because I'm not sure how to make a data file
> available to the example. but that may be a different issue.
See:
http://r-pkgs.had.co.nz/data.html
In fact read through the
On 24 January 2017 at 15:11, Cathy Lee Gierke wrote:
| I'm cleaning up the problems in my build, but there are a few I do not
| understand, like this one. What is this telling me?
|
|
|
| * checking for unstated dependencies in examples ...Warning in grep("^Xlib:
|
Sean,
You could look at the packages Rblpapi and x13binary both of which do
something a little nonstandard, but arch dependent. You can either 'hit it'
in the configure or the make step. I can detail if needed.
x13binary is smaller. It just pulls the Census binary in, for Windows that is
A few times I'd wish there was a way to support:
pkg::fun()
while _not_ "exposing" fun() on the search() path when attaching pkg.
Although it would be part of the public / exported API, the only way
to call the function would be via pkg::fun(). This would cover Sean's
use case. It would also
On 01/24/2017 10:19 AM, Sean Davis wrote:
Hi, all.
I am curious about what folks think about naming conventions for commonly
named functions, some of which are so common that even establishing a
generic would be difficult because of different use cases. Examples
include things like “filter”.
Hi, all.
I am curious about what folks think about naming conventions for commonly
named functions, some of which are so common that even establishing a
generic would be difficult because of different use cases. Examples
include things like “filter”. One possibility is to use the Google Sheets
Hi Lukas,
thanks for the report. I've changed cumsum so that it is now consistent
with cumprod wrt to NA/NaN propagation.
Now NaN is not turned into NA unnecessarily.
Still please be aware that generally NaNs may become NAs in R (on some
platforms/compilers)
?NaN says
"Computations