similar to: na.exclude equivalent

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

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

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 Martyn Plummer and Vele Samak for taking the time to answer my problem. scan certainly will do the trick. However, having taken a look at the code for read.table, it seems to me that I might be able to add in a "what" argument and then just pass it down to the call to scan. But that won't be today's project . . . Dave Kane

Has the likely release date for R 1.4.1 been set? Apologies if there is some obvious place on the web site that I could have looked this up at. We are eager to upgrade to 1.4, but some of the bugs matter to us. We have played around with the patched code, but have mainly succeeded in demonstrating that we need to learn more about UNIX code development . . . Thanks to all for a most excellent

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:

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

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

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

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

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

R CMD check fails when the Depends field in the DESCRIPTION file includes a single package with `.' in the name. * checking for file 'financials/DESCRIPTION' ... OK * checking package directory ... OK * checking DESCRIPTION Package field ... OK * checking DESCRIPTION Version field ... OK * checking DESCRIPTION License field ... OK * checking DESCRIPTION Description field ... OK *

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

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

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

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

Hi, We are considering organizing some of our ascii files with multiple "column names" like so: a.long.but.complete.name a.different.complex.name short.name.1 short.name.2 1 7 2 8 3 9 [more data] The basic idea is that we want to keep, in one location, both a long descriptive name of each variable (in row 1) and a short convenient name (in row 2). I could imagine keeping other

I know that there must be a cool way of doing this, but I can't think of it. Let's say I have an dataframe with NA's. > x <- data.frame(a = c(0,1,2,NA), b = c(0,NA,1,2), c = c(NA, 0, 1, 2)) > x a b c 1 0 0 NA 2 1 NA 0 3 2 1 1 4 NA 2 2 > I know it is easy to replace all the NA's with zeroes. > x[is.na(x)] <- 0 > x a b c 1 0 0 0 2 1 0 0 3 2 1