similar to: R-beta: Postscript command fails

Running R under Solaris 2.5.1 I get "Color allocation error". the offending line is lines(x,col="green4",lty="dotted") from the "graphics" demo Any suggestions? The same program runs fine under linux, BTW. Ina --------------------- Ina Dau Computer Administrator - Room 101 - Pearson Building - UCL email: i.dau at ucl.ac.uk Phone: +44-171-4193636 snail:

Am I the only one with this problem? > postscript() Error in old$command == "default" : comparison (1) is possible only for vector types The function postscript() is creates a list called "old". the function wants to access old$command, but old does not have a component called command. > postscript function (file = ifelse(onefile, "Rplots.ps",

[Env: R 2.12.2, Win XP] I'm creating figures using MASS::eqcsplot to provide equal scaling of the axes. My figures work OK when I plot to the screen, but when I try to do the same plot as a postscript file, I get an unexplicable error, > figframe() Error in if (yuin > xuin * ratio) yuin <- xuin * ratio else xuin <- yuin/ratio : missing value where TRUE/FALSE needed >

Hi everyone, I was trying to mode the following exercise using R. The question: Set up a one pool model using numericintegration. The model will run from time 1 to time 30 using a time step of 1.The pool (A) will be fed by flux "inA" at a rate of 5 units per hour anddrained by flux "outA" at a rate of 20% per hour. At time 0, A has 5units. At time 30, what is the pool size of

>>>>> Steve Martin >>>>> on Mon, 18 Dec 2023 07:56:46 -0500 writes: > Does mFUN() really need to be a function of x and the NA values of x? I > can't think of a case where it would be used on anything but the non-NA > values of x. > I think it would be easier to specify a different mFUN() (and document this > new argument)

Does mFUN() really need to be a function of x and the NA values of x? I can't think of a case where it would be used on anything but the non-NA values of x. I think it would be easier to specify a different mFUN() (and document this new argument) if the function has one argument and is applied to the non-NA values of x. zapsmall <- function(x, digits = getOption("digits"),

Greetings, I'm trying to debug a simple two-line plot routine in R called test.R: cor(swiss) plot(swiss$Catholic, swiss$Examination) These commands work fine when typed into R. They also work fine when I invoke this routine by the following line into my terminal: R --slave < /Library/WebServer/Documents/gsa/test.R My ultimate goal is to send data to this R routine via a web

Le 18/12/2023 ? 11:24, Martin Maechler a ?crit?: >>>>>> Serguei Sokol via R-devel >>>>>> on Mon, 18 Dec 2023 10:29:02 +0100 writes: > > Le 17/12/2023 ? 18:26, Barry Rowlingson a ?crit?: > >> I think what's been missed is that zapsmall works relative to the absolute > >> largest value in the vector. Hence if

I was quite suprised to discover that applying `zapsmall` to a scalar value has no apparent effect. For example: > y <- 2.220446e-16 > zapsmall(y,) [1] 2.2204e-16 I was expecting zapsmall(x)` to act like > round(y, digits=getOption('digits')) [1] 0 Looking at the current source code, indicates that `zapsmall` is expecting a vector: zapsmall <- function (x, digits =

>>>>> Serguei Sokol via R-devel >>>>> on Mon, 18 Dec 2023 10:29:02 +0100 writes: > Le 17/12/2023 ? 18:26, Barry Rowlingson a ?crit?: >> I think what's been missed is that zapsmall works relative to the absolute >> largest value in the vector. Hence if there's only one >> item in the vector, it is the largest, so its

Zapping a vector of small numbers to zero would cause problems when printing the results of summary(). For example, if zapsmall(c(2.220446e-16, ..., 2.220446e-16)) == c(0, ..., 0) then print(summary(2.220446e-16), digits = 7) would print Min. 1st Qu. Median Mean 3rd Qu. Max. 0 0 0 0 0 0 The same problem can also appear when

Isn?t that the correct outcome? The user can change the number of digits if they want to see small values? -- Change your thoughts and you change the world. --Dr. Norman Vincent Peale > On Dec 17, 2023, at 12:11?AM, Steve Martin <stevemartin041 at gmail.com> wrote: > > ?Zapping a vector of small numbers to zero would cause problems when > printing the results of summary().

Le 17/12/2023 ? 18:26, Barry Rowlingson a ?crit?: > I think what's been missed is that zapsmall works relative to the absolute > largest value in the vector. Hence if there's only one > item in the vector, it is the largest, so its not zapped. The function's > raison d'etre isn't to replace absolutely small values, > but small values relative to the largest.

I was just wondering if anyone knows what could be the problem with my exporting of plots. Below is the error messages I get when trying to export my plots (all error messages at the same time). I do get a file produced which works but I don't know why these messages appear. Doesn't matter if it is a pdf or a png or any other format I export to. Also, when exporting to png I get

I think what's been missed is that zapsmall works relative to the absolute largest value in the vector. Hence if there's only one item in the vector, it is the largest, so its not zapped. The function's raison d'etre isn't to replace absolutely small values, but small values relative to the largest. Hence a vector of similar tiny values doesn't get zapped. Maybe the line

Dear all, for an interactive web application i need to produce a lot of graphics (up to 50) on demand. In the moment i'm using the png format. The png() ...using png(file="Rplot%03d.png", ...); 'plots' ; dev.off()... produces very good graphics. The problem is it takes too long to produce the png files. The bitmap() ...using bitmap(file="Rplot%03d.png",

Can I ask a couple of usage questions? (RedHat Linux 6.1, R-1.1) 1. This may just indicate I'm a dinosaur who can't leave SAS behind. I want to write programs and run them with source() to see what they do, then I would like to use the "up arrow" to go back through the commands that were in the file, fiddle them, see what they do, and so forth. Is there no way? SAS has a

Hi, I have a tiny question about the graphics change in R 2.7.0. If I write a script ? la: options(device="pdf") formals(pdf)[c("file","onefile","width","height")] <- list("~/Rplot %03d.pdf", FALSE, 8, 8) plot(3) plot(4) both plots will be written into ONE pdf file. (not two as expected) This worked fine under 2.6.x In R 2.7.0 I

I like the fact that the postscript function enables the possbiility of a more useful title than before. However, I'd prefer the default to be the file name. It's very simple for me to make my own postscript function that does just that simply by setting title = file. I always use onefile = TRUE, so it always works (so far). However, I'm a little reluctant to do that in case some

I like the fact that the postscript function enables the possbiility of a more useful title than before. However, I'd prefer the default to be the file name. It's very simple for me to make my own postscript function that does just that simply by setting title = file. I always use onefile = TRUE, so it always works (so far). However, I'm a little reluctant to do that in case some