similar to: R-alpha: Plot: Title above 'mfrow=c(2,2)' ??

I think I am misunderstanding something about the identify() function. if we have an example such as this: > x_1:10 > y_1:10 > plot(x,y) > identify(x,y, n=1) [1] 2 3 > I clicked on two points and identify() returned both of them (2 and 3). The manual says n is the maximum number of points to be identified. If I specify n=1, should identify() return a single value?

1. lbeta and beta do not work properly: lbeta returns its first argument and beta gives the lbeta result. In names.c lines 245-6, the codes for these should be 2 and 3 instead of 1 and 2 2. crtl-C does not work (except the first time) on Red Hat elf Linux (which has many many other problems as well) nor on the previous version of Linux for Amiga. It worked on Slackware aout Linux and now works

1. lbeta and beta do not work properly: lbeta returns its first argument and beta gives the lbeta result. In names.c lines 245-6, the codes for these should be 2 and 3 instead of 1 and 2 2. crtl-C does not work (except the first time) on Red Hat elf Linux (which has many many other problems as well) nor on the previous version of Linux for Amiga. It worked on Slackware aout Linux and now works

rbind() does something strange to dimnames R : Copyright 1997, Robert Gentleman and Ross Ihaka Version 0.50 Beta (April 1, 1997) R is free software and comes with ABSOLUTELY NO WARRANTY. You are welcome to redistribute it under certain conditions. Type "license()" for details. > test1 <- data.frame(time= c(4, 3,1,1,2,2,3), + status=c(1,NA,1,0,1,1,0), + x= c(0,

Both of these used to work and seem useful and harmless: R> matrix(1,ncol=1)%*%c(1,2) Error in matrix(1, ncol = 1) %*% c(1, 2) : non-conformable arguments R> matrix(1,ncol=1)*(1:2) Error: dim<- length of dims do not match the length of object Thomas Lumley -----------------------------------------------------+------ Biostatistics : "Never attribute to malice what : Uni of

Both of these used to work and seem useful and harmless: R> matrix(1,ncol=1)%*%c(1,2) Error in matrix(1, ncol = 1) %*% c(1, 2) : non-conformable arguments R> matrix(1,ncol=1)*(1:2) Error: dim<- length of dims do not match the length of object Thomas Lumley -----------------------------------------------------+------ Biostatistics : "Never attribute to malice what : Uni of

Does R have a function like the S(plus) function, lmsreg, Least Median of Squares Regression? I am using R-0.61. Thank you, Mike Fleming mfleming at nass.usda.gov -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or

Does R have a function like the S(plus) function, lmsreg, Least Median of Squares Regression? I am using R-0.61. Thank you, Mike Fleming mfleming at nass.usda.gov -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or

Hi, when designing libraries for R, is it possible to call C/Fortran subroutines from other dynamically loaded code? The following example crashes R: ********* fn1.c ***************** void twice(int *i) { *i = 2 * *i; } ********************************* ********* fn2.c ***************** extern int twice(int *i); void negtwice(int *i) { *i = -1 * twice(i); }

Hi, when designing libraries for R, is it possible to call C/Fortran subroutines from other dynamically loaded code? The following example crashes R: ********* fn1.c ***************** void twice(int *i) { *i = 2 * *i; } ********************************* ********* fn2.c ***************** extern int twice(int *i); void negtwice(int *i) { *i = -1 * twice(i); }

The following patch adds a trivial family method for linear models. -k --- src/library/base/funs/lm.orig Tue May 27 02:53:58 1997 +++ src/library/base/funs/lm Sun Aug 10 22:00:46 1997 @@ -412,3 +412,5 @@ } formula.lm<-function(x)formula(x$terms) + +family.lm <- function(x) { gaussian() } =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- r-devel mailing list

Is this behavior correct? (R 0.49 on SunOS 4.1.4) > "a">1 TRUE > "a"<1 FALSE > "a"==1 FALSE > "a">2 TRUE > "a"<2 FALSE (I know, this is like the old joke: "Doctor, it hurts when I do this." "Well, don't do that!" But it might be useful to have this caught by an error or warning message

dbeta(1, a,b) would return 1 instead of 0. Here is the patch for ..../src/math/dbeta.c : --- dbeta.c~ Sun Nov 24 23:43:10 1996 +++ dbeta.c Tue Apr 15 21:25:30 1997 @@ -23,9 +23,7 @@ { if (a <= 0.0 || b <= 0.0) DOMAIN_ERROR; - if (x <= 0) + if (x <= 0 || x >= 1.0) return 0.0; - if (x >= 1.0) - return 1.0; return MATH_CHECK(pow(x, a - 1) * pow(1.0 - x, b - 1.0) /

Seems to be working very nicely (and what a relief to see it actually working!), I've found only a few problems till now: a) Characters outside 0-0x7f seem to get encoded as CP850 or something, not Latin 1 (æøå keys on DK keyboard gives mu,degree,sigma). b) Infinite recursion crashed R. (I forget details, but it was something stupid like f<-function(x){if (x < 1) 1 else f(x)*(x-1)})

Following my posting of a write.table() function, Martin suggested that one could have a generic write() function and special methods for e.g. time series, data frames, etc. Well, a month has passed since ... What does everyone think? Is it a good idea, or would write.table() be enough? If we think that it is not enough, which arguments should the write methods typically allow? What about

Paul Murrell and I are making some progress with making mathematical expressions available in graphs. The idea is to use R expressions to represent the mathematical expressions. So far we have (or will soon have): R LaTeX x^i x^i x[i] x_i alpha \alpha Alpha \Alpha hat(x) \hat{x} \widehat{x} bar(x) \bar{x} \overline{x} x+y x+y x-y x-y x/y x/y (x) (x) {x} {x} frac(x,y)

Perhaps someone can enlighten me here: R> x <- factor(LETTERS[1:3]) R> x [1] A B C R> mode(x) [1] "factor" R> class(x) [1] "factor" R> mode(unclass(x)) [1] "factor" S-PLUS has > x <- factor(LETTERS[1:3]) > mode(x) [1] "numeric" > class(x) [1] "factor" > mode(unclass(x)) [1] "numeric" ???

Can you confirm this problem : ###--------- RESHAPING x11() window has more problems: ---- x11() plot(1:8)# as expected: <<<<<<<< NO Problem, if you OMIT this plot !! ##-- now RESHAPE the x11() - window ! par(pty = 's') # should make SQUARE plotting region plot(1:8) #-- oops, not yet... plot(1:8) # now !

In the future (say after release 0.5 goes out), would it be feasible to start a publically-accessible list of bug reports, known bugs, and patches? (Something like the current TASKS list, but maybe a little bit more dynamic?) Benjamin Bolker Dep't of Ecology and Evolutionary Biology, ben@eno.princeton.edu Princeton University tel: (609) 258-6886, fax: (609) 258-1334

In the future (say after release 0.5 goes out), would it be feasible to start a publically-accessible list of bug reports, known bugs, and patches? (Something like the current TASKS list, but maybe a little bit more dynamic?) Benjamin Bolker Dep't of Ecology and Evolutionary Biology, ben@eno.princeton.edu Princeton University tel: (609) 258-6886, fax: (609) 258-1334