Displaying 5 results from an estimated 5 matches for "srnames".
Did you mean:
sonames
2005 Aug 28
2
xerbla called from BLAS routine (PR#8100)
Full_Name: G?ran Brostr?m
Version: R-2.1.1, 2.2.0
OS: Debian unstable
Submission from: (NULL) (213.65.9.59)
Some BLAS routines call xerbla for error messages, which results in a message
like
"LAPACK routine DGER gave error code -9".
Suggested solution: In
void F77_NAME(xerbla)(char *srname, int *info)
{
/* srname is not null-terminated. It should be 6 characters. */
char
2010 Mar 31
2
Simplifying particular piece of code
..."))
mrets <- merge(mrets, ETM.SR=apply(mrets, 1, MyFunc, ret="ETM.AV120",
stdev="ETM.SD120"))
Is there a way to simplify this, some sort of loop?
mrets is a zoo object.
.AV120 and .SD120 are columns in this object.
I need the exact .SR column names.
This does not work:
SRnames <- paste(colnames.mrets, ".SR", sep="")
AVnames <- paste(colnames.mrets, ".AV120", sep="")
SDnames <- paste(colnames.mrets, ".SD120", sep="")
for(i in seq(SRnames)){
mrets <- merge(mrets, SRnames[i]=apply(mrets, 1, MyFunc,
ret...
2001 Oct 01
1
Graceful exit from fortran.
Is there a way to exit gracefully from dynamically loaded Fortran,
(several layers down), if an error condition is detected?
I.e. suppose I'm within a subroutine called by a subroutine, ...,
called by .Fortran(); I want to give up gracefully if an error
condition is detected.
If I say something like
if(x .gt. 42.d0) stop
then indeed everything stops, i.e. R falls over. I'd
2019 Apr 24
2
R problems with lapack with gfortran
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
2019 May 03
0
R problems with lapack with gfortran
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,