search for: linalg

...to consider Roslyn's design and experience. I'll be glad to discuss further in April. Michael, we can also talk later this week if you'd like. I'll send you a separate email. Loop transformations in MLIR take many different paths. Polyhedral affine-to-affine, generative/lowering in linalg, and also exploring lifting lower level constructs into affine and further into linalg and tensor compute ops. I'm all for exchanging on the rationale, use cases, and design of these paths, alongside with LLVM LNO. One practical option being to compose these lifting, affine transformations and...

...th_inexact -O2 -I/usr/local/R-0.61.1/include -c locfit.c -o locfit.o cc -ieee_with_inexact -O2 -I/usr/local/R-0.61.1/include -c S_enter.c -o S_enter.o cc -ieee_with_inexact -O2 -I/usr/local/R-0.61.1/include -c frend.c -o frend.o cc -ieee_with_inexact -O2 -I/usr/local/R-0.61.1/include -c linalg.c -o linalg.o cc -ieee_with_inexact -O2 -I/usr/local/R-0.61.1/include -c random.c -o random.o cc -ieee_with_inexact -O2 -I/usr/local/R-0.61.1/include -c weight.c -o weight.o cc -ieee_with_inexact -O2 -I/usr/local/R-0.61.1/include -c density.c -o density.o cc -ieee_with_inexact -O2 -I/usr/...

Folks: I'm trying to port some code from python over to R, and I'm running into a wall finding R code that can solve a generalized eigenvalue problem following this function model: http://docs.scipy.org/doc/scipy/reference/generated/scipy.linalg.eig.html Any ideas? I don't want to call python from within R for various reasons, I'd prefer a "native" R solution if one exists. Thanks! --j -- Jonathan A. Greenberg, PhD Assistant Professor Department of Geography and Geographic Information Science University of Illinois...

Thank you for your answer. In facts, 10 threads are asked by armadillo for some LinAlg, which backs to two threads as warned. But I cannot imagine this costs so much time just for that... A deeper analysis of time spent seems to point that a large time was mainly spent on testthat and Rcpp dependencies compilation... But other recent packages depending on these also are not spending...

On 10/01/2023 2:05 p.m., Ivan Krylov wrote: > On Tue, 10 Jan 2023 16:27:53 +0000 > RICHET Yann <yann.richet at irsn.fr> wrote: > >> In facts, 10 threads are asked by armadillo for some LinAlg, which >> backs to two threads as warned. > > I think you're right about your tests de-facto using two threads, but > it might be a good idea to _default_ to up to two threads in tests and > examples. This is especially valuable for third-party developers who > have to mas...

On Tue, 10 Jan 2023 16:27:53 +0000 RICHET Yann <yann.richet at irsn.fr> wrote: > In facts, 10 threads are asked by armadillo for some LinAlg, which > backs to two threads as warned. I think you're right about your tests de-facto using two threads, but it might be a good idea to _default_ to up to two threads in tests and examples. This is especially valuable for third-party developers who have to mass-test packages (one of whic...

Am Fr., 7. Feb. 2020 um 17:03 Uhr schrieb Chris Lattner <clattner at nondot.org >: > > The discussion here is valuable for me, helping me to make my > > presentation about it at EuroLLVM as relevant as possible. My current > > idea is to take a complex loop nest, and compare optimizing it using > > red/green DAGs and traditional pass-based optimizers. > > Cool.

Am 10.01.23 um 21:28 schrieb Duncan Murdoch: > On 10/01/2023 2:05 p.m., Ivan Krylov wrote: >> On Tue, 10 Jan 2023 16:27:53 +0000 >> RICHET Yann <yann.richet at irsn.fr> wrote: >> >>> In facts, 10 threads are asked by armadillo for some LinAlg, which >>> backs to two threads as warned. >> >> I think you're right about your tests de-facto using two threads, but >> it might be a good idea to _default_ to up to two threads in tests and >> examples. This is especially valuable for third-party developers w...

...e: > Am 10.01.23 um 21:28 schrieb Duncan Murdoch: >> On 10/01/2023 2:05 p.m., Ivan Krylov wrote: >>> On Tue, 10 Jan 2023 16:27:53 +0000 >>> RICHET Yann <yann.richet at irsn.fr> wrote: >>> >>>> In facts, 10 threads are asked by armadillo for some LinAlg, which >>>> backs to two threads as warned. >>> >>> I think you're right about your tests de-facto using two threads, but >>> it might be a good idea to _default_ to up to two threads in tests and >>> examples. This is especially valuable for thir...

...e: > Am 10.01.23 um 21:28 schrieb Duncan Murdoch: >> On 10/01/2023 2:05 p.m., Ivan Krylov wrote: >>> On Tue, 10 Jan 2023 16:27:53 +0000 >>> RICHET Yann <yann.richet at irsn.fr> wrote: >>> >>>> In facts, 10 threads are asked by armadillo for some LinAlg, which >>>> backs to two threads as warned. >>> >>> I think you're right about your tests de-facto using two threads, >>> but it might be a good idea to _default_ to up to two threads in >>> tests and examples. This is especially valuable for t...

Hello, I work on large matrices and found something interesting. For multiplication of matrices, the order has a huge influence on computing time when one of them is a sparse matrix. In the below example, M is a full matrix and A is a sparse matrix in a regular matrix class. A %*% M takes much more time than M %*% A; moreover, t(t(M) %*% t(A)) is much faster than A %*% M with same result. I

...(rather than having to hand-write .Fortran calls) but I'll leave that to someone with more expertise in linear algebra than me. Something that perhaps matches the SciPy set of functions (both in terms of input and output): >> > >> > http://docs.scipy.org/doc/scipy/reference/linalg.html >> > >> > Some of these are already implemented, but clearly not all of them. > Package CCA has package fda as dependency. > And package fda defines a function geigen. > The first 14 lines of this function are > > geigen<- function(Amat, Bmat, Cmat) > {...

...um 21:28 schrieb Duncan Murdoch: >>> On 10/01/2023 2:05 p.m., Ivan Krylov wrote: >>>> On Tue, 10 Jan 2023 16:27:53 +0000 >>>> RICHET Yann <yann.richet at irsn.fr> wrote: >>>> >>>>> In facts, 10 threads are asked by armadillo for some LinAlg, which >>>>> backs to two threads as warned. >>>> >>>> I think you're right about your tests de-facto using two threads, >>>> but it might be a good idea to _default_ to up to two threads in >>>> tests and examples. This is especial...

...S TO WORK FINE UNTIL : ... gcc -I/usr/lib/R/include -I/usr/lib/R/include/R_ext -mieee-fp -fPIC -O2 -m486 -fno-strength-reduce -g -c weight.c -o weight.o gcc -shared -o /usr/lib/R/library/locfit/libs/locfit.so S_enter.o adap.o band.o density.o family.o fitted.o frend.o kappa0.o kdtree.o lfstr.o linalg.o locfit.o math.o minmax.o nbhd.o odint.o pcomp.o preplot.o random.o scbmax.o simul.o startlf.o vari.o wdiag.o weight.o -L/usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66 -L/usr/i386-redhat-linux/lib -lg2c -lm /usr/bin/ld: cannot open -lg2c: No such file or directory <------ HERE IS WHERE IT REA...

Le 10/01/2023 ? 11:37, Serguei Sokol a ?crit?: > Le 10/01/2023 ? 10:44, RICHET Yann a ?crit?: >> Dear R-devel people, >> >> We are working to submit a package which is mainly a binding over a >> C++ lib (https://github.com/libKriging) using armadillo. >> It is _not_ a standard RcppArmadillo package, because we also had to >> provide a python binding... so