similar to: Warnings with no INDEX file in a package.

I have a package in which I would like to store a LaTeX .tex file. It is not documentation on any particular function, but is related to the package. In thought that I could just create a "doc" directory under the "inst" subdirectory and place it there. I thought that things in "inst" were just recursively copied when the package was installed. Alas, when I check the

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

Thanks to Henrik Bengtsson, Martin Maechler, Brian Ripley, Jeff Gentry and David Brahm for taking the time to answer my questions about INDEX files in R packages. My key take-aways were: 1) All of this will be changing a lot in R 1.7.0-to-be, so don't sweat the details. 2) Many people run R CMD build before they run R CMD check. I found this quite surprising. I did not realize that R

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

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

I often get warnings like the following when running R CMD check [...] * checking for code/documentation mismatches ... OK * checking tests ... make: *** Warning: File `Makevars' has modification time in the future (2001-11-13 12:54:37.381546042 > 2001-11-13 12:54:37.314975985) [...] I am ready to believe that this is not a bug (i.e., that the timing on my various machines and file

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",

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)

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

I understand that NA's in character vectors are displayed differently than NA's in factor vectors. > c("x", NA, "y") [1] "x" NA "y" > as.factor(c("x", NA, "y")) [1] x <NA> y Levels: x y That seems sensible enough. But shouldn't I see the same behavior in a dataframe? > test <- data.frame(a =

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

We are performming a series of S+ 6.0 versus R 1.3 comparisons. (If anyone has already written scripts for this purpose, we would be eager for a copy.) The purpose is to see if there are any "gotchas" -- places were S+ works and R doesn't -- that would prevent us from going all the way over to R. (We have lots of legacy code, so the conversion costs are non-trivial.) As part of this

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

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

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

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

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

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

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

Thanks to Brian Ripley for suggesting, to my previous post about a problem with merge, that I trace through merge.data.frame. I did so with my test case and all seemed to be well until I got to: if (all.x) for (i in seq(along = y)) is.na(y[[i]]) <- (lxy + 1):(lxy + nxx) I believe that this code sets observations in y (which has been expanded to be the