Hi Ivo,
> "IU" == Ivo Ugrina <[EMAIL PROTECTED]>
> on Fri, 14 Dec 2007 23:03:37 +0100 writes:
IU> I took some time and liberty and tried to improve
IU> existing implementation of SignRank functions
IU> in R. (dsignrank, ...)
IU> As I have seen they've been based on cs
Martin Maechler wrote:
> do you have evidence for your belief?
> i.e. a set of system.time(.) calls where you see the
> difference?
system.time(dsignrank(17511, 400))
user system elapsed
1.010 0.120 1.145
system.time(dsignrank((0:17511), 400))
user system elapsed
1.250.1
Hi Ivo,
> "IU" == Ivo Ugrina <[EMAIL PROTECTED]>
> on Sat, 15 Dec 2007 14:13:10 +0100 writes:
IU> Martin Maechler wrote:
>> do you have evidence for your belief?
>> i.e. a set of system.time(.) calls where you see the
>> difference?
IU> system.time(dsignrank(1751
Thanks, Martin. In the short term (a) seems best. In the long
run we may try (c), because there are other things that data.frame
doesn't do that we want it to do (i.e., allow arbitrary objects with
[ methods, print methods, and the same length to be bound together,
rather than being restricte
Hi Martin,
Martin Maechler wrote:
> that's quite convincing; thank you!
> and I can verify part of it on my computer.
:D
> I think I'd just commit your signrank.c
> (with a few cosmetic changes) to the sources, right?
Right!
There is no need for SIGNRANK_MAX in src/nmath/nmath.h anymore.
> Than
Gabor,
Thank you for drawing this previous work to my attention. I've attached
below code that extends the list comprehension to include logical
'guard' expressions, as in
> leap.years <- .[ x ~ x <- 1900:2100 | (x %% 400 == 0 || x %% 100 != 0
&& x %% 4 == 0) ]
> leap.years
[1] 1904 1908 1
> "TP" == Tony Plate <[EMAIL PROTECTED]>
> on Fri, 14 Dec 2007 13:58:30 -0700 writes:
TP> Duncan Murdoch wrote:
>> On 12/13/2007 1:59 PM, Tony Plate wrote:
>>> Duncan Murdoch wrote:
On 12/11/2007 6:20 AM, [EMAIL PROTECTED] wrote:
> Full_Name: Petr Simecek
If it were simply deprecated and then changed then
everyone using it would get a warning during the period
of deprecation so it would
not be so bad. Given that its current behavior is
not very useful I suspect its not widely used anyways.
| haven't followed the whole discussion so sorry if these
p
