similar to: NA as names of vector from subscripted matrix == bug ?

Displaying 20 results from an estimated 5000 matches similar to: "NA as names of vector from subscripted matrix == bug ?"

2001 Jun 18
1
"[.data.frame" allows un-named 3rd subscript (PR#989)
Since the Extract page has usage as: x[i, j, ... , drop=TRUE] I would expect that 'drop=' would need to be given to the third 'subscript' > diag(4)[ , 4 , 4 ] # Forgot 'drop=' or added extra ',' Error in diag(4)[, 4, 4] : incorrect number of dimensions > > as.data.frame( diag(4) )[ , 4 , 4 ] # should return error, right? [1] 0 0 0 1 Also note:
1999 Dec 10
1
split nukes names() (PR#371)
> split(c(a=1,b=2),c(1,2)) $"1" [1] 1 $"2" [1] 2 The documentation does not *promise* that names will survive, but in Splus3.4, they do. This broke a function that worked under S+ that used the names attribute of elements in the components returned by split. Chuck Berry --please do not edit the information below-- Version: platform = sparc-sun-solaris2.7 arch = sparc
2001 Mar 23
0
cor(x,y) when is.null(y) (PR#883)
Problem: > names(my.dat) [1] "x" "y" > cor(my.dat$x,my.dat$y) # desired result [1] 0.8660254 > cor(my.dat$x,my.dat$y.NOT) # typo [1] 1 > I'd prefer a warning() or stop() in that case. Solution (??) : *** 1,5 **** --- 1,7 ---- cor <- function (x, y=NULL, use="all.obs") { + if (is.null(y) && !is.null( match.call()$y ) ) +
2000 Mar 13
1
plot(1:10,c(1)$nothing) yields index plot (PR#482)
<<insert bug report here>> IMHO, plot(x,c(1)$nothing) should fail or at least issue a warning. Instead it produces an index plot of the first argument, i.e. plot(x) Chuck Berry --please do not edit the information below-- Version: platform = sparc-sun-solaris2.7 arch = sparc os = solaris2.7 system = sparc, solaris2.7 status = Patched major = 1 minor = 0.0 year = 2000
2000 Nov 08
1
substitute(x$y)) corrupts 'y' component (PR#731)
viz. > (function(x,y=a) substitute(x$y))(x) x$a > (function(x,y=a) substitute(x$y))(list(y=1:3)) list(y = 1:3)$a > (function(x,y) eval(substitute(substitute(y))))(x=list(y=1:3),y=x$y) list(y = 1:3)$x$y The behavior I expect and want is like that in Splus 3.4: > (function(x,y=a) substitute(x$y))(x) x$y > (function(x,y=a) substitute(x$y))(list(y=1:3)) list(y = 1:3)$y >
2000 Feb 17
2
"a.matrix[a.char.matrix]<- " crashes R (PR#447)
To wit: --- > junk <- array(3,c(10,3),dimnames=list(as.character(1:10),as.character(1:3))) > junk[cbind(as.character(1:5),as.character(c(1,2,3,2,3)))] <- 20 > > junk Process R segmentation violation (core dumped) at Wed Feb 16 15:57:49 2000 --- I know that the use of a ***character*** matrix is not documented for this context. Still, it should not crash R. In addition to
2000 Mar 12
1
make check fails after base-Ex.R
Dear R-help, I tried to build the R-release version of R-1.0.0. ./configure and make seemed to go just fine. When I ran 'make check' from $RHOME, it dumped core apparently in the quit('no') on the last line of base-Ex.R I had been having some problems with a package I am building in that R would report with "Process R segmentation violation (core dumped)" upon
1999 Nov 11
2
dimname'less array breaks apply (PR#318)
<<insert bug report here>> > apply(array(1:20,c(2,2,5)),2:3,function(x) x) Error: length of dimnames must match that of dims > Changing: dimnames = if (is.null(dn.ans)) list(ans.names, NULL) else c(list(ans.names), dn.ans) To: dimnames = if (length(dn)==0) NULL else if (is.null(dn.ans)) list(ans.names, NULL) else c(list(ans.names), dn.ans) seems to fix this. Chuck
2000 Sep 29
2
all.equal.list() sometimes fails with unnamed and named components (PR#674)
examples: 1) Fails to report that components 2 and 3 differ all.equal(list(1,2,3,zap=1),list(1,3,4,zap=2)) [1] "Component zap: Mean relative difference: 1 2) Incorrectly asserts all are equal when components 2 and 3 differ > all.equal(list(1,2,3,zap=1),list(1,3,4,zap=1)) [1] TRUE 3) Removing named component reveals differences: > all.equal(list(1,2,3,1),list(1,3,4,1)) [1]
2001 Nov 29
1
rug(x) clip warning incorrect if par("xlog")==TRUE (PR#1188)
To wit: > plot(1:2,1:2,log="x") > rug(1:2) # should not warn Warning message: some values will be clipped in: rug(1:2) > plot(1:2,1:2,log="x") > rug(c(0,.1,.2)) # should warn, but does not > I believe this fixes the problem: % diff -c /tmp/orig.rug.R /tmp/cberry.rug.R *** /tmp/orig.rug.R Thu Nov 29 12:59:00 2001 --- /tmp/cberry.rug.R Thu Nov 29
2001 Mar 03
0
bqtl available on CRAN
Package bqtl version 1.0 is now available on CRAN. Description: QTL mapping toolkit for inbred crosses and recombinant inbred lines. Includes maximum likelihood and Bayesian tools. I am keen to have comments about this package including implementation details, additional functionality, and (of course) problems and bugs. Chuck Berry -- Charles C. Berry (858) 534-2098
2004 Jan 21
1
cor( x, y , method = "spearman" ) incorrect if any( is.na(c( x, y (PR#6448)
> version _ platform i686-pc-linux-gnu arch i686 os linux-gnu system i686, linux-gnu status major 1 minor 8.1 year 2003 month 11 day 21 language R > cor( 1:3, rep(NA,3) ) # OK Error in cor(1:3, rep(NA, 3)) :
2000 Mar 26
1
matlines, matpoints don't follow prototype (PR#506)
The Blue Book allows the 'type' argument to be used in matpoints and matlines. matlines(x, y, type="l", lty=1:5, pch=, col=1:4) R-1.0.0 does not. Thus, type="h", "b", must be invoked thru matplot( x, y, type = "h", add=TRUE) For the sake of consistency with S, it would be nice to have matlines defined as: "matlines" <-
1998 Aug 14
1
R-beta: ld problem/SunOS/gcc/g77
In trying to compile R-0.62.2 on my SPARC SunOS: tajo% uname -a SunOS tajo 4.1.3_U1 1 sun4m with gcc/g77, I ran into gcc -o R.binary [deleted] ../lib/libmath.a -L/usr/openwin/lib -lX11 -ldl -ltermcap -lm -lf2c collect2: ld returned 2 exit status ld: /lib/libm.a(lgamma.o): _gamma: multiply defined ld: /lib/libm.a(lgamma.o): _lgamma: multiply defined *** Error code 1 make: Fatal error:
2000 Mar 07
2
lm(rnorm(1000)~rnorm(1000)) kills rw1000 (PR#476)
First: R core: (Thank You!)^HUGE_VAL Now, down to business: In a loop or in repeated command lines: system.time(lm(rnorm(1000)~rnorm(1000))) ( or lm(rnorm(1000)~rnorm(1000))$coef ) fails after several iterations with the Windows message 'This program has performed an illegal operation and will be shut down. If the problem persists, please contact the vendor'. clicking on DETAILS
2004 Jul 21
0
loglin( tab, margin, start = bad.start ) kills R (PR#7123)
> tab <- array( sample(3^5), rep(3,5) ) > loglin( tab, list(1,2,3,4,5) )[[1]] # AOK 2 iterations: deviation 5.456968e-12 [1] 10909.89 > loglin( tab, list(1,2,3,4,5), c(1,2,3) )[[1]] # OUCH! Process R bus error at Wed Jul 21 17:03:55 2004 this is inconsistent - sometimes issuing this msg several times before barfing: Error in switch(z$ifault, stop("This should not
2003 Jul 24
0
unz( "x.zip", "y.csv" ) != pipe( "unzip -p x.zip y.csv" )
Not sure this is a bug in R. Maybe its a bug in my understanding of unz(). The character 'b2' (hexadecimal) is in position 535 of line 1 of 'naughty.csv'. This character appears as superscript '2' and came to me in an EXCEL file that I converted to text in a comma separated ( *.csv ) format. The first line gets truncated by readLines after 534 characters using unz():
2002 Jul 17
2
Build on Solaris 8 gcc-3.1 fails make check
Dear R-help, I am trying to build R-1.5.1 on a Sun Blade 100 (sparc). It fails make check when var(1) returns NaN instead of NA. Using gcc-2.95.3 from sunfreeware.com, the build succeeds and passes make check I have: Solaris 8 gcc-3.1 (built on that machine from sources and installed in /usr/local/gcc-3.1 with binaries symlink'ed to /usr/local/bin) A synopsis is at the bottom of
2002 Jul 17
2
Build on Solaris 8 gcc-3.1 fails make check
Dear R-help, I am trying to build R-1.5.1 on a Sun Blade 100 (sparc). It fails make check when var(1) returns NaN instead of NA. Using gcc-2.95.3 from sunfreeware.com, the build succeeds and passes make check I have: Solaris 8 gcc-3.1 (built on that machine from sources and installed in /usr/local/gcc-3.1 with binaries symlink'ed to /usr/local/bin) A synopsis is at the bottom of
2000 Dec 22
1
rw1020 Rcmd INSTALL path\ deletes rw1020\library\* (PR#789)
The trailing backslash seems to be the culprit. After looking at rw1020\bin\INSTALL, I noticed $pkg =~ s/\/$//; which I assume is to strip the trailing slash from a package name before obtaining the package name and cleaning out its directory I added $pkg =~ s/\\$//; immediately after this line. Rerunning Rcmd INSTALL C:\rw1011\src\library\bqtl\ with that change seemed to work OK