Re: [Rd] R optim(method="L-BFGS-B"): unexpected behavior when working with parent environments

On 06/05/2019 18:21, Thomas Petzoldt wrote: It seems that it's an old bug that was found in some other packages, but at that time not optim: https://bugs.r-project.org/bugzilla/show_bug.cgi?id=15958 I think that the bug description is a little bit misleading. The bug is not in fact that "<<-"

Re: [Rd] R optim(method="L-BFGS-B"): unexpected behavior when working with parent environments

It seems that it's an old bug that was found in some other packages, but at that time not optim: https://bugs.r-project.org/bugzilla/show_bug.cgi?id=15958 and that Duncan Murdoch posted a patch already last Friday :) Thomas Am 06.05.2019 um 16:40 schrieb Ben Bolker: That's consistent/not

Re: [Rd] R optim(method="L-BFGS-B"): unexpected behavior when working with parent environments

That's consistent/not surprising if the problem lies in the numerical gradient calculation step ... On 2019-05-06 10:06 a.m., Ravi Varadhan wrote: > Optim's Nelder-Mead works correctly for this example. > > >> optim(par=10, fn=fn, method="Nelder-Mead") > x=10, ret=100.02 (memory) > x=11, ret

Re: [Rd] R optim(method="L-BFGS-B"): unexpected behavior when working with parent environments

Optim's Nelder-Mead works correctly for this example. > optim(par=10, fn=fn, method="Nelder-Mead") x=10, ret=100.02 (memory) x=11, ret=121 (calculate) x=9, ret=81 (calculate) x=8, ret=64 (calculate) x=6, ret=36 (calculate) x=4, ret=16 (calculate) x=0, ret=0 (calculate) x=-4, ret=16 (calculate) x=

Re: [Rd] read.table() fails with https in R 3.6 but not in R 3.5

On Mon, 6 May 2019 11:12:25 +0200 Ralf Stubner wrote: > On 04.05.19 19:04, Stephen Berman wrote: >> In versions of R prior to 3.6.0 the following invocation succeeds, >> returning the data frame shown: >> >>> read.table("https://www.dwds.de/r/stat?corpus=kern&cnt=tokens&date=decade&format=text";,

Re: [Rd] R problems with lapack with gfortran

On Mon, May 6, 2019 at 11:55 AM Tomas Kalibera wrote: > > On 5/4/19 6:49 PM, Steve Kargl wrote: > > On Sat, May 04, 2019 at 06:42:47PM +0200, Thomas König wrote: > >>> - figure out Fortran2003 specification for C/Fortran interoperability > >>> -- this _sounds_ like the right solution, but I don't

Re: [Rd] R problems with lapack with gfortran

On 5/6/19 12:57 PM, Janne Blomqvist wrote: > On Mon, May 6, 2019 at 11:55 AM Tomas Kalibera > wrote: >> On 5/4/19 6:49 PM, Steve Kargl wrote: >>> On Sat, May 04, 2019 at 06:42:47PM +0200, Thomas König wrote: > - figure out Fortran2003 specification for C/Fortran interoperability > -- this

Re: [Rd] Error in glm(..., family=quasi(..., variance=list(...)))

> Wollschlaeger, Daniel > on Fri, 26 Apr 2019 15:13:36 + writes: > In a glm() call using a quasi() family, one may define a custom variance function in the form of a "list containing components varfun, validmu, dev.resids, initialize and name" (quoting the help page for fami

Re: [Rd] Porting R example datasets to GNU Octave

On 5 May 2019 at 10:47, Andrew Janke wrote: | I'm interested in porting the R example datasets package to GNU Octave | and Matlab. Would you have objections to my doing so? You don't even have to ask... [...] | Since R's datasets package is GPL, I think I'd be within my rights to | just do thi

Re: [Rd] read.table() fails with https in R 3.6 but not in R 3.5

On 04.05.19 19:04, Stephen Berman wrote: > In versions of R prior to 3.6.0 the following invocation succeeds, > returning the data frame shown: > >> read.table("https://www.dwds.de/r/stat?corpus=kern&cnt=tokens&date=decade&format=text";, >> header=TRUE) >Dekade Anzahl > 11900 11467254 >

Re: [Rd] R problems with lapack with gfortran

On 5/4/19 6:49 PM, Steve Kargl wrote: On Sat, May 04, 2019 at 06:42:47PM +0200, Thomas König wrote: - figure out Fortran2003 specification for C/Fortran interoperability -- this _sounds_ like the right solution, but I don't think many understand how to use it and what is implied (in particular,

[Rd] Bug in function boxplot's axis labeling

Dear developeRs, I appreciate that boxplot now labels the axes with variable names per default. However, with argument "horizontal=TRUE" (which I always use), the default axis labels are mixed up, as can e.g. be seen with require(boot) boxplot(time ~ poison, poisons, horizontal=TRUE) The cor

[Rd] Incorrect date range in austres example dataset?

Hi, R developers, It seems there might be an issue with the "austres" example dataset in the "datasets" package. The description in austres.Rd says it's "measured quarterly from March 1971 to March 1994". But there are only 89 observations in the data as defined in the source code. By my count, th

[Rd] Porting R example datasets to GNU Octave

Hi, R Developers, I'm interested in porting the R example datasets package to GNU Octave and Matlab. Would you have objections to my doing so? This would involve transforming the example data and metadata into a format that Octave understands, and porting all of the datasets' Example code pieces

Re: [Rd] R problems with lapack with gfortran

On Sat, May 04, 2019 at 06:42:47PM +0200, Thomas König wrote: > > > - figure out Fortran2003 specification for C/Fortran interoperability > > -- this _sounds_ like the right solution, but I don't think many > > understand how to use it and what is implied (in particular, will > > it require making

[Rd] read.table() fails with https in R 3.6 but not in R 3.5

In versions of R prior to 3.6.0 the following invocation succeeds, returning the data frame shown: > read.table("https://www.dwds.de/r/stat?corpus=kern&cnt=tokens&date=decade&format=text";, > header=TRUE) Dekade Anzahl 11900 11467254 21910 13023370 31920 13434601 41930 132963

Re: [Rd] R problems with lapack with gfortran

On Sat, May 04, 2019 at 06:05:48PM +0200, peter dalgaard wrote: > > - figure out Fortran2003 specification for C/Fortran interoperability > -- this _sounds_ like the right solution, but I don't think many > understand how to use it and what is implied (in particular, will it > require making chang