similar to: Benchmarks for R

Dear All, I'm currently working on a project with the purpose of remotely executing R code, which requires me to have to work with the code of R itself. I've searched the Internet for good information that will help me understand how R is implemented but what I've got so far isn't detailed enough. I've looked specifically at CRAN's manuals on the official website but

Dear All, I'm currently working on a project with the purpose of remotely executing R code, which requires me to have to work with the code of R itself. I've searched the Internet for good information that will help me understand how R is implemented but what I've got so far isn't detailed enough. I've looked specifically at CRAN's manuals on the official website but they

On 23/08/2017 6:25 PM, Bert Gunter wrote: > Doesn't sort by size of subgroup. I interpret the phrase I asterisked as: You were fooled by Peter's tricky single negative. Duncan Murdoch > > Your code does the following: > > First subsets of size 1 are given. > Then all subsets of size 2. > Then all subsets of size 3. > etc. > > Your code does not do this

Hi, The following code, from the examples in ?TkWidgets , immediately crashes R 4.0.1 for Windows: --------------------- snip -------------------- library("tcltk") tt <- tktoplevel() label.widget <- tklabel(tt, text = "Hello, World!") button.widget <- tkbutton(tt, text = "Push", command = function()cat("OW!\n")) tkpack(label.widget,

There seems to be another outage of the Vienna CRAN server [1] though from what I can from afar not related to DNS outage [2]. Could anyone confirm and possibly alert the local team in Vienna? Dirk [1] https://twitter.com/d_olivaw/status/1147161883797086214 [2] The DNS resolves on a few sites but eg simple pings stall -- http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org

Hi all, I should have given a better explanation of my problem. Here it is. I extracted from my code the bit that gives the error. Place this in a file called test.c #include <math.h> #include <R.h> #include <Rmath.h> #include <float.h> #include <R_ext/Print.h> int main(){ double prob[3] = {0.0, 0.0, 0.0}; double prob_tot = 0.; prob[0] = 0.3*dnorm(2, 0,

switch(i, ...) extracts 'i'-th argument in '...'. It is like eval(as.name(paste0("..", i))) . Just mentioning other things: - For 'n', n <- nargs() can be used. - sys.call() can be used in place of match.call() . --------------------------- >>>>> peter dalgaard <pdalgd at gmail.com> >>>>> on Mon, 15 May 2017 16:28:42

Installing packages from binaries on Windows seems broken, when using mirrors that are up to date with CRAN install.packages( 'httr', type = 'binary', repos = "https://cran.rstudio.com/" ) Changing repos to the Kansas CRAN mirror installs the package as expected, but that could be because the KS mirror has not yet synced. Someone pointed out that the PACKAGES.gz

I think Herv?'s idea was just that if switch can evaluate arguments selectively, so can stopifnot(). But switch() is .Primitive, so does it from C. I think it is almost a no-brainer to implement a sequential stopifnot if dropping to C code is allowed. In R it gets trickier, but how about this: Stopifnot <- function(...) { n <- length(match.call()) - 1 for (i in 1:n) { nm

Aha... Hadn't noticed that stringsAsFactors only works via as.is in read.table. Yes, the doc should probably be fixed. The code probably not -- packages loading different data sets depending on user options is an even worse idea than hav?ng the option in the first place... (I don't mean having the possibility, I mean the default.stringsAsFactor thing). In general, read.table() gets

Hi I?m trying to fit a nonlinear model to a derivative of the logistic function y = a/(1+exp((b-x)/c)) (this is the parametrization for the SSlogis function with nls) The derivative calculated with D function is: > logis<- expression(a/(1+exp((b-x)/c))) > D(logis, "x") a * (exp((b - x)/c) * (1/c))/(1 + exp((b - x)/c))^2 So I enter this expression in the nls function:

>>>>> peter dalgaard <pdalgd at gmail.com> >>>>> on Mon, 26 Jun 2017 13:43:28 +0200 writes: > This seems to be due to changes made by Martin Maechler in > 2008. Presumably this fixed something, but it escapes my > memory. Yes: The change set (svn -c46441) also contains the following NEWS entry BUG FIXES o

The 3.2.4 release had two annoyances which we would rather not have in an "ultra-stable" release, designed to hang around for the duration of the 3.3 series. One was a relatively minor Makefile issue affecting system using R's bundled lzma library. The other, rather more serious, affected printing and formatting of POSIXlt objects, which would unpredictably get the Daylight Savings

**Maybe this bug needs to be understood further before applying the patch because patch is most likely also wrong** Because, from just looking at the expressions, I think neither the R 3.6.0 version: omittedSig <- omittedSig && (signature[omittedSig] != "missing") nor the patched version (I proposed): omittedSig <- omittedSig & (signature[omittedSig] !=

Ah, got it. For some ancient reason config.site on that machine had LDFLAGS=-L/usr/X11R6/lib in config.site, and that prevented configure from inserting -L /usr/local/lib, so linked /usr/lib/libreadline.dylib, which is the Apple-supplied one, which possibly is really libedit... -p > On 18 May 2016, at 22:01 , peter dalgaard <pdalgd at gmail.com> wrote: > > gcc

> On 24 Aug 2017, at 01:25 , Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > > On 23/08/2017 6:25 PM, Bert Gunter wrote: >> Doesn't sort by size of subgroup. I interpret the phrase I asterisked as: > > You were fooled by Peter's tricky single negative. > <giggles>... Let's do this more carefully, then: M <-

Full schedule is available on developer.r-project.org. (The date is chosen to celebrate the 5th anniversary of R 1.0.0. Some irregularity may occur on the release day, since this happens to be a Saturday and the release manager is speaking at the CelebRation2020 event...) -- Peter Dalgaard, Professor, Center for Statistics, Copenhagen Business School Solbjerg Plads 3, 2000 Frederiksberg,

OK, I see what you mean. But in those cases, we don't get the catastrophic failures from the if (k < 0) return 0.; if (k == 0) return 1.; /* else: k >= 1 */ part, because at that point k is sure to be integer, possibly after rounding. It is when n-k is approximately but not exactly zero and we should return 1, that we either return 0 (negative case) or n

Hi Peter, Sorry if I was not clear. Perhaps an example will make my point: > data(iris) > class(iris$Species) [1] "factor" > write.table(iris,'data/myiris.tab') > data(myiris) > class(myiris$Species) [1] "factor" > rm(myiris) > options(stringsAsFactors = FALSE) > data(myiris) > class(myiris$Species) [1] "factor" >

I read this paper <https://www.stat.auckland.ac.nz/~ihaka/downloads/Compstat-2008.pdf> and haven't been able to find out what happened - I have seen some sporadic mention in message groups but nothing definitive. Does anyone know? [[alternative HTML version deleted]]