Displaying 4 results from an estimated 4 matches for "31.44828".
2007 Nov 05
1
do.call without arguments?
Hello,
I have a vector containing strings of simple operation methods.
methods <- c("mean","sd","median") e.g.
Now, I'd like to apply these methods to my data and I thought, I could make a
do.call. But these methods don't need any further arguments... Do I have to
create an empty argument list?
I wanted to use a tapply( data, factor, ??? do.call
1999 Nov 11
2
tapply not simplifying to vector? (PR#320)
Hi, all.
The help file for tapply says that if simplify is true, and the result of
the calculation is always a scalar, then tapply will return a vector.
Nonetheless:
> t1 <- tapply(runif(10), rep(1:5, 2), mean)
> is.vector(t1)
[1] FALSE
> is.array(t1)
[1] TRUE
>
I have found this in version 0.65.1 on an SGI running Irix 6.5, and on a
Mac running Linux-PPC. I've also
2008 Feb 12
3
fun.aggregate=mean in reshape
Hi all,
We are facing a problem while introducing ourselves to Reshape package
use. Melt seems to work fine, but cast fails when we use mean as
fun.aggregate. As you see here, length and sum work fine, but mean
throws this same error whatever dataset we use.
> cast(aqm, month ~ variable, length)
month ozone solar.r wind temp
1 5 26 27 31 31
2 6 9 30 30
2005 Jan 06
1
arrays emerging from tapply
The code below illustrates some points about results from tapply that
I find strange. I wonder if they are intended and if so why it is so.
1) When you make a table the dimnames is a *named* list, tapply
returns an unnamed list.
2) data.frame behaves differently on an array and a table. Is this
an intended feature?
3) For tables class(TAB) and attr(TAB,"class") both return