similar to: Gaining access to complex LAPACK functions

Greetings - For a host of reasons I chose (was forced) to upgrade my multi-Opteron box from Fedora 7 -> Fedora 8. In the process, I also updated the ACML I had installed from 4.0.0 to 4.1.0. While I get no errors (that I can find) in the config -> make -> make install sequence, I'm pretty sure (based on some benchmarks) that I'm not getting BLAS and/or Lapack to compile in. So,

I am interested in tapping into LAPACK functionality directly from R. Using R-2.4.1 for Windows, I was able to do so ala: dyn.load("bin/Rlapack.dll") is.loaded("dstebz") # returns TRUE N <- 100 NW <- 4 n.tapers <- 5 tpW <- (2 * pi * NW)/N otNmo <- 1:N D <- as.double(cos(tpW) * ((N - 1 - 2 * (0:(N - 1)))/2)^2) E <- as.double((otNmo * (N - otNmo))/2) z

Hi, I'm trying to use Frank Harrell's Design:::ols function to do regression of y (numeric) on the interaction of two factors (x1 and x2), but Lapack throws an error: > library(Design) ... > load(url("http://www.csse.unimelb.edu.au/~gabraham/x")) > ols(y ~ x1 * x2, data=x) Error in chol2inv(fit$qr$qr) : 'size' cannot exceed nrow(x) = 20 > traceback()

Hi, I wonder where I can find an example of using a function in LAPACK library in a user's own C code. I wrote a C program which will be compiled and linked to produce a DLL file and then loaded into R. I hope to use a function from LAPACK library, for example, dgesdd, in the program. Following R manual, I call the function by F77_CALL(dgesdd) in the program. The program can be compiled

Full_Name: Ravi Varadhan Version: 2.8.1 OS: Windows Submission from: (NULL) (162.129.251.19) Inverting a matrix with solve(), but using LAPACK=TRUE, gives erroneous results: Here is an example: hilbert <- function(n) { i <- 1:n; 1 / outer(i - 1, i, "+") } h5 <- hilbert(5) hinv1 <- solve(qr(h5)) hinv2 <- solve(qr(h5, LAPACK=TRUE)) all.equal(hinv1, hinv2) #

On 5/6/19 12:57 PM, Janne Blomqvist wrote: > On Mon, May 6, 2019 at 11:55 AM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: >> On 5/4/19 6:49 PM, Steve Kargl wrote: >>> On Sat, May 04, 2019 at 06:42:47PM +0200, Thomas K?nig wrote: >>>>> - figure out Fortran2003 specification for C/Fortran interoperability >>>>> -- this _sounds_ like the

rvaradhan at jhmi.edu wrote: > Full_Name: Ravi Varadhan > Version: 2.8.1 > OS: Windows > Submission from: (NULL) (162.129.251.19) > > > Inverting a matrix with solve(), but using LAPACK=TRUE, gives erroneous > results: Thanks, but there seems to be a much easier fix. Inside coef.qr, we have coef[qr$pivot, ] <- .Call("qr_coef_real", qr, y, PACKAGE =

I need your help to make R works on my linux box, runing fedora 11. Few things on the machine and steps I did: 1. uname -a shows: Linux bagvapp 2.6.29.4-167.fc11.i586 #1 SMP Wed May 27 17:14:37 EDT 2009 i686 athlon i386 GNU/Linux 2. it has a gcc (version 4.4) RedHat's build 3. the g77 comes with the box does not work (R's configure tells it could not compile simple fortran code); so

I'm not too happy with this either, but I believe the reason is that there would be a significant extra maintenance burden consisting of things that is not being used by R itself. In particular, complex math routines are little used and have historically caused a number of issues with correct argument and return-value passing. Notice that it is a bit of a can of worms involving matching up C

On 5/4/19 6:49 PM, Steve Kargl wrote: > On Sat, May 04, 2019 at 06:42:47PM +0200, Thomas K?nig wrote: >>> - figure out Fortran2003 specification for C/Fortran interoperability >>> -- this _sounds_ like the right solution, but I don't think many >>> understand how to use it and what is implied (in particular, will >>> it require making changes to LAPACK

Hello, I just had a lot of trouble compiling a version of R which uses a recently-compiled version of ATLAS and LAPACK. ATLAS and LAPACK compiled correctly and installed fine and passed all of their checks (and yes, I did compile them all with -fPIC as is required for R). This was my initial configure line: ./configure --with-x --enable-threads=posix --with-blas="-L/usr/local/lib

Peter, Is there not already a significant maintenance burden from cherry-picking routines? From my own experience (https://bugs.r-project.org/bugzilla/show_bug.cgi?id=16482 <https://bugs.r-project.org/bugzilla/show_bug.cgi?id=16482>) this is a painful process. And while users may not call these complex routines directly, R is often used as a front-end for libraries that do, so

Hello All, I have been trying to figure out on linking R with an external lapack. Even though the R-admin recommends against doing so, our requirements force us to link it to an external lapack. I am running configure with the following parameter. *./configure --with-lapack="-L/usr/lib -llapack -lcblas" * The above seems to be having NO effect. However, later I tried

Hi, I think there is a problem with the LAPACK version of qr() in version 1.7.0. (version below). 1. The documentation states that LAPACK=TRUE is the default, but the code has LAPACK=FALSE. 2. With LAPACK=TRUE qr() is never pivoting, even in cases where it very clearly should be. e.g. set.seed(0) X<-matrix(rnorm(40),10,4);X[,1]<-X[,2] qrx<-qr(X,LAPACK=TRUE) qrx$pivot # note, no

Well, I've now tried just about every permutation I can think of - including using the ATLAS lapack (instead of generic), in various combinations with ACML, or generic BLAS, or ATLAS blas. No matter what I do, so long as I have lapack of any flavour, I get the 'stats error' with make check. And, it always seems to throw the error at the same point in the stats test file (an svd in

The following were the replies to my question about using R's LAPACK and other .h files in some of my C programs. From what was said, it appears that buying a ready-made library (MKL = $200, for example) or using CLapack according to the Shumway lecture notes are the best approaches: -------------------------------- >From Andy Liaw: (1) If you just want linear algebra routines in your C

Hi, The following errors occurs when I run the nlme's example: ------------------------------------------------------------------ Error in chol.default((value + t(value))/2) : lapack routines cannot be loaded In addition: Warning message: In chol.default((value + t(value))/2) : unable to load shared library '/usr/local/lib/R/modules//lapack.so':

Hi everyone, I am interested in using the SSYEV Lapack subroutine in a R package. Unfortunately I am not familiar with the all Lapack library and I was wondering why the routine SSYEV is not part of the R-LAPACK interface module. Is there any plan to extend the R-Lapack module in the next R release? Should I try to directly call the SSYEV routine of the external Lapack library from my R

Hi Peter, we (the gfortran team) are currently discussing this at https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90329 . I invite everybody who has an interest in this topic to take part in the discussion there. > Workarounds/solutions include: > > - disable certain optimizations -- works for now, but doesn't remove the root cause so seems generally fragile That looks like a

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