I have been using the fork package on a cluster to spawn jobs. I have
noticed that I end up with many "R defunct" (zombie) processes following
the use of fork that do not die completely until I close down R.
Initially, I thought it may be my code but I ran the example from the
latest fork pac
On 12/15/2006 8:30 AM, billk01 wrote:
> I have been using the fork package on a cluster to spawn jobs. I have
> noticed that I end up with many "R defunct" (zombie) processes following
> the use of fork that do not die completely until I close down R.
> Initially, I thought it may be my code b
On Fri, Dec 15, 2006 at 08:30:05AM -0500, billk01 wrote:
> I have been using the fork package on a cluster to spawn jobs. I have
> noticed that I end up with many "R defunct" (zombie) processes following
> the use of fork that do not die completely until I close down R.
> Initially, I thought
> Robert Gentleman writes:
> I would vastly prefer apropos to be case insensitive by default. The
> point of it is to find things similar to a string, not the same as, and
> given that capitalization in R is somewhat erratic (due to many authors,
> and some of those changing their minds ove
Kurt Hornik <[EMAIL PROTECTED]> writes:
>> Robert Gentleman writes:
>
>> I would also, personally prefer some sort of approximate matching since
>> there are different ways to spell some words, and some folks abbreviate
>> parts of words.
>
> The same design has been employed by help.search
> Seth Falcon writes:
> Kurt Hornik <[EMAIL PROTECTED]> writes:
>>> Robert Gentleman writes:
>>
>>> I would also, personally prefer some sort of approximate matching since
>>> there are different ways to spell some words, and some folks abbreviate
>>> parts of words.
>>
>> The same des
I apologize if this is just a misunderstanding on my part, but I was
under the impression that the intervals returned by co.intervals should
cover all the observations. Yet
x<-1:10
z<-co.intervals(x,overlap=0)
In R, z equals
[,1] [,2]
[1,] 0.5 1.5
[2,] 2.5 3.5
[3,] 3.5 4.5
[4,] 5.5
I've noticed that the max.col function with the default "random"
option often gives unexpected results. For instance, in this test, it
seems clear what the answer should be:
> # second col should always be max
> x1 = cbind(1:10, 2:11, -Inf)
>
> # this works fine
> max.col(x1, "first")
[1] 2 2 2 2
This happens equally when overlap = 0.5 (the default).
Yes, it is a bug. R does xr <- x[r + ii] with fractional r.
On Fri, 15 Dec 2006, Benjamin Tyner wrote:
> I apologize if this is just a misunderstanding on my part, but I was
> under the impression that the intervals returned by co.intervals
