search for: maxcole

There is no function called 'maxCol' in 2.7.0, so should 'maxCol' be purged from maxCol.Rd and 'max.col' be promoted from an alias (and the file renamed)? from today's R-devel: /usr/local/src/R-devel> head ./src/library/base/man/maxCol.Rd % File src/library/base/man/maxCol.Rd % Part of the R package, http://www.R-project.org % Copyright 1995-2007 R Core

Hi everyone, I'm experiencing difficulty getting the results I want when I use a nested for loop. I have a data set to which I perform some calculations, and then try to apply a regression over a rolling window. The code runs, but the regression results I am getting (intercept and slope) are simply the same, repeated again and again in the results matrix. The regression does not seem to be

This is not specifically a bug, but an (implicitly/obscurely) documented behavior of read.csv (or read.table with fill=TRUE) that can be quite dangerous/confusing for users. I would love to hear some discussion from other users and/or R-core about this ... As always, I apologize if I have missed some obvious workaround or reason that this is actually the desired behavior ... In a nutshell,

Hi everyone, I'm trying to calculate correlation coefficients between corresponding columns in two matrices with identical dimensions but different data. The problem is that the matrices contain NAs in different locations. I am using the following code to try to calculate correlations between complete sets of data: #Code start maxcol<-ncol(mat1) for (i in 1:maxcol) {

I've noticed that the max.col function with the default "random" option often gives unexpected results. For instance, in this test, it seems clear what the answer should be: > # second col should always be max > x1 = cbind(1:10, 2:11, -Inf) > > # this works fine > max.col(x1, "first") [1] 2 2 2 2 2 2 2 2 2 2 > > # this gives random answers >

We have a memory leak when a function with a closure exits early prior to registering that closure through some path that will guarantee cleanup. The easiest way to fix it is to guarantee that once a closure is passed into a public API, it will be cleaned regardless of whether that API succeeds or fails. But to avoid cleaning the closure more than once, we need to refactor our internal handling,

On Mon, Sep 07, 2020 at 04:46:39PM -0500, Eric Blake wrote: > We have a memory leak when a function with a closure exits early prior > to registering that closure through some path that will guarantee > cleanup. The easiest way to fix it is to guarantee that once a > closure is passed into a public API, it will be cleaned regardless of > whether that API succeeds or fails. But to

I've noticed that the max.col function with the default "random" option often gives unexpected results. For instance, in this test, it seems clear what the answer should be: > # second col should always be max > x1 = cbind(1:10, 2:11, -Inf) > > # this works fine > max.col(x1, "first") [1] 2 2 2 2 2 2 2 2 2 2 > > # this gives random answers >

Dear Adrian and Ian (and r-helpers), I encountered a curious result in developing an example using the bicreg function in the BMA package: I noticed that pairs of models with equal R^2 and equal numbers of predictors had nevertheless different BIC values. Looking at the bicreg function, the definition of BIC appears to be the usual one, or close to it [bic <- n * log(1 - r2/100) + (size - 1) *

Hi all, I am trying to convert a data set of physician death codings (each individual's cause of death is coded by multiple physicians) from long to wide format, but the "reshape" function doesn't seem to work because it requires a "time" variable to identify the sequence among the repeated observations within individuals. My data set has no order, and different

As promised in my earlier thread on libnbd completion callback question. Eric Blake (2): generator: Refactor handling of closures in unlocked functions generator: Free closures on failure docs/libnbd.pod | 2 +- generator/C.ml | 48 +++++++++++------ generator/C.mli | 1 + lib/debug.c | 7 +-- lib/opt.c | 31 ++++++-----

The menu directory won't compile with gcc 3.4.0 because gcc complains that "ebp" cannot be used as a constraint. If preserving ebp is necessary then it will have to be done in the assembler code. Gcc 3.3.3 just seems to ignore the constraint. It didn't do anything special to preserve the register. I also noticed that getnumrows returns the contents of 0x484 which is the

Dear Sirs, I am trying to compile R v1.2.1 under Digital Unix 4.0D. The configure-script runs without any problems but during 'make' I receive the following error-message: [......] g77 -mieee -g -O2 -c dtrco.f -o dtrco.o g77 -mieee -g -O2 -c dtrsl.f -o dtrsl.o g77 -mieee -g -O2 -c eigen.f -o eigen.o g77 -mieee -g -O2 -c lminfl.f -o lminfl.o ar cr libappl.a Rsock.o approx.o bakslv.o

Hello everybody, I have a little problem in good old R. It is basically the following. I have this small database with 3 rows and the following columns: d1, d2, d3 and Highest d value - which selects the highest value from d1, d2, d3 in each row. d1 d2 d3 Highest d value 1 51.398426 39.111721 11.6086220 51.398426 2 4.057801

These bindings get as far as running very simple connections. However there are many missing parts still: * No callbacks. * No functions which handle buffers (pread/pwrite!) This is posted just for general early interest, not even for review. Rich.

Hello, This morning I downloaded, unzipped, and compiled the latest version of R for unix, in my HOME/APPLICATIONS directory. My current unix machine is a sparc-sun-solaris2.9, running SunOS 5.9. Here are the last few lines of the output following ./configure: R is now configured for sparc-sun-solaris2.9 Source directory: . Installation directory: /usr/local C compiler:

I can use gdata to successfully read in the example Excel file, but not any other excel files. Why might this be the case? It seems that the problem has something to do with opening the database but no indication as to what the problem is. So i'm at a loss of how to fix it. > library(gdata) gdata: read.xls support for 'XLS' (Excel 97-2004) files ENABLED. gdata: read.xls support

I have included the full configure/make output: (the particular error regarding bessel_i.c is at the END of the report). -walter tautz cd build/R-1.4.0 \ && unset noclobber \ && CPPFLAGS=" " \ LDFLAGS="" \ ./configure --prefix=/software/r-1 \ --datadir=/software/r-1/data \ --libdir=/software/r-1/lib \

I'm having trouble making todays development snapshot: -DHAVE_CONFIG_H -g -O2 -c stirlerr.c -o stirlerr.o stirlerr.c:34: conflicting types for `Rf_stirlerr' ../../src/include/R_ext/Mathlib.h:557: previous declaration of `Rf_stirlerr' make[3]: *** [stirlerr.o] Error 1 [20] /home/mfa5/gilp/R-versions/R-devel : uname -a SunOS mfa99579 5.6 Generic_105181-11 sun4u sparc SUNW,Ultra-5_10

On 04-Jan-16 23:24, Michael Felt wrote: > The bulk is on my forums - the final post for today is: > > Results to date: > > A. It looks like I am going to need a newer compiler for C - xlc/xlC > V11 apparently does not understand this code: > > "/data/prj/cran/R-3.2.3/src/main/memory.c", line 2149.31: 1506-046 (S) > Syntax error. > > I will have to check