similar to: R + C + Lapack toy regression example

Professor Ripley commented on LAPACK error codes: https://stat.ethz.ch/pipermail/r-help/2007-March/127702.html and says "Internal LAPACK errors are usually problems with arithmetic accuracy, and as such are compiler- and CPU-specific." Is there a listing for the error codes from Lapack routine 'dsyevr'? Especially I am interested about the meaning and handling of error codes 1

Hello there I'm writing some c-code to solve a numerically tough problem for me in R. Looking in Lapack.h, i find the following line F77_NAME(dgesvx)(const int* fact, const char* trans, const int* n, and I believe that "fact" should've been char instead of int, i.e. F77_NAME(dgesvx)(const char* fact, const char* trans, const int* n, My reasoning: In the R-source:

Dear All, Under Debian GNU/Linux La.svd (with method = "dgesdd") sometimes gives the error "Error in La.svd(data, nu = 0, nv = min(nrow, ncol), method = "dgesdd") : LAPACK routine DGESDD gave error code -12" It seems not to depend on the data per se, but on the relationship between numbers of rows and columns. For example, if the number of columns is 100,

This is a multipart message in MIME format. --=_alternative 00812CFCCA256D66_= Content-Type: text/plain; charset="us-ascii" Two points in respect to PR#2867. First, the trivial one: (1) In Lapack.c, on lines 806 and 812, there are calls of F77_CALL(dgeqp3). But the error messages on lines on lines 809 and 815 refer to "dqeqp3", i.e., they currently have a "q"

Dear Thomas, thank you for your input. I've debugged one of the packages and I confirm that the breakage is related to passing of strings from C to Fortran. Indeed, BLAS and LAPACK define a large number of subroutines that take one or more explicit single-character strings as arguments. Other than that, BLAS has only one function (xerbla), which takes a string of unspecified length,

Hi, I have tried to pinpoint potential problems which could lead to the LAPACK issues that are currently seen in R. I built the current R trunk using AR=gcc-ar RANLIB=gcc-ranlib ./configure --prefix=$HOME --enable-lto --enable-BLAS-shlib=no --without-recommended-packages and used this to find problem areas. There are quite a few warnings that were flagged, due to mismatches in function

Dear all, I coded a function called u.glm u.glm <- function (x,ahi,age,bmiz,gender) { library(nortest) lil.rslt <- lillie.test(x) if (lil.rslt$p.value >0.05) { cat("Logtrans=0, lillie=",lil.rslt$p.value,"\n") xmodel<-glm(x~ahi+age+bmiz+as.factor(gender)) summary(xmodel) confint(xmodel) } else { cat("Logtrans=1,

Hello List, I have create a small package with C code. In the C code, I call Fortran routines of Lapack. Here is the call in the C function: F77_CALL(dgesvd)(&jobu, &jobvt,&size, &size,A, &size, D,U,&size,V,&size,&work1, &lwork,&error); In the src directory, I have a Makevars File with: PKG_LIBS = $(LAPACK_LIBS) $(BLAS_LIBS) $(FLIBS) And in the

Sorry guys, but I chose a really stupid name before (no "reference classes"). Hope it's okay to re-post. Cheers, Janko >>> ORIGINAL MESSAGE <<< Dear list, Is it possible to update or reassign '.self' with an image of '.self' (e.g. a locally stored .Rda file) from within a method? I know that this might sound akward, but here's the use

Hi! everybody: We used opus-codec for a VOIP gateway. The GW is running at a UBUNTU server. The opus stream is transcoded to G711 pcmu stream.So there are many opus codecs running simultaneously. We noticed that if there more than 5 streams in. the voice then has notisable glitchs.More streams in, worse voice got. Then we write test code for opus-codec which encode a .pcm file simultaneously.

Hi all, i am trying to compile a test, calling from C code R Lapack shared libraries. In particular, i am calling simple LAPACK driver dposv for solving linear equation system A*x=B with positive definite A. My code looks like the following in solve.c ========================== #include<stdio.h> #include <R_ext/BLAS.h> #include <R_ext/Lapack.h> int main(){

Using the 64-bit Solaris compilers make check dumps core in La_rs at 73 F77_CALL(dsyev)(jobv, uplo, &n, rx, &n, rvalues, work, &lwork, &info); I can't reproduce it easily, but example(eigen) occasionally stops with Error: abs(sm - V %*% diag(lam) %*% t(V)) < 60 * Meps is not TRUE which might be connected. The tiny rounding errors in example(eigen) aren't

I wish to pass a vector ``y'', some of whose entries are NAs to a fortran subroutine which I am dynamically loading and calling by means of .Fortran(). The subroutine runs through the vector entry by entry; obviously I want to have it do one thing if y[i] is present and a different thing if it is missing. The way I am thinking of proceeding is along the xlines of: ymiss <- is.na(y)

I have sort of an emergency question for the list. One of my professors for an S-Plus intensive class distributed a function to produce partial regression plots. I need to run it under R, because I'm doing the homework on my home computer with a modem; hence I don't have the speed required to emulate X-Windows and run S Plus off one of the campus servers. Bottom line: I'm using R.

Dear list: I am interested in the following sort of problem, as is found frequently in the field of QSAR. I have biological activity as a function of chemical structure, with structure defined in a categorical manner in that the SUBSTITUENT is the levels of the POSITION factor. For example, data from Kubinyi (http://www.kubinyi.de/dd-12.pdf) for this type of analysis is presented as follows:

I was hoping that there might be some way to attach significance code like the ones from summary.lm to a dataframe. Anyone know how to do something like that. Here is the function i'd like to add that functionality to: add1.coef <- function(model,scope,test="F",p.value=1,order.by.p=FALSE) { num <- length(model$coefficients) add <- add1(model,scope,test=test) sub <-

Dear list, I'm following the instructions provided here to compile R 64 bit on AIX 6.1. I did export OBJECT_MODE=64 export CC="gcc -maix64 -pthread" export CXX="g++ -maix64 -pthread" export FC="gfortran -maix64 -pthread" export F77="gfortran -maix64 -pthread" export CFLAGS="-O2 -g -mcpu=power6" export FFLAGS="-O2 -g -mcpu=power6"

One other note: I'm also using the latest src/main/dcf.c that was giving an issue on AIX previously; see [this](https://stat.ethz.ch/pipermail/r-devel/2015-September/071781.html) thread. Thanks. On Thu, Oct 8, 2015 at 6:51 PM, Vinh Nguyen <vinhdizzo at gmail.com> wrote: > Please note that if I don't specify those variables, then R 32 bit > compiles fine. Thanks. > > --

Dear list, I have a series of data points which I want to approximate with exactly two linear functions. I would like to choose the intervals so that the total deviation from my fitted lines is minimal. How do I best do this? Thanks! Kamila The information transmitted in this electronic communication...{{dropped}}

Here's an update: I checked the ChangeLog for R, and it seems like readDCF was changed in 3.0.2. I went on a whim and copied src/main/dcf.c from R 2.15.3 over to 3.2.2, and R compiled fine and install.packages now work for me. This is probably not ideal, but it at least makes R usable on AIX for me. Would definitely like to help figure out what's wrong with the new dcf.c on AIX.