similar to: Suggestions for poor man's parallel processing

Thanks to Luke Tierney, Agustin Lobo, Stephen Eglen, A.J. Rossini, Simon Wood and Timothy H. Keitt for responding to my question about poor man's parallel processing. Much of the substantive material was cc'ed to r-help already, but my take is as follows. 1) Currently, there is nothing "simple" for solving my problem. 2) I thought that Timothy Keitt's description of the use

It turns out that my web host doesn't allow direct links. Try going to http://www.warnes.net/downloads or getting it from the sourceforge snippet library https://sourceforge.net/snippet/detail.php?type=snippet&id=101149. -Greg > -----Original Message----- > From: Warnes, Gregory R [mailto:gregory_r_warnes at groton.pfizer.com] > Sent: Monday, May 13, 2002 10:15 AM > To:

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

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)

In previous versions of R (at least in 1.5.1, I think), my practice was not to include an INDEX file in the package. R CMD check did not complain and an INDEX was created for me when I use R CMD build. At least, this is how I remember it. I thought that this was a good way to behave since it ensured that my INDEX was automatically kept up to date by R, without me having to worry about what

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 =

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

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

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

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

Hi all, I'm trying to get the snow package with mpi working on my linux ubuntu 10.04 machine. When I tried to install it (see below) it already had problems with the dependencies. R version 2.14.0 (2011-10-31) Copyright (C) 2011 The R Foundation for Statistical Computing ISBN 3-900051-07-0 Platform: x86_64-pc-linux-gnu (64-bit) R is free software and comes with ABSOLUTELY NO WARRANTY. You

Dear R-help, Has anyone tried running R on a Beowulf-type cluster? I can get R to run in batch (using R CMD BATCH) on a cluster, but am wondering if it is possible to get an interactive R session on a compute node. Right now, if I run: beorun --nolocal R I just get the R start-up message and back to the shell prompt. If I try bpsh 0 R I can get R started (but the R prompt does not

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

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

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

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

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