similar to: Problems merging with POSIXct objects and all = TRUE (PR#1121)

I am having problems using merge with all = TRUE when one of the dataframes has objects of class POSIXct. If this is a bug, let me know and I will report it to r-bugs. Here is an example: > version _ platform sparc-sun-solaris2.6 arch sparc os solaris2.6 system sparc, solaris2.6 status major 1

Although the documentation is somewhat sketchy, I() can be used to create objects of class AsIs: > I("a") [1] "a" attr(,"class") [1] "AsIs" "character" > I(4) [1] 4 attr(,"class") [1] "AsIs" "numeric" > I(4 + 0i) [1] 4+0i attr(,"class") [1] "AsIs" "complex" > This

The help for options says: echo: logical. Only used in non-interactive mode, when it controls whether input is echoed. Command-line options `--quiet' and `--slave' set this initially to `FALSE'. I don't think that this is correct for me. Consider the following session: mica|junk> ls test.R mica|junk> cat test.R cat("Why was this command

The inconsistency is that you use $<- to set the column, then [[<- to change it. Had you tried to set the column by x[[1]] <- as.character(x[[1]]) you would have seen the problem immediately (it does not work as you would have intended). If you want to be sure to turn off conversion to factor, you need to set the column to class "AsIs". My belief is that will behave

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)

Hi, I often have large dataframes with many variables and many NA's, from which I would like to subset out some rows. Here is a toy example: > x <- data.frame(a = c("x", "y", "z"), b = c(1, NA, 5)) > x a b 1 x 1 2 y NA 3 z 5 I realize that, if I know the values in x$b that I want to subset, things are easy: > x[x$b %in% c(1),] a b 1 x 1

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

Here is an example involving "VIA\B". > 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 day 22 language

The help page for library says that: package, help: name or character string giving the name of a package. Yet, I don't seem to be able to use a string variable here. > version _ platform sparc-sun-solaris2.6 arch sparc os solaris2.6 system sparc, solaris2.6 status major 1

There is a bug in all.equal.character: > all.equal.character(c("A", "B", "C"), c("A", "B", "C")) [1] TRUE > all.equal.character(c("A", "B", "C"), c("A", "B", NA)) Error in sum(out) : Object "out" not found > traceback() 3: sum(out) 2: paste("`is.NA' value

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

I am seeing some strange behavior using save on a character vector containing a slash. If this is a bug, I will happily submit it (as a single entry! ;-) ) to r-bugs. Here is an example involving "VIA\B". > version _ platform sparc-sun-solaris2.6 arch sparc os solaris2.6 system sparc, solaris2.6 status

R 2.6.1 on a Thinkpad T60 running up-to-date Gentoo: Despite the documentation, which says: 'strftime' is an alias for 'format.POSIXlt', and 'format.POSIXct' first converts to class '"POSIXlt"' by calling 'as.POSIXlt'. Note that only that conversion depends on the time zone. strftime fails on POSIXct objects: > foo <-

The result of rowsum() in R doesn't have the dimnames I'd expect, e.g.: > rowsum(matrix(1:12, 3,4), c("Y","X","Y")) [,1] [,2] [,3] [,4] 1 2 5 8 11 2 4 10 16 22 whereas S-Plus gives the more useful result: [,1] [,2] [,3] [,4] X 2 5 8 11 Y 4 10 16 22 This is because R's rowsum() code gives the

Environment variables set with Sys.putenv() disappear (i.e. become "") after a while, especially after heavy-duty I/O. Example: R> x <- matrix(1., 3000, 3000) R> save(x, file="myx.RData") R> Sys.putenv(HOME="/tmp") R> while (Sys.getenv("HOME") != "") {cat("ok\n"); load("myx.RData")} The loop prints

Hey everyone! I am seeing strange behavior with NA in the rownames of dataframes: > a <- data.frame(1:3, row.names = c("r1", NA, "r3")) > cbind(a) X1.3 r1 1 <NA> 2 r3 3 Everything works. The peculiar thing is that when the NA is in the first row, things no longer work as I would have expected: > b <- data.frame(1:3, row.names

I am not sure if this is a bug within is.na<- or if it lies deeper in the dataframe construction process. Indeed, perhaps it is not a bug at all (in which case I would suggest that the help page for NA be provided with a warning for unsuspecting users (like me)). When used on a character vector within a dataframe, is.na<- coerces the vector to factor. > x <- data.frame(var =

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

Full_Name: Kevin C. Bartz Version: 1.5.1 OS: Solaris 2.6 Submission from: (NULL) (192.223.226.5) A while ago, 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

An NA in the rownames of a matrix (or dataframe) causes misalignment when the matrix is printed: R> x <- matrix(1:12, 3,4, dimnames=list(letters[1:3], LETTERS[1:4])) R> rownames(x)[2] <- NA R> x A B C D a 1 4 7 10 <NA> 2 5 8 11 c 3 6 9 12 The bug is in function Rstrlen, in src/main/printutils.c. MatrixRowLabel and MatrixColumnLabel (same file) rely on Rstrlen