similar to: Bug list summary (automatic post)

================================================= 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

================================================= 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

================================================= 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! The postscript device in 0.90 does not produce symbols (pch=) as it should. E.g.: postscript(file="test.ps",width=8,height=6.4,horizontal=FALSE) plot(1:10,1:10,pch=1:5) legend(1,9,letters[1:5],pch=1:5) dev.off() The result looks quite different compared to the X-windows version. The symbol 1 (pch=1) is much to small, while the other symbols seem to big. Is it a bug? How can I

Dear R-List, I have a dataframe X containing factor f and numeric variable x1, x2, ... I want to create a new dataframe (or possibly a matrix) that gives statistics (e.g. sum) for the variables x1, x2, ... in each group defined by factor f. What is the simplest way to do this? I tried: attach(X) Z <- data.frame(f=levels(f),x1=as.vector(lapply(split(x1,f),sum))) and stumbled on: Error

On Mon, 28 Aug 2000, Rashid Nassar wrote: > Dear Professor Ripley, > > Thank you very much for your kind explanation. If I may lamely say > something in my defence, even as I apologize for my error: I mistook the > sentence "the (quoted) name of a function" to mean "optionally quoted" > because of the parentheses surrounding "quoted", and was

Thanks for your reply Nassar. What I really want is to overlay (like add=TRUE) the plots 1 and 2. With plots "at the same screen" I meant overlaid and not one beside the other, i.e., only one plot with all the points (1 to 10) in blue (or any other color), the points 5 to 9 in red and a regression line from points 5 to 9. Best regards, Antonio Olinto ----- Original Message -----

Rashid Nassar <rnassar@acpub.duke.edu> writes: > I have one more nitpick, if I may: > > summary(aov.obj) prints significance *'s but doesn't print the legend > at the bottom explaining their meaning (it is not parallel with > summary(lm.obj) > > > Question: Is this kind of nitpicking feedback useful (if so I'd be > glad to continue to keep notes and

Dear R-Users! My aim is to produce boxplots without the outliers included in the plot. I started to write a function that looks something like: myboxplot <-function(x,fa) { bpdata <- boxplot(x~fa,plot=FALSE) bpnames <- names(bpdata) for (JJ in bpnames) { command <- paste("bpdata$",JJ,"$out <- numeric(0)",sep=""); eval(command) }

A couple of help page typos that I came across: 1. help(sample) Arguments: x: Either a (numeric, complex, character or logical) vector of more than one elements from which to choose, or a positive ^ [element] 2. help(delay) Description: `delay' creates a promise to evaluate the given expression in the

yes I have tries, and nothing. It just shows the strings with the slashn, just like i typed it. -----Original Message----- From: Rashid Nassar [mailto:rnassar at duke.edu] Sent: ÐÝì?ôç, 16 Óå?ôåìâñßïõ 2004 15:44 To: Christos Rodopoulos Subject: Re: [R] How do I insert a newline in my title in a plot? Have you not tried what you have already suggested: title("this is a title\nIn 2

Hi! Since installation of R 0.90 there are problems with the size of text and numbers also in the x11-device (I reported about similar problems with the postscript device recently). For numbers and letters a different size is used: plot(1:10,1:10,type="n") text(2,8,"F5F5F5F5F5") text(2,7,"F5F5F5F5F5",cex=2) The same problem is also found in the postscript