similar to: R-mailinglists will be "on hold" for a few hours on Saturday.

Displaying 20 results from an estimated 10000 matches similar to: "R-mailinglists will be "on hold" for a few hours on Saturday."

1999 Mar 18
0
Major Internet disruption to/from ETH Zurich...
The big Swiss University network provider has been having severe problems for about 8 hours now --- particularly the cross-atlantic connection seems broken --- Many of you will get R-help or ESS-help E-mails very much delayed. Hope things start working soon by themselves. [for those that are disrupted: When you get this message, things should be back to normal; otherwise you wouldn't have
1998 Jan 23
0
S-Plus graphs to LaTeX picture commands
Well, R ( http://lib.stat.cmu.edu/R/CRAN/ ) has a pictex(..) driver. >>>>> "kjetil" == kjetil halvorsen <kjetil@caoba.entelnet.bo> writes: kjetil> Is there any possibility to write code which ``translates'' kjetil> from splus graphics to latex picture commands? Or somebody has kjetil> written something like that? kjetil> I did
1998 May 06
1
min(numeric(0)) = ? -- proposal for "S incompatible change"
[Same question for max(.), cummin(.) and cummax(.)] In S, S-plus and R, this currently gives NA. I wonder if it wouldn't make more sense to follow common mathematical/logical reasoning here: min { empty set } = +Inf max { empty set } = -Inf (For integers, these would be INT_MAX and INT_MIN, respectively). Maybe this is a real ``first time'': I am proposing a change which
1998 Jun 02
0
"fgrep" for help \\ IBM PowerPC AIX
>>>>> "TL" == Thomas Lumley <thomas@biostat.washington.edu> writes: TL> ...... TL> Currently "%*%" doesn't have any help but help TL> requests get routed to Arith, because "%*%" as a regular expression TL> matches "%%". I will add this to the special cases in help(), but TL> should we use fgrep
1998 Jul 01
0
"Coding conventions" for R: Use TRUE & FALSE, and not T & F
The reason being a design decision of a while ago that "T" and "F" shouldn't be reserved words in R as they are in S-plus. Hence, T & F are just variables being set to TRUE and FALSE respectively; they *can* be overwritten by the user which is very useful e.g., when you do mydat <- read.table(file, header =TRUE) and the file has variable names "T" or
1998 Sep 09
0
R help Web page
[CC'ed to R-devel, since it should be of interest to more ..] >>>>> "Guy" == Guy Nason <G.P.Nason@Bristol.ac.uk> writes: Guy> Dear Martin, Hope you are well. I am trying to start to get my Guy> [new] WaveThresh package working for R. Great, thank you! Can you make sure that your Examples (.EX in S syntax; \examples{..} in *.Rd) are directly
1998 Oct 30
0
R 0.63 testers help: Please "(cd tests; make print-tests.Rout)"
R 0.63 only ------------ (0.62 does not have the print-tests.Rout.save against which to diff!) I'd be glad if some of you could help us find out some printing/formatting differences of the same R version on different architectures. I have the suspiscion that the new glibc aka libc-6 (Linux), has changed some of the internal printing/formatting code [fprintf ..]. One consequence is that
1998 Dec 01
0
Random Number Generators, .Random.seed and all that..
As some of you know, we have been thinking of allowing the possibility of a CHOICE of the kind of random number generator (=: RNG) to use in R. The current R-release snapshot even has some code in it; however, this will be changed quite a bit. Here is a kind of informal RFC (request for comments / request for criticism / ..): 1a. With the new scheme, we still want that save(..) &
1999 Aug 13
0
scan() + error interferes with count.fields() in some cases (PR#248)
As just mentioned on R-devel, and originally reported (somewhat less concisely) by Adrian Trapletti, This code write(c(paste("\"", LETTERS[1:3],"\"", sep=""),1:3), nc=3) scan("data") # gives error as it should count.fields("data") # will be wrong count.fields("data") # is now ok : 3 3 gives (in 0.64.2 and in 0.65
1999 Feb 05
0
[Fwd] Problems installing R on SunOS 4.1.4
[forwarded to R-devel, where this really belongs] >>>>> "Samira" == Samira M Ismail <samira@ime.unicamp.br> writes: (to me in a private mail) Samira> We have been trying to install R.0.63 for Unix (SunOS 4.1.4 - Samira> SPARC 20) and we detected the following problem which makes Samira> impossible to run R. We have got the following message:
1998 Aug 14
0
R-beta: Book "Data Analysis with R" (undergrad. teaching) ??
This was ``accidentally'' only sent to me. But I think the question (and possibly answers) should be relevant to much more people! >> To: maechler at stat.math.ethz.ch >> Subject: manual >> From: Pat Altham <P.M.E.Altham at statslab.cam.ac.uk> >> Date: Thu, 13 Aug 1998 11:34:31 +0100 >> >> Could you kindly email me (or tell me how to obtain)
1998 Nov 09
1
Proposal for discussion: COLNAMES & ROWNAMES
Looking into several different parts of R../src/library/base/R/*.R has led me to the conclusion that quite a bit of code doubling could be saved by using the following two functions whose naming philosophy is derived from that of NROW() & NCOL(): COLNAMES <- function(x) if(is.null(n <- colnames(x))) paste(seq(length=NCOL(x))) else n ROWNAMES <- function(x)
1999 Mar 09
1
example(.) partly broken (since 0.63.3) --> patch (PR#134)
(I don't have time just now to diagnose & fix..) In R 0.63.3 [both on Solaris and Linux] > example(outer) Error: Couldn't find 'outer' example whereas this worked in 0.63.2. NON-exhaustive `research' [i.e. small sample out of about 1000]: o examples that stopped working (in 0.63.3 and did before) kronecker, outer, vector, Im o Examples working
1998 Mar 04
1
pretty(.) bug -- fix --> "compatibility" ?
In current versions of R, pretty(333) gives an infinite loop (due to a silent integer overflow in src/appl/pretty.c). I've looked at this problem and also at what S-plus does, (no code there to inspect, just experiments), and then I have fixed pretty.c. I think that it now behaves much more reasonably (both than before and than S / S-plus). The only problem: pretty(.) is not
1999 Jan 20
1
data frames with non-unique row.names
In R and S, the general idea is that data.frames must have unique row.names (aka dimnames(.)[[1]]). Several observations / problems (in R *and* S !). [Example code at the end] 1) Both in S and R, data.frame(..) (and e.g., also cbind(<data.frame>, ..) which dispatches to data.frame()) silently drops the whole row.names and replaces it by "1" "2" ...
1998 Jan 16
1
data.frame(...) not constructing "1:n" row.names [diff. S <--> R]
[I think Doug Bates has already alluded to this, somewhere..] In R, data.frame( ... ) does not construct row.names whereas in S, it does: R: > data.frame(x=1:2,y=3:4) x y [1,] 1 3 [2,] 2 4 > row.names(data.frame(x=1:2,y=3:4)) NULL S-plus: > data.frame(x=1:2,y=3:4) x y 1 1 3 2 2 4 > row.names(data.frame(x=1:2,y=3:4)) [1] "1" "2"
1998 Mar 25
2
R alpha/beta naming
Read this morning >>> R : Copyright 1998, Robert Gentleman and Ross Ihaka >>> Version 0.61.2 Alpha (March 15, 1998) ----- So, there still is no "R beta" around.... - If I didn't know R, would I use a statistics software, if it was still in alpha testing state? - Is this really what we want to tell people about R? More to the point: I think, we could
1998 Jun 30
2
gl() in S -- puzzle
In order to run some R examples in S & Splus, I want the gl() function in S. In R, it is gl <- function (n, k, length = n * k, labels = 1:n, ordered = FALSE) factor(rep(rep(1:n, rep(k, n)), length = length), labels = labels, ordered = ordered) Since S's factor() has no "ordered= F" argument, in S we need to call ordered() instead of factor() in the case of
1999 Jan 22
1
backsolve... --> class()es for special matrices ?
>>>>> "JonR" == Jonathan Rougier <J.C.Rougier@durham.ac.uk> writes: JonR> ... By the way, I have `solve' JonR> methods for triangular matrices and variance matrices -- would JonR> you be interested? { Jonathan, I hope it's okay if I CC this to R-devel; this must be of a wider interest } Ye.e..s; for triangular ones,
1999 Jun 23
1
coercing factors to matrix() --> num/char ? -- inconsistencies|?
The old factor() wars...... {{maybe don't just report that factor()s are broken by design..}} If ff is a factor, e.g., ff <- as.factor(rep(1:2,3)) f2 <- ff; levels(f2) <- c("Lo","Hi") 1) we don't allow {in R as in S-plus 3.x} arithmetic on factors, i.e. 1 + ff gives an error, and I think most of us believe this is as desired. {{if one