similar to: (PR#1577) is.na<- coerces character vectors to be factors

Displaying 20 results from an estimated 11000 matches similar to: "(PR#1577) is.na<- coerces character vectors to be factors"

2002 May 20
0
is.na<- coerces character vectors to be factors within dataframes (PR#1577)
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 =
2001 Oct 04
1
Strange behavior with saved character vectors containing a slash
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
2002 Apr 08
2
subsetting with NA's
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
2001 Oct 04
1
Bug when trying to save a character vector with an embedded / (PR#1115)
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
2001 Nov 29
3
package argument to library as string
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
2001 Aug 31
1
--quiet flag sets echo option to TRUE (PR#1083)
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
2002 Apr 30
3
rbind'ing empty rows in dataframes in 1.4.1 versus 1.5.0
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
2001 Nov 06
1
R CMD check, undoc and package checking
As cool and wonderful as the package checking tools for R are, I sometimes am stymied when trying to track down a problem. For example, I occasionally see error messages when running R CMD check like the following: [...] * checking Rd files ... OK * checking for undocumented objects ... ERROR * in parse(file, n, text, prompt) : syntax error on line 932 * in undoc(dir =
2002 Jul 10
1
bug in all.equal.character (PR#1767)
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
2002 May 16
0
is.na() can coerce character vectors to be factors within a dataframe
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
2002 May 21
1
I() fails on objects of class POSIXct (PR#1587)
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
2001 Oct 04
1
Problems merging with POSIXct objects and all = TRUE
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
2002 May 29
1
merge.data.frame can coerce character vectors to factor in some circumstances (PR#1608)
If the following two conditions are met: 1) all.x is TRUE 2) at least 1 row in y does not have a match in x then any character vectors in y will be coerced to be factors. Here is a simple example (previously provided on r-devel): > x <- data.frame(a = 1:4) > y <- data.frame(b = LETTERS[1:3]) > y$b <- as.character(y$b) > z <- merge(x, y, by = 0, all.x = TRUE) > z
2002 May 14
0
FW: Summary of Suggestions for poor man's parallel processing
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:
2002 Apr 30
2
display of character NA's in a dataframe in 1.5.0
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 =
2002 May 08
3
Suggestions for poor man's parallel processing
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
2002 Aug 13
2
Misalignment of <NA> in rownames (PR#1905)
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
2002 Aug 28
2
NA rownames in dataframes
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
2001 Sep 26
1
Characters vectors, NA's and "" in merges
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
1999 Apr 13
1
outer fails with group generic operations on factors (PR#166)
B <- A <- factor(c("a", "b")) outer(A, B, "!=") Warning: "FUN" not meaningful for factors [,1] [,2] [1,] NA NA [2,] NA NA Now, this used to work in 0.63.2, but someone `improved' outer. There it did an implicit as.numeric. The problem is that get in match.fun does not understand group generics, and gets Browse[1]> FUN