search for: rto_

Displaying 20 results from an estimated 23 matches for "rto_".

Did you mean: rto
2018 Jun 19
0
aic() component in GLM-family objects
In R, family has aic component since version 0.62. There is no aic component in family in R 0.61.3. Looking at blame, https://github.com/wch/r-source/blame/tags/R-0-62/src/library/base/R/family.R , aic component in family is introduced in svn revision 640 (https://github.com/wch/r-source/commit/ac666741679b50bb1dfb5ce631717b375119f6ab): using aic(.) [Jim Lindsey]; use switch() rather than many if
2019 Feb 10
1
Extract.data.frame.Rd about $.data.frame
In R devel, data.frame method of '$' has been removed, but this part of "Details" section of Extract.data.frame.Rd still implies existence of the method. The \code{data.frame} method for \code{$}, treats \code{x} as a list, except that (as of R-3.1.0) partial matching of \code{name} to the names of \code{x} will generate a warning; this may become an error in future
2019 Nov 29
0
Inappropriate class(o)[!inherits(o,"AsIs")] in get_all_vars
class(o)[!inherits(o,"AsIs")] is still in function 'get_all_vars' in R patched (in https://svn.r-project.org/R/branches/R-3-6-branch/src/library/stats/R/models.R). It was ported to R patched by r77402. On Monday, 18 November 2019, 8:12:10 PM GMT+7, Martin Maechler <maechler at stat.math.ethz.ch> wrote: >>>>> Martin Maechler >>>>>? ?
2019 Mar 02
0
stopifnot
Instead of if(!is.null(names(cl))) names(cl) <- NULL , just names(cl) <- NULL looks simpler and the memory usage and speed is not bad in my little experiment. -------------------------------------------- Subject: Re: [Rd] stopifnot To: r-devel at r-project.org Date: Saturday, 2 March, 2019, 3:28 PM [...] A revised patch (also with simpler 'cl'): --- stop.R 2019-02-27
2018 Sep 07
1
Proposal: more accurate seq(from, to, length=n)
In R, seq(0, 1, 0.1) gives the same result as (0:10)*0.1. It is not the same as c(0, 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1) , as 0.1 is not represented exactly. I am fine with it. In R, seq(0, 1, length=11) gives the same result as seq(0, 1, 0.1). However, for seq(0, 1, length=11), it is more accurate to return c(0, 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1) . It can be obtained by
2019 Oct 06
2
Strange "no-echo" in place of "slave"
SVN revision replaces "slave" with "no-echo" in R devel. In each of the following, "no-echo" is rather strange to me. - src/gnuwin32/README.Rterm 3) As a no-echo process for ESS mode in NTEmacs with flag --ess. - src/library/grDevices/src/qdCocoa.m /* the no-echo thread work until this is NO */
2018 Sep 08
0
Proposal: more accurate seq(from, to, length=n)
I just thought that returning a more accurate result was better and that (1:10)/10 was an obvious way to calculate. It turned out that it was not that easy. I found that calculation that I proposed previously was not accurate for seq(-5, 5, length=101). I then thought of from + (0:(length.out - 1))/((length.out - 1)/(to - from)) , that is dividing by (1/by) instead of multiplying by 'by'.
2019 Nov 17
2
Inappropriate class(o)[!inherits(o,"AsIs")] in get_all_vars
SVN?revision?77401?changes ????????x[isM]?<-?lapply(x[isM],?function(o)?`class<-`(o,?class(o)[class(o)?!=?"AsIs"])) to ????????x[isM]?<-?lapply(x[isM],?function(o)?`class<-`(o,?class(o)[!inherits(o,"AsIs")])) in?function?'get_all_vars'?in?src/library/stats/R/models.R?in?R?devel. The?change?is?inappropriate.
2018 May 06
0
length of `...`
Does anyone notice r-devel thread "stopifnot() does not stop at first non-TRUE argument" starting with https://stat.ethz.ch/pipermail/r-devel/2017-May/074179.html ? I have mentioned (function(...)nargs())(...) in https://stat.ethz.ch/pipermail/r-devel/2017-May/074294.html . Something like ..elt(n) is switch(n, ...) . I have mentioned it in
2023 Mar 13
0
scan(..., skip=1e11): infinite loop; cannot interrupt
With ?if?(!j--)?{ ?????R_CheckUserInterrupt(); ?????j?=?10000; ?} as?in?current?R?devel?(r83976),?j goes negative (-1) and interrupt is checked every 10001 instead of 10000. I?prefer ?if?(!--j)?{ ?????R_CheckUserInterrupt(); ?????j?=?10000; ?} . In?current?R?devel?(r83976),?if?EOF?is?reached,?the?outer?loop?keeps?going,?i?keeps?incrementing?until?nskip.
2019 Apr 03
0
stopifnot -- eval(*) inside for()
With f <- function(x) for (i in 1) x fc <- cmpfun(f) (my previous example), error message of fc(is.numeric(y)) shows the originating call as well, while error message of f(is.numeric(y)) doesn't. Compiled version behaves differently. Even with f <- function(x) for (i in 1) {x; eval(expression(i))} fc <- cmpfun(f) , error message of fc(is.numeric(y)) shows the originating call in R
2019 Feb 18
1
Extract.data.frame.Rd about $.data.frame
The statement in R devel: There is no \code{data.frame} method for \code{$}, so \code{x$name} uses the default method which treats \code{x} as a list (with no partial matching of column names). The replacement method (for \code{$}) checks \code{value} for the correct number of rows, and replicates it if necessary. The added "(with no partial matching of column names)" is wrong.
2020 Feb 16
0
round(x, dig) [was "Development version of R fails tests .."]
I?disagree?with?what?is?assessed?as?"correct"?in?vignette?of?package?'round'. With x?<-?9.18665 ,?what?is?actually?stored?in?'x'?is?a?number?that?is?slightly?larger?than?9.18665.?So,?as?said?in?the?vignette,?it?is?closer?to?9.1867?than?9.1866. sprintf("%.4f",?x) giving "9.1867" is?correct,?as?it?is?a?string?representing?the?_exact_?number?9.1867.
2019 Apr 14
0
stopifnot
In current definition of function 'stopifnot' in stop.R in R 3.6.0 beta (https://svn.r-project.org/R/branches/R-3-6-branch/src/library/base/R/stop.R) or R devel (https://svn.r-project.org/R/trunk/src/library/base/R/stop.R), if 'exprs' is specified, cl[[1]] is quote(stopifnot) . To be more robust, quote(base::stopifnot) may be used instead. Also, in current definition of function
2019 Jul 04
1
methods package: A _R_CHECK_LENGTH_1_LOGIC2_=true error
In 'conformMethod', there is another instance of omittedSig & <something about signature[omittedSig]> . It just affects error message. Original: ? ? if(any(is.na(match(signature[omittedSig], c("ANY", "missing"))))) { ? ? ? ? bad <- omittedSig & is.na(match(signature[omittedSig], c("ANY", "missing"))) After r76756: ? ? if(any(iiN
2019 Feb 24
1
stopifnot
>From https://github.com/HenrikBengtsson/Wishlist-for-R/issues/70 : ... and follow up note from 2018-03-15: Ouch... in R-devel, stopifnot() has become yet 4-5 times slower; ... which is due to a complete rewrite using tryCatch() and withCallingHandlers(). >From https://stat.ethz.ch/pipermail/r-devel/2017-May/074256.html , it seems that 'tryCatch' was used to avoid the following
2019 May 30
2
stopifnot
Here is a patch to function 'stopifnot' that adds 'evaluated' argument and makes 'exprs' argument in 'stopifnot' like 'exprs' argument in 'withAutoprint'. --- stop.R 2019-05-30 14:01:15.282197286 +0000 +++ stop_new.R 2019-05-30 14:01:51.372187466 +0000 @@ -31,7 +31,7 @@ .Internal(stop(call., .makeMessage(..., domain = domain))) }
2019 Mar 07
0
stopifnot
By not using 'withCallingHandler' or 'tryCatch', the state is like 'stopifnot' in R 3.4.x. If 'stopifnot' becomes faster than in R 3.4.x when the expressions given to 'stopifnot' are all TRUE, it is because 'match.call' is not called. Credit is to https://github.com/HenrikBengtsson/Wishlist-for-R/issues/70 for the idea. Speaking about
2020 May 01
4
paste(character(0), collapse="", recycle0=FALSE) should be ""
Without 'collapse', 'paste' pastes (concatenates) its arguments elementwise (separated by 'sep', " " by default). New in R devel and R patched, specifying recycle0 = FALSE makes mixing zero-length and nonzero-length arguments results in length zero. The result of paste(n, "th", sep = "", recycle0 = FALSE) always have the same length as
2019 Mar 02
1
stopifnot
A private reply by Martin made me realize that I was wrong about stopifnot(exprs=TRUE) . It actually works fine. I apologize. What I tried and was failed was stopifnot(exprs=T) . Error in exprs[[1]] : object of type 'symbol' is not subsettable The shortcut assert <- function(exprs) stopifnot(exprs = exprs) mentioned in "Warning" section of the documentation similarly fails