search for: patperri

There is currently a bug in the arima function. Namely, for arima models with differencing or seasonal differencing, the innovation variance estimator uses the wrong denominator whenever xreg is non-null. This is the case, for example, when fitting an ARIMA(p,1,q) model with a drift term (common in financial applications). I reported the bug (and a fix) at

I have a package on CRAN now (corpus-0.3.1) that is currently failing tests on Linux, but passing on all other architectures: https://cran.r-project.org/web/checks/check_results_corpus.html I believe that the issue arrises from a namespace class between "xrealloc", which my package provides for internal use, but which R also seems to provide (possibly as part of TRE in

I've done a bit more investigation into this issue. Here is my current understanding of the situation: 1. I have a package on CRAN (corpus-0.3.1) that passes tests on all platforms except for Linux. 2. My package defines a C function, "xrealloc", for internal use. 3. The libreadline library that R links to defines a different version of "xrealloc". 4. On Linux, when I

The bug repository is like an elephant: It doesn't forget, but the gestation period is long. In the present case, it is clear that something is not right, but someone needs to have sufficient recall and insight to check that your proposed fix is not unfixing a deliberate change. We should get to it eventually. (For some value of "we" not including "me"...) -pd On 20 Apr

On 11 May 2017 at 12:16, Patrick Perry wrote: | I've done a bit more investigation into this issue. Here is my current | understanding of the situation: | | 1. I have a package on CRAN (corpus-0.3.1) that passes tests on all | platforms except for Linux. | 2. My package defines a C function, "xrealloc", for internal use. | 3. The libreadline library that R links to defines a

A recent change to r-devel causes an R CMD check warning when a C file includes a "#pragma GCC diagnostic ignored" pragma: https://github.com/wch/r-source/commit/b76c8fd355a0f5b23d42aaf44a879cac0fc31fa4 . This causes the CRAN checks for the "corpus" package to emit a warning: https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-fedora-clang/corpus-00check.html .

I noticed that the 3.2.1 release cycle is about to start. Is there any chance that this fix will make it into the next version of R? This bug is fairly serious: getting the wrong variance estimate leads to the wrong log-likelihood and the wrong AIC, BIC etc, which can and does lead to suboptimal model selection. If it's not fixed, this issue will affect every student taking our time series

Hi Patrick, It was recently added as a cran policy (thanks Dirk's cran policy watch: https://twitter.com/markvdloo/status/935810241190617088). It seems to be a general stricter policy on keeping to the C(++) standard. Warnings are there for a reason and should usually not be ignored. I'm not familiar with the warning you are suppressing but it seems likely that your code might assume

Thank you!. My apologies again for not including the console output in my message before. I sent another e-mail with the output in the meantime, so it should be a bit clearer now, what I am seeing. In case I missed something, please let me know. Yes, I am using latin1 and cp1252 interchangebly here, mostly because Encoding() is reporting the encoding as "latin1". You presumed correctly

This is a follow-up on my initial posts regarding character encodings on Windows (https://stat.ethz.ch/pipermail/r-devel/2017-August/074728.html) and Patrick Perry's reply (https://stat.ethz.ch/pipermail/r-devel/2017-August/074830.html) in particular (thank you for the links and the bug report!). My initial posts were quite chaotic (and partly wrong), so I am trying to clear things up a

On 21 May 2015, at 12:49 , Martin Maechler <maechler at lynne.stat.math.ethz.ch> wrote: >>>>>> peter dalgaard <pdalgd at gmail.com> >>>>>> on Thu, 21 May 2015 11:03:05 +0200 writes: > >> On 21 May 2015, at 10:35 , Martin Maechler <maechler at lynne.stat.math.ethz.ch> wrote: > >>>> >>>> I noticed that