similar to: question about F77_NAME()

Displaying 20 results from an estimated 20000 matches similar to: "question about F77_NAME()"

2015 Mar 25
4
F77_CALL/NAME problem
Dear R-devel, I am trying to use Fortran DGESV subroutine into C. Here it is the relevant part of the C file I am currently writing #include<stdio.h> #include<R.h> #include<Rmath.h> #include<math.h> void F77_NAME(DGESV)( int*, int*, double*, int*, int*, double*, int*, int*); void solve( int *p, double *A, double *Ainv) { ... F77_CALL(DGESV)(p, p, Ain, p, ipiv,
2014 Jun 04
1
Lapack / dgesvx function declaration
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:
2004 Jan 09
2
debugging strange segfault
Dear R-devel, Can anyone give me some hints on how to go about debugging a strange segfault in my randomForest package? Here's the scoop: A user reported segfault when running predict() in the randomForest package. I asked for the data and code. The combination runs fine under WinXPPro, but does give segfault on one of our Linux boxes running R (1.7.0 through R-devel_2004-01-08) on
2004 Feb 28
2
matrix inverse in C
Hi, I'm writing an R package using the C code i've written. I'm wondering if anyone knows an easy way to calculate an inverse and cholesky factor of a matrix using the Fortran/C library of R: and how to call them from C. My code is based on the Numerical Reciepe code, and I'm trying to use something that is already in R. Thanks for your help in advance, Kosuke
2019 Sep 12
1
Calling a LAPACK subroutine from R
Followup: I have checked my package nleqslv which uses dgemv only from Fortran, on Kubuntu 18.04 with the development version of R. No errors or problems. Berend > On 12 Sep 2019, at 08:57, Berend Hasselman <bhh at xs4all.nl> wrote: > > > I have tried what I proposed in a virtual Kubuntu 18.04 which uses gfortran 7.4. > I used the latest development version of R. >
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
2012 Mar 06
2
Calling FORTRAN function from R issue?
Hello, I am trying to call the BLAS Level1 function zdotc from R via a .C call like this: #include "R.h" #include "R_ext/BLAS.h" void testzdotc() { Rcomplex zx[3], zy[3], ret_val; zx[0].r = 1.0; zx[0].i = 0.0; zx[1].r = 2.0; zx[0].i = 0.0; zx[2].r = 3.0; zx[0].i = 0.0; zy[0].r = 1.0; zy[0].i = 0.0; zy[1].r = 2.0; zy[0].i = 0.0; zy[2].r = 3.0;
2019 Sep 11
4
Fw: Calling a LAPACK subroutine from R
Berend, I do not think this works with gfortran 7+. I am calling the BLAS subroutine dgemv from Fortran code in my package eha, and the check (with R-devel) gives: gmlfun.f:223:1: warning: type of ?dgemv? does not match original declaration [-Wlto-type-mismatch] & score, ione) ^ /home/gobr0002/R/src/R-devel/include/R_ext/BLAS.h:107:1: note: type mismatch in parameter 12
2019 Sep 11
1
Fw: Calling a LAPACK subroutine from R
On 2019-09-11 22:16, Avraham Adler wrote: > Can you write a small C function that calls LAPACK call that fro your > Fortran code? Yes, an extra step but maybe less traumatic than rewriting > parts of LAPACK directly. Yes, I know how to do that, but I find it somewhat bizarre that it is impossible to call a Fortran subroutine from Fortran. And rewriting 'dgemv' was simple:
2013 Aug 27
1
Error in simulation. NAN
Hi all, im triyng to implement a bayesian model with R and c++. I have a strange problem. I can't reproduce the error with a small script and then i post the original one. The problem is after the line for(MCMC_iter2=0;MCMC_iter2<thin;MCMC_iter2++) For the first 34 iterations all work fine, after, all the simulations of mu_acc_P return an "nan". If i delete the line
2002 Jun 10
1
R's RNG produced garbage when called from f77 (Irix)
Dear R-help, I've managed to crash R on Irix when I called a Fortran subroutine that calls R's random number generator, as described in Section 5.6 of the R-exts manual. (It does say in that section that this is not guaranteed to be portable...) (Well, R doesn't crash when calling the RNG. It crashed when the random number generated isn't inside the unit interval.) Can anyone
2019 Apr 29
3
R 3.6.0 for Debian buster
Am Montag, 29. April 2019, 15:03:54 CEST schrieb Kurt Hornik: > >>>>> Johannes Ranke writes: > > Am Montag, 29. April 2019, 13:44:03 CEST schrieb Kurt Hornik: > >> >>>>> Johannes Ranke writes: > >> Thanks. You may have seen that with current gfortran in > >> testing/unstable, there are problems with the R BLAS/LAPACK API entries
2004 Jul 05
1
passing char's from C to Fortran (mac os x)
Hello All, In some package I use a c-routine which calls a fortran routine which expects a char-string as input. As per the writing R-extensions manual, the Fortran routine is declared in C as: void F77_NAME (setoptions) (char **option); and then it is calles as follows: char **option; option = new char*[1]; option[0] = new char[256]; option[0] = strcpy(option[0],"Iteration
2010 Jan 03
3
F77_CALL, F77_NAME definition
I give up. Maybe it is my search (Windows) but I cannot seem to find the definition of the F77_CALL or F77_NAME macros. Either there are too many matches or the search just doesn't find it. For example where is the source for: F77_CALL(dpotri) ? Thank you. Kevin
2019 Apr 29
1
R 3.6.0 for Debian buster
On 29 April 2019 at 15:03, Kurt Hornik wrote: | >>>>> Johannes Ranke writes: | | > Am Montag, 29. April 2019, 13:44:03 CEST schrieb Kurt Hornik: | >> >>>>> Johannes Ranke writes: | >> Thanks. You may have seen that with current gfortran in | >> testing/unstable, there are problems with the R BLAS/LAPACK API entries | >> using a Fortran
2002 Jun 12
3
help debugging segfaults
(Sorry for the cross-post--- I wasn't sure which list is more appropriate...) Hi everyone, I've run into segfaults when using my randomForest package on large dataset (e.g., 100 x 15200) and large number of trees (e.g., ntree=7000 and mtry=3000). I'm wondering if anyone can give me some hints on where to look for the problem. The randomForest package mainly consists of two things:
2002 Jun 12
3
help debugging segfaults
(Sorry for the cross-post--- I wasn't sure which list is more appropriate...) Hi everyone, I've run into segfaults when using my randomForest package on large dataset (e.g., 100 x 15200) and large number of trees (e.g., ntree=7000 and mtry=3000). I'm wondering if anyone can give me some hints on where to look for the problem. The randomForest package mainly consists of two things:
2009 Jun 17
3
Matrix inversion-different answers from LAPACK and LINPACK
Hello. I am trying to invert a matrix, and I am finding that I can get different answers depending on whether I set LAPACK true or false using "qr". I had understood that LAPACK is, in general more robust and faster than LINPACK, so I am confused as to why I am getting what seems to be invalid answers. The matrix is ostensibly the Hessian for a function I am optimizing. I want to get
2002 Jun 18
1
can't find array overruns (was: help debugging segfaults)
Dear R-devel, Last week I got several responses to my question about debugging segfaults in my code (original post below). After I changed the S_alloc() calls to Calloc()/Free(), the symptom was gone, but I was told to keep looking. So I did: o Switched to Calloc/Free. Electric Fence did not find any problem. o Put assert(index < bound); assert(index >=0); everywhere in the C routine
2008 Jul 09
1
Help with installing add-on packages
Dear R users. Recently I wanted to update my R distribution to the current one (R-2.7.1). I am running a Fedora core 8 distirbution. The installation went fine, but when I tried to add some additional packages the majority made an exit with an error. Only a few least demanding (e.g. RColorBrewer) managed to get through the installation process. What happened between the versions 2.6.x and 2.7.x