Displaying 5 results from an estimated 5 matches for "srname".
Did you mean:
soname
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 buf[7];
strncpy(buf, srname, 6);
buf[6] = '\0';
error(_("LAPACK routine '%6s' gave error code %d"), buf, -(*info));
}
change 'LAPACK' to 'The' (or 'T...
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,
re...
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
...a few warnings that were flagged, due to mismatches
in function types.
The prototypes that R has in its header files, for example BLAS.h,
are often not compatible with gfortran function declarations. To take
one small example, in src/main/print.c, we have
void NORET F77_NAME(xerbla)(const char *srname, int *info)
so xerbla_ is defined with two arguments.
However, gfortran passes string lengths as hidden arguments.
You can see this by compiling the small example
$ cat xer.f
SUBROUTINE FOO
INTEGER INFO
CALL XERBLA ('FOO', INFO)
END
$ gfortran -c -fdump-tree-o...
2019 May 03
0
R problems with lapack with gfortran
..., due to mismatches
> in function types.
>
> The prototypes that R has in its header files, for example BLAS.h,
> are often not compatible with gfortran function declarations.? To take
> one small example, in src/main/print.c, we have
>
> void NORET F77_NAME(xerbla)(const char *srname, int *info)
>
> so xerbla_ is defined with two arguments.
>
> However, gfortran passes string lengths as hidden arguments.
> You can see this by compiling the small example
>
> $ cat xer.f
> ????? SUBROUTINE FOO
> ????? INTEGER INFO
> ????? CALL XERBLA ('FOO',...