Displaying 20 results from an estimated 3000 matches similar to: "Using functions in LAPACK in a C program"
2003 Apr 22
4
"LAPACK routine DGESDD gave error code -12" with Debian (PR#2822)
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,
2008 Aug 07
1
LAPACK.dll and Excel with R 2.7.0
Hello,
I was building a R addin for Excel. I was able to build R.dll, export to
Rdll.lib and wrap it in a Excel addin (.xll) format. Most basic
functions work fine within Excel except functions that use LAPACK, e.g.
eigen, solve etc. But if you use solve(..., LINPACK = T). That's fine.
So apparently the problem is with loading the shared library
../modules/lapack.dll. I read one of the
2007 Mar 05
1
Error in La.svd(X) : error code 1 from Lapack routine 'dgesdd'
Dear R helpers,
I am working with R 2.4.1 GUI 1.18 (4038) for MacOSX. I have a matrix of
10 000 genes and try to run the following commands:
> model.mix<-makeModel (data=data, formula=~Dye+Array+Sample+Time,
random=~Array+Sample)
> anova.mix<-fitmaanova (data, model.mix)
> test.mix<-matest (data, model=model.mix, term="Time", n.perm=100,
test.method=c(1,0,1,1))
2010 May 04
1
error in La.svd Lapack routine 'dgesdd'
Error in La.svd(x, nu, nv) : error code 1 from Lapack routine ‘dgesdd’
what resources are there to track down errors like this
[[alternative HTML version deleted]]
2001 Nov 16
2
DGESDD from Lapack for R-1.4.0?
Hi,
I'm just wondering if it is planned to include the Lapack
routine DGESDD (and friends) in R-1.4.0? This is faster
(supposedly by a factor of ~6 for large matrices) than
DGESVD which is currently (R-1.3.1) called by La.svd.
And if it is not in the plans yet, is there a chance it
could be? I've added it to my local version of R-1.3.1 and
so far see a factor of 4 improvement over
2004 Feb 25
1
lapack routine dgesdd, error code 1
Hello R-users,
during one of my analyses that involve a SVD, I get the following error
message:
Error in La.svd(x, nu, nv, method) : error code 1 from Lapack routine
dgesdd
With a search on the R web site, I only found references to error codes
17 and 3 for this particular routine. I also found the Lapack web site,
but could not find a list of the possible error messages. If somebody
knows what
2004 Mar 04
1
prcomp: error code 1 from Lapack routine dgesdd
Dear all
I have a big matrix of standardized values (dimensions 285x5829) and R
fails to calculate
the principal components using prcomp() with the following error message:
pc <- prcomp(my.matrix)
Error in La.svd(x, nu, nv, method) : error code 1 from Lapack routine
dgesdd
Is the matrix too big? I'm using R-1.8.1 under Unix (Solaris8) and
Linux(Suse 8.2). I tried to
perform a principal
2012 May 03
0
error in La.svd Lapack routine 'dgesdd'
Dear Philipp,
this is just a tentative answer because debugging is really not possible
without a reproducible example (or, at a very bare minimum, the output
from traceback()).
Anyway, thank you for reporting this interesting numerical issue; I'll
try to replicate some similar behaviour on a similarly dimensioned
artificial dataset when I have some time (which might not be soon). As
for now,
2004 May 07
1
Error compiling ROracle on Windows 2000
Hello,
I am trying to compile ROracle _0.5-4 under R 1.9.0 without much success. I am running Windows 2000 SP4, Visual C++ 6.0 SP6, and Oracle client 9.2.0.1.0. I was able to run the pre-compiled version of ROracle_0.5-2 under R 1.7.1, but does not work on R 1.8.1 or R 1.9.0. Here is the output from nmake:
C:\Program Files\R\rw1090\library\ROracle\src>nmake
Microsoft (R) Program
2007 Apr 11
1
Calling LAPACK functions directly from R
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
2007 Oct 17
3
Observations on SVD linpack errors, and a workaround
Lately I'm getting this error quite a bit:
Error in La.svd(x, nu, nv) : error code 1 from Lapack routine 'dgesdd'
I'm running R 2.5.0 on a 64 bit Intel machine running Fedora (8 I think).
Maybe the 64 bit platform is more fragile about declaring convergence.
I'm seeing way more of these errors than I ever have before.
From R-Help I see that this issue comes up from time to
2007 Jun 14
1
LAPACK Headers
Hey Everyone,
I'm running R 2.4.0 on Debian etch 4.0, and I'm trying to call some
LAPACK functions from the C code in my package. Actually, to be
honest I'm not really having trouble using commands such as La_dgesv
from within my C code, but I do get warning when compiling the package
saying:
***.c: In function '***':
***.c:37: warning: implicit declaration of function
2019 Sep 12
2
Fw: Calling a LAPACK subroutine from R
On 11/09/2019 21:38, Berend Hasselman wrote:
> The Lapack library is loaded automatically by R itself when it needs it for doing some calculation.
> You can force it to do that with a (dummy) solve for example.
> Put this at start of your script:
>
> <code>
> # dummy code to get LAPACK library loaded
> X1 <- diag(2,2)
> x1 <- rep(2,2)
> # X1;x1
> z <-
2010 Oct 19
2
Creating a Windows import lib from R.dll (x64)?
Hello,
The procedure for creating an import library (Rdll.lib) that is documented
in gnuwin32/README.packages works fine using the i386 architecture, but
it doesn't seem to work under x64.
Specifically, the procedure is:
pexports R.dll > R.exp
lib /def:R.exp /out:Rdll.lib /machine:X86 R.dll
There are two issues under x64:
1. Older version of pexports crash when applied to an x64 R.dll.
2009 Jun 26
1
problems compiling for RHEL 5.3 x86_64
Well, CentOS 5.3, which amounts to the same thing.
I recently decided to upgrade my main research machine from Fedora Core
8 -> CentOS 5.3. Basically, I was looking to move to a distro with
longer 'term-of-life' than the release schedule for Fedora currently
allows. The machine is a multi-Opteron box, so both 32- and 64-bit apps
natively supported. Since I do a lot of 'linear
2018 Mar 26
1
R Lapack – why a subset?
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
2007 Nov 09
1
Building Rdll.lib with Visual C++
>From the R-2.6.0/doc/README.packages it says:
Using Visual C++
================
You may if you prefer use Visual C++ to make the DLLs (unless they use
Fortran source!). The notes here were tested with VC++6.
First build the import library Rdll.lib by
make R.exp
...
In the installation (R-2.6.0-win32.exe) there is no Makefile with an
R.exp target that I could find and I get
2004 Apr 14
1
prcomp - error code 18
I am attempting to perform a pca on a data frame of dimension 5000x19, but
when I execute
pcapres<-prcomp(pres,center=TRUE)
the following error message is returned:
Error in La.svd(x, nu, nv, method) : error code 18 from Lapack routine
dgesdd
Where am I going wrong? I am running R-1.8.0 on Debian.
Regards,
Laura
2010 Nov 14
3
LAPACK libraries improperly linked
I am not sure if this is an R development problem or not. I am starting
with completely clean OS and and installing the latest version of R
without trying to anything special but I am having trouble with the
LAPACK library linking when I try to build packages that require them.
I thought perhaps my problem may be if interest here.
I just dumped Vista off a laptop formatted the disk and
2003 Oct 27
3
(PR#4806)
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_000_01C39C9F.B5DABBD0
Content-Type: text/plain;
charset="iso-8859-1"
# Your mailer is set to "none" (default on Windows),
# hence we cannot send the bug report directly from R.
# Please copy the bug report (after finishing