similar to: dist() objects with NA's don't print them (PR#4866)

Vince Carey found this (thank you!). Since the fix to the problem is not entirely obvious, I post this to R-devel as RFC: help(dist) says: >> Missing values are allowed, and are excluded from all computations >> involving the rows within which they occur. If some columns are >> excluded in calculating a Euclidean, Manhattan or Canberra >> distance, the sum is

The current documentation for as.dist() contains >> Usage: >> >> as.dist(m, diag = FALSE, upper = FALSE) >> >> >> Arguments: >> >> m: A matrix of distances to be converted to a '"dist"' object >> (only the lower triangle is used, the rest is ignored). and indeed, as.dist(m) currently takes almost

>>>>> "MikG" == M GRUM <M.GRUM@CGIAR.ORG> writes: MikG> I'm resending this bug report with a new example. As MikG> seen below, cut.dendrogram gives an error message for MikG> some heights, but not for others and with some MikG> datasets adn not others. I can't see why. MikG> Last time I unwittingly sent my message with

Currently, as.data.frame() , i.e., at least its "matrix" method, still coerces logicals to factors. I think this is not desired and not according to the changes to read.table() for R 1.4.0 which allow logicals. Does anybody see a reason against a change which would allow logical matrices to become data.frames with logical variables ? Martin Maechler <maechler@stat.math.ethz.ch>

I've had a need for multinomial "random number generation" occasionally. And other people too. The following code is currently in the (very small ``not very high importance'') CRAN package normix --- which I will rename to "nor1mix" very seen because of a ``name registration'' problem I want to add "this" (well the functionality) to a

>>>>> "daheiser" == daheiser <daheiser@gvn.net> >>>>> on Tue, 6 Apr 2004 04:24:35 +0200 (CEST) writes: daheiser> It is an error in the algorithm. "it" being the behavior reported in bug report PR#1228 --- [too bad you didn't use the whole string "PR#1228" in your subject; if you had, no new report would have

As many of you have probably realized, the spam filtering at @stat.math.ethz.ch has been dead for since yesterday (09-25) ~16:50 till today ~08:30. The sudden death may have been caused by unrelated installation of some perl modules (spamassassin *is* running on perl) by our IT staff. We are very sorry for this event. On the bright side: You have been able to get a glimpse of what you are

In some contexts, I find the current behavior of rank() very `suboptimal'. We have the argument na.last = {TRUE | FALSE | NA } where the first two cases treating NAs (almost) as if they were == +Inf or == -Inf whereas the 3rd case just drops NAs. For the typical ``Rank Transformation'' that is recommended in EDA in several contexts, I would however want something else, namely keep

>>>>> "Jacob" == Jacob van Wyk <jlvw at rau.ac.za> writes: Jacob> Could anybody please help: I simply want to generate Jacob> random samples from a multinomial distribution with Jacob> fixed n and given probability vector p. Jacob> How can I do this? I've recently written the following {for the R package "normix"}. The

During the last 24 hours or so, quite a few e-mails have been delayed for the R-help (and in one case the R-announce) mailing lists. The double posting of "New version of ipred package" to R-announce is my fault, not the posters. I apologize for all inconveniences. The reason is a mail server upgrade and reconfiguration. This should all be past now and the delayed mail hopefully soon

I'm diverting this to the more appropriate mailing list, R-help, since heatmap() is standard R function. >>>>> "Johan" == Johan Lindberg <johanl at kiev.biotech.kth.se> >>>>> on Fri, 02 Jan 2004 10:04:14 +0100 writes: Johan> I am trying to plot a matrix of m-values in a heatmap Johan> with "average linkage". The rows

>>>>> "MikeM" == Michael M Meyer <mikem at salter-point.com> >>>>> on Sat, 07 Sep 2002 18:40:01 -0700 writes: MikeM> which(x==max(x)) will return the indices fo all MikeM> elements that are equal to the max. So the first max MikeM> would be which(x==max(x))[1] (At least this works in MikeM> R, I assume it does in

>>>>> "Achim" == Achim Zeileis <zeileis@ci.tuwien.ac.at> writes: Achim> Just a small documentation bug: something went wrong Achim> for the description of the graphical parameter `las' Achim> on the HTML version of the `par' help page: `las' is Achim> missing and instead a line from the description is Achim> used.

I've already fixed the bugs, but as with the last one, this is not critical enough to allow breaking current R-devel's code freeze. I hope I will have corrected it for 1.5.1.. ## Here is code reproducing the problems; ## I use try(.) whenever I know the current versions of R would ## give an error: library(splines) x <- c(1:3,5:6) y <- c(3:1,5:6) (isP <- interpSpline(x,y))#

Executive Summary: This only concerns predict() at new points when the formula contained things like poly() or ns() {in the RHS}. Because I hadn't have time to fix this yet, I submit it. [R version 1.5.1 and at least 1.4.1, probably all versions at all:] For these, R 1.5.x does not differ from 1.4.1 : Inspite of R 1.5.0's "NEWS" entry and the ?Safepredict help page,

Dear R-devel subscribers, I'm feeling quite sheepish at the moment: When I had activated the change from majordomo to mailman this morning, I accidentally didn't activate the spam(+some virus) detection part. I've only activated it half an hour ago. Indeed there were twos message of the following kind sent from R-devel -- I did never seem them personally, because we *do* filtering

At the end of his bug report, Philippe says PhGr> ..... Moreover, the subset operation [] uses as.integer() and PhGr> consequently, can suffer from the same syndrome. A WARNING section in PhGr> Extract.Rd would be welcome too. [BTW: Thank you Philippe! ] Currently, "Extract.Rd" does not say anything on the kind of indices `i' that can be used in things like

Just found because an old (written for S+) function of mine did label plots wrongly with R. Example --- inspired from example(qqnorm) --- data(precip) qqnorm(precip, ylab = "Precipitation [in/yr] ...") qqnorm(precip, ylab = "Precipitation [in/yr] ...", datax = TRUE) this is all "fine" -- `datax' is a switch that just switches the axes but keeps the

As reported on R-help by Ming-Chung Li, the cor() function has a new bug in R 1.8.0 when used with matrix arguments (to give the Cor-Matrix) and the non-default use = "pairwise.complete.obs" argument (which can be abbreviated, e.g. to use = "pair"). A quite minimal example is > x <- cbind(1:3, c(0,4,5)) > cor(x)[1,2] [1] 0.9449112 >

{BCC'ed to three Core groups} Following the recommendation of the mailman developers, I have activated occasional "VERP"ing for our mailing lists. (and will turn it off again, after about a day or so). Here is the mailman "comment-docu" on this : # These variables control the format and frequency of VERP-like delivery for # better bounce detection. VERP is Variable