similar to: R-devel Digest V1 #314

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

In looking over the bugs list, it seems to me that most of them are things we can no longer do anything about, because they are on old versions or broken systems or were features or .... There are now so many they obscure the bugs needing attention. I am about the remove the following. If anyone thinks they are still relevant, could you please send a follow-up to R-bugs with details under 1.2.0

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

Debian tries to build its packages on a variety of platforms. The arm platform compiled 0.90.1 (the last Debian release before the Debian package required an Atlas library, something we no longer require) failed in 'make check'. The log snippet follows; I traced this to the example(Bessel) code. > matplot(nu, t(outer(xx,nu, besselI)), type = 'l', ylim = c(-50,200), +

I have a small handheld pc having ARM process as a CPU. I installed debian and installed R using apt-get command. Everything worked great except for drawing even simple graphs x <- 1:10 plot(x) I got error messages 1: Nonfinite axis limits [GScale(nan,nan,1, .); log=0] 2: relative range of values = 9.0072e+15 * EPS, is small (axis 1). 3: Nonfinite axis limits

I post this message on R-help mailing list but someone emailed me that I can get helped if I post this one on R-devel mailing list. I have a small handheld pc having ARM process as a CPU. I installed debian and installed R (R-1.7.0 base and core, help html, latex-help) using apt-get command. Everything worked great except for drawing even simple graphs x <- 1:10 plot(x) I got error

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

Hi. While there is an x-axis set up for: > plot.factor(factor(1:3)) this axis is not present for > plot.factor(factor(1:3), col="red") which actually should just be the same as the first plot and call barplot(table(.)), shouldn't it? Where did the ticks and labels go? Note that > barplot (table(factor(1:3)), col="red") has the x-axis. Something funky is going

R-help Digest Friday, December 3 1999 Volume 01 : Number 034 In this issue: [R] model.tables Re: [R] Installing R on Slackware Linux Re: [R] Installing R on Slackware Linux [R] nlmin Re: [R] nlmin Re: [R] nlmin Re: Summary: [R] Wanted: online Introduction to R [R] Applying a function of several variables to data Re: [R] R and XML -- a near perfect

[I have abbreviated the subject as jitterbug has been having probems with long subjects.] The issue here is that one cannot mix log/non-log axes in the calls to screen(), as the appropriate par() parameter is read-only, but the meaning of yaxp depends on it. But beyond that you can't set x/yaxp for log axes. You should be able to do this: you can in the S original. A simpler version: plot

One Question: if I make a lattice-plot (beware: under development!) with a special layout e.g. c(2,2,4): p1 <- xyplot(y~x|id,data=data,layout=c(2,2,3)) is there a way to print.trellis e.g. the second page of the trellis object "p1"? print.trellis(p1,page=2) #!wrong! I want this to automatically dev.print the pages (no, I don't want multiple postscript pages). If this