similar to: syntax confusion with function/non-function objects (PR#694)

I was surprised to find that the variance of a scalar, using var(), is NA. Surely this should be zero? Cheers, Jonathan. --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 = 0 minor = 99.0 year = 2000 month = February day = 9 language = R Search Path: .GlobalEnv,

I find this a bit puzzling ... > solve(matrix(c(5, 2, 3, 1), 2, 2), c(Inf, 3)) [1] NaN Inf > solve(matrix(c(5, 2, 3, 1), 2, 2)) %*% c(Inf, 3) [,1] [1,] -Inf [2,] Inf I would expect the answer to be c(-Inf, Inf), so why has the -Inf been replaced by NaN in solve? Cheers, Jonathan. --please do not edit the information below-- Version: platform = sparc-sun-solaris2.7 arch = sparc

The following commands z <- matrix(seq(0, 1, len=1000)) image(z, 1, z, zlim=c(0, 1), col=gray(1:10/10)) appear to violate the image functionality as described on the help page. As I understand it, by specifying a zlim of c(0, 1) and a colour vector of length 10, the colours should correspond to the intervals (0, 0.1), (0.1, 0.2), ..., (0.9, 1.0), this being 10 equally-spaced intervals on (0,

Hi everyone, Is there any reason why we should not automatically coerce a factor supplied as an argument to col in a plotting function? The following modification (to R-1.6.1) seems pretty harmless > plot.xy function (xy, type, pch = 1, lty = "solid", col = par("fg"), bg = NA, cex = 1, ...) { if (is.factor(col)) col <- codes(col)

Hi Everyone, At the moment it is not possible to replicate complex lists, but only simple ones: > rep(list(fred = 1:10), 10) # works fine > rep(list(fred = 1:10, happy = "squash"), 10) Error in rep(list(fred = 1:10, happy = "squash"), 10) : Unimplemented feature in rep There is nothing in ?rep that suggests that the latter should not work, and I think it would

Might it be possible to tighten the definition of "is.qr". I noticed that after I mistakenly typed example(lm) # make lm object named lm.D9 qr.Q(lm.D9) which exhausted the heap memory and produced two warning messages. As an object of class "lm" has a "qr" component, "is.qr" failed to detect that "lm.D9" was not a "qr" object. The

Hi everyone, There is no mention in ?new.env (R-1.6.0) of what the effect of setting the hash argument of new.env() actually does. What does it mean in performance terms to say that "the environment will be hashed"? Thanks, Jonathan. -- Jonathan Rougier Science Laboratories Department of Mathematical Sciences South Road University of Durham

Here's a nasty one. The following has caused a segmentation fault and possibly also a bus error. fred <- 1:6 dim(fred) <- 6 dimnames(fred) <- list(LETTERS[1:6]) mm <- matrix(1:12, 2, 6) mm %*% fred # segmentation fault here In the case without the dimnames assignment the result is OK. Cheers, Jonathan. --please do not edit the information below-- Version: platform =

Hi Everyone, I have modified my version of R-1.4.1 to include choleski with pivoting (like in Splus). I thought R-core might consider including this in the next version of R, so I give below the steps required to facilitate this. 1. Copied Linpack routine "dchdc.f" into src/appl 2. Inserted line F77_SUBROUTINE(dchdc) in src/appl/ROUTINES 3. Inserted "dchdc.f" into

Hi everyone, I encountered unexpected behaviour when calling "missing" within a "local" environment, namely fred <- function(x, y) { x <- as.vector(x) local({ dontwantme <- 1:100 if (missing(y)) print("No \"y\" today") }) x } whereupon I get > fred(1:10) Error in eval(expr, envir, enclos) : "missing" illegal use of

This situation arose in a computer practical this morning. A student overwrote "c" with a function. This messes up lots of things, but it is difficult to remove the function "c" from the global environment because it is used as a function in both "rm" and "remove". [The solution was to reassign "c" as a number, and then remove it.] Would it be

This is the result of my make check, could anyone help me out on this one? Formats: text example running code in 'base-Ex.R' ...*** Error code 1 make: Fatal error: Command failed for target `base-Ex.Rout' Current working directory /apps/R/R-1.6.0/tests/Examples *** Error code 1 make: Fatal error: Command failed for target `test-Examples-Base' Current working directory

In the optim() documentation, the control parameter "maxit" says "There is no other stopping criteria." That should be "are", or "criterion" ... While I'm at it -- poking at the code a little bit, it looks as if the initial simplex is set from the initial point by displacing each parameter value by max(0.1,0.1*pmax(fabs(Bvec))), where Bvec is the

Hi all, is it possible to create a multidemensional list? Haven't found anything in the list() help page. Thanks, Sven -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe" (in the "body", not the subject !)

Dear list I have a simple question that I have a mental block on: Having used a loop (from i = 1 to n) to assign some numerical values to row.list[[i]] e.g. row.list[[3]]= 0 1 I am wanting to combine the output into a simple matrix. for example, if I combine the output from persons 1 to 3 into a matrix, I thought I could do : h<-rbind(row.list[[1]]:row.list[[3]]) However, I get the

The "bug" is that it doesn't print anything; one might argue that this is not a bug, since such an array *is* empty, but I don't buy that argument. It *does* print if #{columns} (= last dimension) > 0 : > array(NA,dim=c(2,0)) > array(NA,dim=c(2,1,0)) > array(NA,dim=c(0,2)) [,1] [,2] > array(NA,dim=c(0,2,1)) , , 1 [,1] [,2] >

The following seems to be odd behaviour: fred <- 1:10 mode(fred) # "numeric" exists("fred") # TRUE exists("fred", mode="numeric") # FALSE Unless I have misunderstood, the final evaluation should be TRUE, as an object called "fred" exists and its mode is "numeric". In the same category, I have just noticed that get("fred")

Hi Everyone, The following rather extreme claim on memory causes a segmentation fault on my installation: fred <- matrix(1:1200, 20, 60) littleOP <- function(x, y) { z <- as.vector(x) %*% t(as.vector(y)) dim(z) <- c(dim(x), dim(y)) z } littleOP(fred, fred) # this is OK littleOP(littleOP(fred, fred), fred) # whoops! Segmentation fault What's a bit strange

Okay, I stumped. I'm trying to build a matrix or data.frame that consists of values by group. For example, resid, group 574 0.536196370873122 E 575 0.93191093696265 E 576 -1.27116094894117 A 577 -1.05159666055027 A 578 0.398273458301184 D 579 0.586373126102573 E 580 0.806575304513802 E 581 0.897258393118338 E 582 0.342393324256838 D 583 0.781245511773227 E I

I get a segmentation fault as follows: > tmp <- array(list(), c(3, 4)) > tmp[[1, 2]] NULL # as expected > tmp[[1, 2]]$fred <- 1:10 > tmp # as expected [,1] [,2] [,3] [,4] [1,] "NULL" "List,1" "NULL" "NULL" [2,] "NULL" "NULL"