similar to: The function 'any' (PR#2503)

Full_Name: Paul Louisell Version: 1.6.2 OS: Windows NT Submission from: (NULL) (192.249.47.9) I've found a problem with either the 'apply' or 'is.factor' functions, and it seems like it might be cause for concern. Here are the commands taken directly from the R session: > is.factor(test.frame[, 1]) [1] TRUE > is.factor(test.frame[, 2]) [1] TRUE >

Hi, I'm having a problem using the 'SHLIB' command in R. I keep getting syntax errors. The help gives the following usage for it: Rcmd SHLIB [-o dllname] files 'files' is supposed to be a list of files, but whether I set up a list or a character vector, I still get a syntax error. Does anyone know if they're are supposed to be quotes somewhere in there? If someone has an

I'm using version 2.0.0 of R on a Windows 2000 OS. Packages that I installed in 1.9.1 are not installing properly in 2.0.0. Specifically, I can install packages from local zip files with the following code (which I execute through the GUI): > install.packages(choose.files('',filters=Filters[c('zip','All'),]), .libPaths()[1], CRAN = NULL) updating HTML package

Hello everyone, I'm using R 1.5.1 on Windows. I chose the option 'Install Source Files' when installing R. The code below shows my use of the command SHLIB and the error I get. C:\R\rw1051\bin>Rcmd SHLIB C:\Stage 9 (Phase 2)\cir3int.f 'perl' is not recognized as an internal or external command, operable program or batch file. I'm assuming I'm missing some perl

Hi, I'm working with a programmer on translating code I wrote for a simulation in S into FORTRAN. Since the S source code is not available, I decided to use the random number generator (RNG) in R. The problem is that the R code is complex enough that we can't isolate the proper source files to include. Although we can link to the C code and call the RNG, we haven't been able to find

Hi, I'm using R version 1.8.0 on Windows NT. When fitting a glm with Poisson random component and a log link, I frequently need to include an offset. Typically I use xtabs or table to get the counts for the contingency table, and then I use as.data.frame.table to create a data frame that I can use in the glm function. I have not found an option that allows me to total the offset variable to

Hello, Does anyone know of an R version of loess that allows more than 4 predictors and/or allows the specification of offsets? For that matter, does anyone know of _any_ version of loess that does either of the things I mention? Thanks, Paul Louisell 650-833-6254 ploua@allstate.com Research Associate (Statistician) Modeling & Data Analytics ARPC [[alternative HTML version deleted]]

On 08/05/2018 2:58 PM, Duncan Murdoch wrote: > On 08/05/2018 1:48 PM, Steven Nydick wrote: >> Reproducible example: >> >> x <- list(list(list(), list())) >> unlist(x) >> >> *> Error in as.character.factor(x) : malformed factor* > > The error comes from the line > > structure(res, levels = lv, names = nm, class = "factor") >

I'm using R version 2.0.1 on a Windows 2000 operating system. Here is some actual code I executed: > test [,1] [,2] [1,] 1000 500 [2,] 500 250 > eigen(test, symmetric=T)$values [1] 1.250000e+03 -3.153033e-15 > eigen(test, symmetric=T)$values[2] >= 0 [1] FALSE > eigen(test, symmetric=T, only.values=T)$values [1] 1250 0 > eigen(test, symmetric=T,

On Thu, 30 Jan 2025 13:07:31 -0800 Michael Chirico <michaelchirico4 at gmail.com> wrote: > There are at least dozens of other cases on CRAN [2],[3]. Some of these involve casting an int to Rboolean. Best case, the int is compared against NA_LOGICAL beforehand, avoiding any mistake (there's at least one like that). Worst case, NA_LOGICAL is not considered before the cast, so NA will

On 08/05/2018 4:50 PM, Steven Nydick wrote: > It also does the same thing if the factor is not on the first level of > the list, which seems to be due to the fact that the islistfactor is > recursive, but if a list is a list-factor, the first level lists are > coerced into character strings. > > > x <- list(list(factor(LETTERS[1]))) > > unlist(x) > Error in

In do_matrix in src/array.c there is a type switch containing : case LGLSXP : for (i = 0; i < nr; i++) for (j = 0; j < nc; j++) LOGICAL(ans)[i + j * NR] = NA_LOGICAL; That seems page inefficient, iiuc. Think it should be : case LGLSXP : for (j = 0; j < nc; j++) for (i = 0; i < nr; i++) LOGICAL(ans)[i + j * NR] = NA_LOGICAL; or more simply : case

Reproducible example: x <- list(list(list(), list())) unlist(x) *> Error in as.character.factor(x) : malformed factor* What should happen: unlist(x) > NULL R.version platform x86_64-apple-darwin15.6.0 arch x86_64 os darwin15.6.0 system x86_64, darwin15.6.0 status major 3 minor 5.0 year 2018 month 04 day

Chain?of?calls?of?C?functions?in?coerce.c?for?as.character(<logical>)?in?R: do_asatomic ascommon coerceVector coerceToString StringFromLogical?(for?each?element) The?definition?of?'StringFromLogical'?in?coerce.c?: attribute_hidden?SEXP?StringFromLogical(int?x,?int?*warn) { ????int?w; ????formatLogical(&x,?1,?&w); ????if?(x?==?NA_LOGICAL)?return?NA_STRING;

This is a general question to people who've installed R on a UNIX sparc-sun-solaris platform: Have you had any issues related to maintaining R on this platform, e.g., installations that didn't work, instances of R crashing and possibly requiring a new installation, etc? I'm especially interested in anyone who has experience with both R and S-Plus on this OS. Is there any reason to

Hi, I believe my question is pretty simple, but I'd like to give you brief background first: I work at a company with UNIX installed on a sparc-sun-solaris platform; the OS version is SunOS 5.9. Several of us who work here have been advocating for the installation of R on this server. The IT security group at my company prefers not to install the gcc compilers on our UNIX production servers;

Hi, I'm working on a server with a sparcv9 chip using SunOS 5.9 Generic May 2002. The compilers are the Sun Studio 12 compilers. I'm trying to build a 64-bit version of R-2.6.1, and while the configure script runs, the make does not. Here are the options I set in config.site: ________________________________________________________________________ _ R_PAPERSIZE=letter CC="cc

R community, As you may know, R's iconv doesn't work well converting to and from encodings that allow embedded nulls. For example > iconv("foo", to="UTF-16") Error in iconv("foo", to = "UTF-16") : embedded nul in string: '\xff\xfef\0o\0o\0' However, I don't believe embedded nulls are at issue here, but rather that R's iconv

I'd like to propose that the whenever the length of condition passed to an if or a while statement differs from one, an error is produced rather than just a warning as today: > x <- 1:2 > if (x == 1) message("x == 1") x == 1 Warning message: In if (x == 1) message("x == 1") : the condition has length > 1 and only the first element will be used There are

A colleague sent me the following: If you specify probabilities in the 'sample' function and forget to type 'prob=...', then you get nonsense. E.g. sample(1:10,1,c(0,0,0,0,1,0,0,0,0,0)) does not filter '5', while sample(1:10,1,prob=c(0,0,0,0,1,0,0,0,0,0)) does it correctly. I wish this would return an error because the