similar to: weighted.mean uses zero when na.rm=TRUE (PR#14032)

One descriptive statistic that is conspicuously missing from core R is the statistical mode - the most frequent value in a discrete distribution. I would like to propose adding the attached 'statmode' (or a similar function) to the 'stats' package. Currently, it can be quite cumbersome to calculate the mode of a distribution in R, both for experts and beginners. The lack of a

I present you with a function that solves a problem that has bugged me for many years. I think the problem may be general enough to at least consider adding this function, or a revamped version of it, to the 'stats' package, with the other multinomial functions reside. I'm using R to export data to text files, which are input data for an external model written in C++. Parts of the

The model frame shows the response and predictors in a data frame with nicely labelled columns: fm <- lm(wt~qsec+log(hp)+sqrt(disp), data=mtcars) model.frame(fm) # ok When the left hand side consists of more than one response, those response variables still look good, inside a matrix: fm <- lm(cbind(qsec,hp,disp)~wt, data=mtcars) model.frame(fm)[[1]] # ok A problem arises when

The write.csv() function is currently implemented as function (..., col.names=NA, sep=",", qmethod="double") { write.table(..., col.names=NA, sep=",", qmethod="double") } Surely, it should be function (..., col.names=NA, sep=",", qmethod="double") { write.table(..., col.names=col.names, sep=sep,

Dear r-bugs, I'd like to be able to draw boxplots with solid or dotted whisker lines. The lty argument is currently ignored by boxplot(), and indeed hardwired in bxp(). It's not very difficult to customize these functions to generate various types of boxplots, but generally it might be an idea to allow the user to pass a few more graphical arguments to boxplot(). The approach might as

I have been reading about autocorrelation in linear models over the last couple of days, and I have to say the more I read, the more confused I get. Beyond confusion lies enlightenment, so I'm tempted to ask R-Help for guidance. Most authors are mainly worried about autocorrelation in the residuals, but some authors are also worried about autocorrelation within Y and within X vectors

Full_Name: Arni Magnusson Version: 1.6.2 OS: Windows XP Submission from: (NULL) (210.48.49.68) Hi there. I'm experiencing unexpected behaviour from as.POSIXct: > as.POSIXct("1969-12-24") [1] "1969-12-23 23:00:00 New Zealand Standard Time" > as.POSIXlt("1969-12-24") [1] "1969-12-24" > as.POSIXlt("1969-12-24")+1 [1] "1969-12-23

The audit trail indicates that PR#3663 is not reproducible and/or fixed, but I believe windows(record=T) is still not working as documented: windows(record=T) for(i in 1:5) plot(0, 0, cex=4, pch=as.character(i)) After cycling through the plots with PgUp and PgDn, the user finds out that plot 5 is lost. Indeed, .SavedPlots reports that only 4 plots were saved. I'm running the example in

Dear r-bugs, The 'see also' link in help(area,html=T) is broken, see line 91 in library/MASS/html/area.html: "../../integrate/html/integrate.html" should be "../../base/html/integrate.html" Regards, Arni OS: Windows XP R: 1.7.1 MASS: 7.1-8

I'd like to suggest changes to three help pages, regarding the use of pch=NA to suppress plotting symbols. See below. Arni R 2.0.1 on WinXP === help(bxp) === The argument outpch=" " needs to be replaced with outpch=NA in two places. I actually wrote this part of the documentation myself at one point, but have now realized that pch=NA and pch=" " are not the same:

In Windows XP, the matrix() function crashes the program when 'dimnames' is an empty list: matrix(1:4, nrow=2, dimnames=list()) # R has encountered a problem and needs to close ... This bug is specific to WinXP, as Linux64 handles this situation more gracefully: matrix(1:4, nrow=2, dimnames=list()) Error in matrix(1:4, nrow = 2, dimnames = list()) : invalid type

Unlike R 2.1.1, version 2.2.0 generates warnings when an 'oma' argument as passed to pairs(): A <- rnorm(100) B <- rnorm(100) pairs(cbind(A,B)) # no warning pairs(cbind(A,B), oma=c(6,8,10,12)) # warnings in R 2.2.0 I think pairs() should draw the plot quietly, without warnings. Can't see anything in the documentation indicating that an

Dear r-bugs, When I create EPS files, they sometimes appear rotated in my LaTeX PDF document and sometimes they don't. Two examples: ## x1.eps is not rotated in LaTeX x <- seq(-1, 1, length=100) postscript("c:/x1.eps", height=3, width=4, horizontal=FALSE, onefile=FALSE, paper="special") plot(x, dnorm(x), type="l") dev.off() ## x2.eps is not

Dear r-bugs, I'm having problems loading the 'grid' package when it has been detached earlier in the same session: > library(grid) > detach("package:grid") > library(grid) Error in .Call("L_initGrid", PACKAGE = "grid") : .Call function name not in load table Error in library(grid) : .First.lib failed This bug was mentioned on r-help

This relates to a message from Christophe Pallier to r-help some time ago. Like myself, he finds aggregate very useful, but the interface a little cumbersome. I've implemented a more compact formula interface, found at the bottom of this message: data(ToothGrowth) # I used to aggregate like this: aggregate(list(len=ToothGrowth$len),

Dear r-devel, I have implemented a function to create color palettes with improved contrast and logical order, compared with the built-in ones: source("arni.colors.R") # code is given below barplot(rep(1,100), col=arni.colors(100), space=0, border=0, axes=F) par(mfrow=c(2,1)) # rainbow() has too much green... barplot(rep(1,50), col=rev(rainbow(50,end=0.7)), space=0, border=0,

Dear Martin, Thank you for the well-reasoned response. I realized I was rather late to make this suggestion for 4.0.0, changing a somewhat low-level function that can indeed affect packages. I was just reviewing some R user scripts that were using type.convert(), mainly on data frames. In all cases, people were passing as.is=TRUE, so I was reminded that I would not be the only user who would

Dear r-devel, Among the R functions I have written and later shared with colleagues, there are five that I hope will become a part of the R base package. The tasks are neither specific nor marginal, so rather than creating one more 'misc' package, I would be happy if the R Development Core Team would adopt these functions and hammer them into shape. The functions are available from

From:r-devel-admin@stat.math.ethz.ch on 02/22/2003 12:00 PM CET Sent by: r-devel-admin@stat.math.ethz.ch Please respond to r-devel@stat.math.ethz.ch To: r-devel@stat.math.ethz.ch cc: (bcc: Asheka Rahman/arahma1/LSU) Subject: R-devel digest, Vol 1 #101 - 10 msgs Send R-devel mailing list submissions to r-devel@stat.math.ethz.ch To subscribe or unsubscribe via the World Wide Web,

>>>>> Arni Magnusson >>>>> on Mon, 13 Apr 2020 22:20:19 +0000 writes: > If read.table() is defaulting to "character" instead of "factor" data type, shouldn't type.convert() also default to "character" in R 4.0.0? > This would seem like a good time to change the default to type.convert(as.is=TRUE), to align it with