similar to: variations in how long commands take

Hi, I think that there is something that I am misunderstanding in creating tables using dates that are of class POSIXct. Consider: > x <- data.frame(date = as.POSIXct(strptime(c(rep("2002-10-17", 4), rep("1999-12-08", 2)), format = "%Y-%m-%d"))) > x date 1 2002-10-17 2 2002-10-17 3 2002-10-17 4 2002-10-17 5 1999-12-08 6 1999-12-08 > table(x$date)

Full_Name: Sharon Kuhlmann Version: 0.99 OS: solaris2.6 Submission from: (NULL) (129.16.167.231) When I use the function > eigen(x), it gives me a "Process R bus error", and the program quits. I'm running the following R version: platform sparc-sun-solaris2.6 arch sparc os solaris2.6 system sparc, solaris2.6 status Patched

Hi, In 1.4.1, I was able to create extra "empty" rows in a dataframe as so: > x <- data.frame(a = letters[1:3], b = 1:3) > x a b 1 a 1 2 b 2 3 c 3 > x[4,] a b NA NA NA > rbind(x, x[4,]) a b 1 a 1 2 b 2 3 c 3 NA NA NA > R.version _ platform sparc-sun-solaris2.6 arch sparc os solaris2.6

I seem to remember an error like this being mentioned before, but if it wasn't: > zz <- density(rnorm(100)) > plot(zz) Error in plot.new() : Figure margins too large > version _ platform sparc-sun-solaris2.6 arch sparc os solaris2.6 system sparc, solaris2.6 status major 0 minor 90.1 year 1999 month December day 15 language R Paul Gilbert

I don't seem to be able to initialize a vector of NAs. I hope this is a bug and not a new feature (I realize I have not paid much attention to a lot of recent discussion about NA): platform sparc-sun-solaris2.6 arch sparc os solaris2.6 system sparc, solaris2.6 status major 1 minor 5.0 year

You get a warning message when you specify a ylab parameter while plotting data whose x's are POSIXct values. Apparently the `axis.POSIXct' method tries to reset the ylab---via the ... parameter---after it has already been set by higher level methods. Here is a function that illustrates the problem. ylabProblem <- function() { x <- ISOdate(2003, 4, 1:10) # POSIXct

Hello List, Knowing I would eventually need to ask for help on the list, I've held off my thanks and congratulations on the 1.+ releases of R. I am amazed at the dedication of the R-core team, and do add my applause and thanks. I've had a compile problem with the latest version which has not occurred before. I'm compiling under: platform sparc-sun-solaris2.6 arch sparc

I was surprised not to find dev.ask when I looked for it. Is there an alternative method of holding plots before going on to the next one? > R.version _ platform sparc-sun-solaris2.6 arch sparc os solaris2.6 system sparc, solaris2.6 status major 1 minor 1.1 year

Typically, when I use strptime with "impossible" dates I get an NA, which is what I expect. > version _ platform sparc-sun-solaris2.6 arch sparc os solaris2.6 system sparc, solaris2.6 status major 1 minor 3.0 year 2001 month 06

Hello everybody, if I'm using par(xpd=NA) gridlines will plotted outside the plotting region. This is "new" (and, in my opinion, unaesthetic) in version 1.4 - compared to version 1.3. Is this a bug or a feature? Example: ------------------ par(xpd=NA) plot(1:11) grid() ------------------ platform sparc-sun-solaris2.6 arch sparc os solaris2.6

To whom should bug reports of the R port of acepack be directed? On a SPARC/Solaris 2.6 or 2.7 (SunOS 5.6 or 5.7) system running R-1.0.0 the avas example fails > library(acepack) > example(avas) avas> TWOPI <- 8 * atan(1) avas> x <- runif(200, 0, TWOPI) avas> y <- exp(sin(x) + rnorm(200)/2) avas> a <- avas(x, y) Process R bus error (core dumped) at Mon

R> order(1, na.last=NA) Error in apply(sapply(z, is.na), 1, any) : dim(X) must have a positive length This bug appears unrelated to PR#1906, and so the fix of 8/15 doesn't help. It comes from the line inside order(): ok <- !apply(sapply(z, is.na), 1, any) where z=list(1) in my example. sapply() returns a single-element vector, not a matrix, making apply() unhappy. This might

Here's a simple example: > x <- rnorm(20) > y <- 1 + 10*x + rnorm(20) > plot(y ~ x, subset=2*(1:10),xlab="In",ylab="Out") Error in length(x) == l : comparison (1) is possible only for vector types The problem seems to be in this section of the code for plot.formula: if (!missing(subset)) { s <- eval(m$subset, data, parent.frame()) l

.. R is now configured for sparc-sun-solaris2.6 Source directory: . Installation directory: /unsup/R-0.64.2 C compiler: gcc -g -O2 FORTRAN compiler: g77 -O2 Gnome support: no $ gcc --version egcs-2.91.66 $ g77 --version GNU Fortran 0.5.24-19981002 "make check" later fails. The failure is in the test of the eigen() function. The

I often use merge with dataframes that contain character vectors which have elements that are sometimes "NA" (meaning the string NA, not the same thing, obviously, as NA in a numeric or factor vector). For example, the stock ticker for Nabisco was "NA". Unfortunately (for me), it seems like merge insists on inserting "NA" for missing values. My question: Is there some

Seems to be a day for finding peculiar little things. There is an inconsistency in the behavior of lm vis a vis glm: > x <- rnorm(15) > y <- 1 + 10*x + rnorm(15) > z <- as.factor(rep(c("A","B","C"),rep(5,3))) > xyz <- data.frame(x,y,z) > fit.lm <- lm(y ~ x + z, data=xyz, subset=(z != "C")) > fit.glm <- glm(y ~ x +

My xyplot has a number of panels, and I'd like a separate key for each rather than a single key for the entire set. However, I cannot find a way to pass multiple key definitions to xyplot's "key" argument. Allow me to throw out a simple example: require(methods) require(lattice) ## define sample data myFrame1 <- data.frame(a=1:100, b=rep(1:10,10), c=unlist(lapply(1:10, rep,

Almost all of the heavy crunching I do in R is like: > for(i in long.list){ + do.something(i) + } > collect.results() Since all the invocations of do.something are independent of one another, there is no reason that I can't run them in parallel. Since my machine has four processors, a natural way to do this is to divide up long.list into 4 pieces and then start 4 jobs, each of which

This seemed too advanced for r-help and is related to the recent discussion of character vectors in dataframes. Following Brian Ripley's most excellent advice, we are moving to a world in which character vectors in dataframes are always of class AsIs. The cool way of doing this seemed to be the following: > cat(c("x", "y", "z"), file = "test.txt",

I noticed this oddity about R profiling and setMethod. First, I "test out" Rprof. > require(methods) Loading required package: methods [1] TRUE > > Rprof("test.out") > data.frame("a") X.a. 1 a > Rprof(NULL) So far, so good. Next, I define myClass. > setClass("myClass", representation(mySlot = "numeric")) [1]