similar to: argument order for Math2 group functions in R 2.6.x (PR#10679)

signif() is primitive in 2.6.x, and so uses positional matching (almost all primitives do). See the NEWS file for the announcement of the change. On Sat, 2 Feb 2008, ben.hansen at umich.edu wrote: > Full_Name: Ben Hansen > Version: 2.6.1 > OS: Windows > Submission from: (NULL) (66.93.3.101) > > > Hi, > > In R 2.6.0 or 2.6.1 on Windows, I get the following upon

Dear Ben, If you take a look at the definition of signif() in R 2.6.1 and, e.g., in R 2.5.1 you'll see the source of the problem: R 2.6.1: > signif function (x, digits = 6) .Primitive("signif") R 2.5.1: > signif function (x, digits = 6) .Internal(signif(x, digits)) <environment: namespace:base> >From ?Primitive: "The advantage of .Primitive over .Internal

(Drats! Jitterbug is playing tricks with the PR# again. Attempting to refile so that we can kill PR#10509) Peter Dalgaard wrote: > Kurt.Hornik at wu-wien.ac.at wrote: > =20 >> ------- Start of forwarded message ------- >> Date: Tue, 13 Nov 2007 21:44:57 +0100 >> To: Steve Mongin <sjm at ccbr.umn.edu> >> Cc: cran at r-project.org >> Subject: Re: range(

------- Start of forwarded message ------- Date: Tue, 13 Nov 2007 21:44:57 +0100 To: Steve Mongin <sjm at ccbr.umn.edu> Cc: cran at r-project.org Subject: Re: range( <dates>, na.rm = TRUE ) In-Reply-To: <200711062044.OAA14064 at minnow.ccbr.umn.edu> Reply-To: Kurt.Hornik at wu-wien.ac.at From: Kurt Hornik <Kurt.Hornik at wu-wien.ac.at> X-AntiVirus: checked by AntiVir

On Fri, May 22, 2020 at 9:55 PM David Winsemius <dwinsemius at comcast.net> wrote: > The premise in the first few lines of your preamble is at odds (in the > logical sense) with my understanding of primitive function behavior. Try: > > data.frame(x=1:2,y=letters[1:2])[j=2, i=1] > > David > I had never seen naming indexes of the [] operator. The documentation of []

Hi all, I noticed something strange when I ran aov and anova. vtot=c(7.29917, 7.29917, 7.29917) #identical values fac=as.factor(c(1,1,2)) #group 1 has first two elements, group 2 has the 3rd element When I run: > anova(lm(vtot~fac)) Analysis of Variance Table Response: vtot Df Sum Sq Mean Sq F value Pr(>F) fac 1 1.6818e-30 1.6818e-30 0.3333 0.6667 Residuals 1

signif(.) is a <primitive> function. Unfortunately, I couldn't even find WHERE in the source, signif(.) is defined. Here are the symptoms: xmin <- .Machine $ double.xmin signif(xmin,3) #--> NA umach <- unlist(.Machine)[paste("double.x", c("min","max"), sep='')] for(dig in 1:10) {cat("dig=",dig,": ");

I'm interested in the difference between these two intuitively equivalent sequences that produce different results (in R version 2.13.1 (2011-07-08) 32-bit). I think R's reference counting optimization is causing this difference in behavior. > a <- 1 > a+{a[1] <- 20} [1] 21 > a <- 1 > a[1] <- 1 > a+{a[1] <- 20} [1] 40 Is one of these the "correct"

I have some trouble interpreting the output from profiling. I have read the help pages Rprof, summaryRprof and consult the R extensions manual, but I still have problems understanding the output. Basically the output consist of self.time and total.time. I have the understanding that total.time is the time spent in a given function including any subcalls or child functions or whatever the

Full_Name: Wacek Kusnierczyk Version: 2.10.0 r48269 OS: Ubuntu 8.04 Linux 32 bit Submission from: (NULL) (129.241.199.164) In the following example (and many other cases): quote(a=1) # 1 the argument matching is apparently incorrect wrt. the documentation (The R Language Definition, v 2.8.1, sec. 4.3.2, p. 23), which specifies the following algorithm for argument matching: 1. Attempt to

Using the IRanges package from Bioconductor and somewhat recent R-2.9.1. ov = IRanges(1:3, 4:6) length(ov) # 3 seq(along = ov) # 1 2 3 as wanted seq_along(ov) # 1! I had expected that the last line would yield 1:3. My guess is that somehow seq_along don't utilize that ov is an S4 class with a length method. The last line of the *Details* section of ?seq has a typeo. Currently it is

hi, I recently attended one of the ruby meetings that we have in my city. There one of the speaker said that google,amazon .. are working on RoR but still the performance of RoR is not at par with J2EE others.... he meant that though google,amazon working o it they will not bring it as front applications only parts the reason ruby is slow in comparison to other languages.... and in real time

Hi, I'm currently in the process of writing an R-installation SOP for my company. As part of that process I'm using the recommendations from the 'R Installation and Administration' document, section 3.2, "Testing an installation". This is done on an XP machine, using the latest binary of 2.11.0. The binary is downloaded and then installed from the installer. I then

Dear All, I try to use Sweave to make a document. But when I use the Sweave() command on it and build a pdf with pdflatex (3.141592-1.40.3) my apostrophes are replaced by some gibberish (an 'a' with a hat on it, a capital A with a arc pointing upwards on it and a capital Y with two points on it). If I manually replace the apostrophes using the keyboard, I get a different looking

Hello. This question concerns the Methods package. I have created a new class and am trying to set a method for it for S4 group generic "Summary". I have run into some signature problems. An example: > setClass("track", representation(x="numeric", y="character")) [1] "track" > setGeneric("max", group="Summary")

[ Email repost 3 of 3 ] From: Dirk Eddelbuettel <edd at debian.org> To: R-devel org <r-devel at r-project.org> Subject: [Patch] Minor glitch in 'Writing R Extensions' Date: Mon, 3 Sep 2012 10:58:32 -0500 The (marked up in info mode) manual Writing R Extensions says in 6.1.3 -- Function: double fprec (double X, double DIGITS) Returns the value of X

Hi, I have noticed that there is a change in the use of ellipses or . in R versions 2.6.1 and later. In versions 2.5.1 and earlier, the . were always at the end of the argument list, but in 2.6.1 they are placed after the main arguments and before method control arguments. This results in the user having to specify the exact (complete) names of the control arguments, i.e. partial matching is

Hi, OK, if you try to explicitly make them generic, you are told that they are implicitly already generic: > setGeneric("is.finite", function(from, ...) standardGeneric("is.finite")) Error in setGeneric("is.finite", function(from, ...) standardGeneric("is.finite")) : "is.finite" is a primitive function; methods can be defined, but the

Hi everyone, I'm witnessing an odd modelling phenomenon that I can't explain. If anyone has seen this before, or can explain what's going on would let me know, I'd be very grateful! Especially if I'm just being dim. I'm fitting a pair of continuous variates and their interaction to some residuals from another model. The sequential anova statement changes with the term

I need a function like signif(), but returns the rounded values as character strings, formatted with trailing zeros where appropriate. If anyone has one, I would sure appreciate a copy. Thanks -Don Details: signif() rounds a number to a specified number of significant digits, for example: > x <- c(2.503,2.477,0.1204) > signif(x[1],3) [1] 2.5 > signif(x[2],3) [1] 2.48