Re: [Rd] Calling a LAPACK subroutine from R

2019-09-11 Thread Berend Hasselman
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. It worked just as on macOS. Berend > On 11 Sep 2019, at 22:07, Göran Broström wrote: > > Berend, > > I do not think this works with gfortran 7+. I am calling the BLA

Re: [Rd] Fw: Calling a LAPACK subroutine from R

2019-09-11 Thread Avraham Adler
I think better stated that it is subset that relied on a “bug” that was never trapped for until now. We’re it written “properly” this never would have arisen. At least to the best of my understanding. Avi On Wed, Sep 11, 2019 at 4:34 PM Göran Broström wrote: > > > On 2019-09-11 22:16, Avraham A

Re: [Rd] Fw: Calling a LAPACK subroutine from R

2019-09-11 Thread Göran Broström
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 impossibl

Re: [Rd] Fw: Calling a LAPACK subroutine from R

2019-09-11 Thread Avraham Adler
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. Avi On Wed, Sep 11, 2019 at 4:08 PM Göran Broström wrote: > Berend, > > I do not think this works with gfortran 7+. I am calli

Re: [Rd] Fw: Calling a LAPACK subroutine from R

2019-09-11 Thread Göran Broström
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) ^

Re: [Rd] R-intro: Appendix A: attach position

2019-09-11 Thread Kurt Hornik
> Suharto Anggono Suharto Anggono via R-devel writes: Thanks: fixed now in the trunk. Best -k > In "An Introduction to R", in "Appendix A  A sample session", in the part on > Michelson data, information for > attach(mm) > is > Make the data frame visible at position 3 (the default). > In f

Re: [Rd] Fw: Calling a LAPACK subroutine from R

2019-09-11 Thread Berend Hasselman
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: # dummy code to get LAPACK library loaded X1 <- diag(2,2) x1 <- rep(2,2) # X1;x1 z <- solve(X1,x1

Re: [Rd] [ALTREP] What is the meaning of the return value of Is_sorted and No_NA function?

2019-09-11 Thread Wang Jiefei
Hi Gabriel, Thanks for your answer and future update plan. Somehow this email has been delayed for a week, so there might be a wired reply from me saying that I have found the answer from the R source code, it was sent from me last week. Hopefully, this reply will not cost another week to post:)

Re: [Rd] [ALTREP] What is the meaning of the return value of Is_sorted and No_NA function?

2019-09-11 Thread Gabriel Becker
Hi Jiefei, The meanings of the return values for sortedness can be found in RInternals.h, and are as follows: /* ALTREP sorting support */ enum {SORTED_DECR_NA_1ST = -2, SORTED_DECR = -1, UNKNOWN_SORTEDNESS = INT_MIN, /*INT_MIN is NA_INTEGER! */ SORTED_INCR = 1, SORTED_INC

[Rd] Fw: Calling a LAPACK subroutine from R

2019-09-11 Thread Giovanni Petris
Sorry for cross-posting, but I realized my question might be more appropriate for r-devel... Thank you, Giovanni From: R-help on behalf of Giovanni Petris Sent: Tuesday, September 10, 2019 16:44 To: r-h...@r-project.org Subject: [R] Calling a LAPACK su

Re: [Rd] '==' operator: inconsistency in data.frame(...) == NULL

2019-09-11 Thread Hilmar Berger
Sorry, I can't reproduce the example below even on the same machine. However, the following example produces the same error as NULL values in prior examples: > setClass("FOOCLASS", +  representation("list") + ) > ma = new("FOOCLASS", list(M=matrix(rnorm(300), 30,10))) > isS4(ma) [1] TRU

Re: [Rd] '==' operator: inconsistency in data.frame(...) == NULL

2019-09-11 Thread Hilmar Berger
Another example where a data.frame is compared to (here non-null, non-empty) non-atomic values in Ops.data.frame, resulting in an error message: setClass("FOOCLASS2", slots = c(M="matrix") ) ma = new("FOOCLASS2", M=matrix(rnorm(300), 30,10)) > isS4(ma) [1] TRUE > ma == data.frame(a=1:

Re: [Rd] '==' operator: inconsistency in data.frame(...) == NULL

2019-09-11 Thread Hilmar Berger
Dear Martin, On 11/09/2019 09:56, Martin Maechler wrote: > > > I wonder if data.frame() == NULL should also > return > > a value instead of an error. R help reads: > > > "At least one of |x| and |y| must be an atomic vector, but > > if the other is a list R attempts to c

Re: [Rd] '==' operator: inconsistency in data.frame(...) == NULL

2019-09-11 Thread Martin Maechler
> Hilmar Berger > on Wed, 4 Sep 2019 15:25:46 +0200 writes: > Dear all, > I just stumbled upon some behavior of the == operator which is at least > somewhat inconsistent. > R version 3.6.1 (2019-07-05) -- "Action of the Toes" > Copyright (C) 2019 The R Foundatio

[Rd] [ALTREP] What is the meaning of the return value of Is_sorted and No_NA function?

2019-09-11 Thread Wang Jiefei
Hi, I would like to figure out the meaning of the return value of these two functions. Here are the default definitions I find from R source code: static int altreal_Is_sorted_default(SEXP x) { return UNKNOWN_SORTEDNESS; } static int altreal_No_NA_default(SEXP x) { return 0; } I guess the m