similar to: Checksums of packages change on CRAN without change in version number

Dear all, I've been diving a bit deeper into this per request of Tomas Kalibra, and found the following : - the lock on the file is only after trying to read it using oligo, so that's not a R problem in itself. The problem is independent of extrenal packages. - using Windows' fc utility and cygwin's cmp utility I found out that every so often the download.file() function inserts

I don't think there's much wrong with is.na(as_date(Inf, origin='1970-01-01'))==FALSE, as there still is some "non-NA-ness" about the value (as difftime shows), but that the output when printing is confusing. The way cat is treating it is clearer: it does print Inf. So would this be a solution? format.Date <- function (x, ...) { xx <- format(as.POSIXlt(x), ...)

My apologies for not including sessionInfo(), and I'm a bit angry at myself for that. Retrying in a fresh session of R, I get different results. More specifically, I get the expected result where accuracy is the same in the first and the last line. As I didn't include my sessionInfo() in my previous mail, I can't figure out why I now have a different result. So I'm positive

Technically it is used as a predictor in the model. The information is contained in terms : > terms(x ~ . - z, data = d) x ~ (y + z) - z attr(,"variables") list(x, y, z) attr(,"factors") y x 0 y 1 z 0 attr(,"term.labels") [1] "y" attr(,"order") [1] 1 attr(,"intercept") [1] 1 attr(,"response") [1] 1

Dear all, to my astonishment data.table cannot be installed on R 3.5 Windows. When checking the package page, the Windows binary is available for download. When checking the server however, I can't seem to find data.table. Also install.packages() says the package is only available in source form and may need compilation. Compiling using Rtools 35 is no problem. Is this merely an issue of

Hi Peter, I share your experience with trying to help IT departments setting things up. The network directory of the students is mapped to a drive, but R still uses the unc path instead of the drive when attempting to create that user library. Unless I do it manually of course. The only solution I see right now is to set the HOME or R_LIBS_USER environment variable in Renviron, but that should be

I ran this code in RStudio Server on a linux machine, but I don?t know the version offhand. I will try to get it tomorrow. Thanks. Thanks, Greg Michaelson www.datarobot.com 704-981-1118 > On Mar 14, 2018, at 4:47 PM, Joris Meys <jorismeys at gmail.com> wrote: > > To my surprise, I can confirm on Windows 10 using R 3.4.3 . As tail is not recognized by Windows cmd, I replaced

Dear all, as a follow-up to the question asked on R-package-devel (see link below): Someone sent a package to CRAN with a few problems. There's more things wrong with the submission, but one thing that really caught my eye was the following error: Warning message: running command '"C:/PROGRA~1/R/R-33~1.2/bin/x64/R" CMD BATCH --vanilla "testthat.R"

I think you are confusing package and function here. Plus some of the R Core packages, that you mention, contain functions that should probably be replaced by functions with better implementation from packages on CRAN. Best regards Morgan On Fri, 11 Oct 2019 15:22 Joris Meys, <jorismeys at gmail.com> wrote: > > > On Fri, Oct 11, 2019 at 3:55 PM Morgan Morgan <morgan.emailbox

On Wed, Jan 31, 2018 at 1:41 PM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > On 31/01/2018 6:33 AM, Joris Meys wrote: > > 3. given your criticism, I'd like your opinion on where I can improve the >> documentation of https://github.com/CenterForStatistics-UGent/pim. I'm >> currently busy updating the help files for a next release on CRAN, so your

Hi, I wanted to send a small patch for survival documentation. So I forked, patched and tried to build locally using R CMD build, but this failed with errors about undefined references. Upon closer inspection, the undefined references relate to files that give a warning when compiled through install.packages("survival", type = "source") on Windows, for example:

Martin, also from me a heartfelt thank you for taking care of this. Some thoughts on Henrik's response: On Mon, May 7, 2018 at 2:28 AM, Henrik Bengtsson <henrik.bengtsson at gmail.com > wrote: > > I still argue that the current behavior cause more harm than it helps. > I agree with your analysis of the problems this legacy behaviour causes. Deprecating the default

You only have to make an S4 method if there is already an S4 generic. If there is just an S3 generic, then just define S3 methods on it. I think we should stay away from defining S4 generics when there is no good reason for them. Good reasons include multiple dispatch, or a non-default signature. Neither of those apply in this case. Michael On Thu, May 24, 2018 at 6:39 AM, Joris Meys

Hi Hadley, my point actually came from a data analyst point of view. A character variable is something used for extra information, eg the "any other ideas?" field of a questionnaire. A categorical variable is a variable describing categories defined by the researcher. If it is made clear that a factor is the object type needed for a categorical variable, there is no confusion. All my

On Thu, Aug 30, 2018 at 2:09 PM D?nes T?th <toth.denes at kogentum.hu> wrote: > Note that `||` and `&&` have never been symmetric: > > TRUE || stop() # returns TRUE > stop() || TRUE # returns an error > > Fair point. So the suggestion would be to check whether x is of length 1 and whether y is of length 1 only when needed. I.e. c(TRUE,FALSE) || TRUE would give an

The ratio of object size to rds file size depends on the object. Some variation is due to how header information is stored in memory and in the file but I suspect most is due to how compression works (e.g., a vector of repeated values can be compressed into a smaller file than a bunch of random bytes). f <- function (data, ...) { force(data) tf <- tempfile()

I believe the word "truncated" is causing the confusion. 3 is "the next smallest integer" following 2.5. But it is not the truncation done by trunc(). Rewording to "rounding the next smallest integer" would get rid of that confusion imho. Cheers Joris On Wed, Sep 19, 2018 at 7:57 PM Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > This may be a doc

FWIW, you can get the URL and extract the link with extension from there. Archived packages are always tarballs, so that makes the following possible: url <- "https://cran.r-project.org/package=httr&version=1.3.0" library(RCurl) pkgurl <- gsub(".*(https://cran.+\\.tar.gz).*", "\\1", getURL(url)) install.packages(pkgurl, type

Dear Sebastian, Initially I was a bit hesitant to think about yet another way to summarize data, but your illustrations convinced me this is actually a great addition to the toolset currently available in different R packages. Many of us have written custom functions to get the required tables for specific data sets, but this would reduce that effort to simply using the right collap() call. Like

Dear Dr. Pfaff, Thank you for this, creating a package out of single file was my oriingal question, but not only creating and also maintaining it that way so R package is an artifact of the development process rather than "manually maintained" structure. I will have look at your sources. Best, Mehmet S?zen <suzen at acm.org> On 31 January 2018 at 15:51, Pfaff, Bernhard Dr.