similar to: stringsAsFactors and type.convert()

Dear Martin, Thank you for the well-reasoned response. I realized I was rather late to make this suggestion for 4.0.0, changing a somewhat low-level function that can indeed affect packages. I was just reviewing some R user scripts that were using type.convert(), mainly on data frames. In all cases, people were passing as.is=TRUE, so I was reminded that I would not be the only user who would

>>>>> Arni Magnusson >>>>> on Mon, 13 Apr 2020 22:20:19 +0000 writes: > If read.table() is defaulting to "character" instead of "factor" data type, shouldn't type.convert() also default to "character" in R 4.0.0? > This would seem like a good time to change the default to type.convert(as.is=TRUE), to align it with

Hi Simon, thank you for the concise reply. Do you mean the reported behavior of drop() is not a bug? It looks like a borderline bug to me (see below), but I'm not the judge of that. If this is the intended behavior and serves an actual purpose, then that could be explicitly documented in a \note{} on the help page. Such a note would slightly reduce the surprise of users running into this

One descriptive statistic that is conspicuously missing from core R is the statistical mode - the most frequent value in a discrete distribution. I would like to propose adding the attached 'statmode' (or a similar function) to the 'stats' package. Currently, it can be quite cumbersome to calculate the mode of a distribution in R, both for experts and beginners. The lack of a

Creating a plot with reverse Y axis is easy enough with traditional graphics: > x <- 1:3 > y <- 1:3 > plot(y~x, ylim=c(3,1)) +-----------+ 1 | o | | | 2 | o | | | 3 | o | +-----------+ 1 2 3 But xyplot doesn't grasp my idea: > xyplot(y~x, ylim=c(3,1)) +-----------+ 3 | o | | | 2 | o |

Full_Name: Arni Magnusson Version: 1.6.2 OS: Windows XP Submission from: (NULL) (210.48.49.68) Hi there. I'm experiencing unexpected behaviour from as.POSIXct: > as.POSIXct("1969-12-24") [1] "1969-12-23 23:00:00 New Zealand Standard Time" > as.POSIXlt("1969-12-24") [1] "1969-12-24" > as.POSIXlt("1969-12-24")+1 [1] "1969-12-23

Hi all, I would like to propose the attached function ASCIIfy() to be added to the 'tools' package. Non-ASCII characters in character vectors can be problematic for R packages, but sometimes they cannot be avoided. To make packages portable and build without 'R CMD check' warnings, my solution has been to convert problematic characters in functions and datasets to escaped

I present you with a function that solves a problem that has bugged me for many years. I think the problem may be general enough to at least consider adding this function, or a revamped version of it, to the 'stats' package, with the other multinomial functions reside. I'm using R to export data to text files, which are input data for an external model written in C++. Parts of the

I'm relaying a question from my institute's sysadmin: Would it be possible to modify update.packages() and related functions so that 'lib.loc' accepts integer values to specify a library from the .libPaths() vector? Many Linux users want to update all user packages (inside the R_LIBS_USER directory, e.g. ~/r/library) and none of the system packages (inside the /usr directory,

The NEWS for R 4.0.0 says "R now uses a stringsAsFactors = FALSE default, and hence by default no longer converts strings to factors in calls to data.frame() and read.table()." This seems to have been implemented by setting options(stringsAsFactors = FALSE) in the main R profile. However, setting options(stringsAsFactors = NULL) reverts to the same behavior as the old

Further, in addition to the `val <- FALSE` patch a few hours ago by Martin, the line after should also be changed - if(!is.logical(val) || is.na(val) || length(val) != 1L) + if(!is.logical(val) || length(val) != 1L || is.na(val)) ## Consider Sys.setenv("_R_CHECK_LENGTH_1_LOGIC2_" = "TRUE") options(stringsAsFactors = c(TRUE, FALSE)) default.stringsAsFactors() # correct

Hello, I also want to report 2 missed cases of stringsAsFactors=TRUE in base: 1. grid.expand() still uses hard stringsAsFactors=TRUE in its arguments. 2. as.data.frame.table() also keeps factors after conversion from table. >>>>>> Duncan Murdoch >>>>>> on Sun, 12 Apr 2020 08:57:14 -0400 writes: > > > The NEWS for R 4.0.0 says "R now uses

I have been reading about autocorrelation in linear models over the last couple of days, and I have to say the more I read, the more confused I get. Beyond confusion lies enlightenment, so I'm tempted to ask R-Help for guidance. Most authors are mainly worried about autocorrelation in the residuals, but some authors are also worried about autocorrelation within Y and within X vectors

>>>>> Hugh Parsonage >>>>> on Mon, 13 Apr 2020 21:20:26 +1000 writes: > Further, in addition to the `val <- FALSE` patch a few hours ago by > Martin, the line after should also be changed > - if(!is.logical(val) || is.na(val) || length(val) != 1L) > + if(!is.logical(val) || length(val) != 1L || is.na(val)) > ## Consider

Dear r-devel, Among the R functions I have written and later shared with colleagues, there are five that I hope will become a part of the R base package. The tasks are neither specific nor marginal, so rather than creating one more 'misc' package, I would be happy if the R Development Core Team would adopt these functions and hammer them into shape. The functions are available from

Hi! I'm developing R packages and use Travis CI for continous integration. When submitting to CRAN Im suggestet to test the package using the latest R-devel. I would like that all test where run using Travis. Is there anyone who knows if this is possible to run travis test using the latest r-devel? -- Regards M?ns ============================ M?ns Magnusson 070 - 588 97 15 mons.magnusson

Dear r-devel, I have implemented a function to create color palettes with improved contrast and logical order, compared with the built-in ones: source("arni.colors.R") # code is given below barplot(rep(1,100), col=arni.colors(100), space=0, border=0, axes=F) par(mfrow=c(2,1)) # rainbow() has too much green... barplot(rep(1,50), col=rev(rainbow(50,end=0.7)), space=0, border=0,

Hi, I am building my own TCP daemon for easing some routine admin stuff... I am no expert on security,. I would really appreciate it if someone sent me some pointers to writing TCP daemons that are hacker-proof( i know there is nothing like that...but I do not want to be making mistakes in coding that are well known.. ;) The daemon runs as root....so that is why I am woried.... Thx, Arni

Jean-Marc Valin wrote: ... > I think the amount of Windows crap is getting a bit ridiculous. Does > anyone know of a solution to keep things manageable? I mean, the same > autotools files manage the build for Linux PCs, Blackfins and MacOS (and > others). Yet, we need one set of files for each MS compiler version > (good thing they don't practice "release early, release

Mikael Magnusson writes: > Package: libspeex1 > Version: 1.1.6-1 > Severity: wishlist > > Is there anything that keeps 1.1.6-1 in experimental from being uploaded to > unstable? Do you know when it will happen? > > I'm debianizing iaxclient, which needs speex version 1.1.x. Currently I'm > using 1.1.6-1 in experimental, which is working fine. >