[Rcpp-devel] using SparseSuite and RcppEigen in package

Simon Barthelmé simon.barthelme at gipsa-lab.fr
Thu Jan 18 12:20:00 CET 2018


Thanks everyone, I'll try and submit a pull request when I have a minute.

Best

Simon

On 18/01/2018 12:03, Dmitriy Selivanov wrote:
> I was going to suggest the same - Martin is very responsive and open 
> for improvements.
>
> 18 янв. 2018 г. 15:00 пользователь 
> <rcpp-devel-request at lists.r-forge.r-project.org 
> <mailto:rcpp-devel-request at lists.r-forge.r-project.org>> написал:
>
>     Send Rcpp-devel mailing list submissions to
>     rcpp-devel at lists.r-forge.r-project.org
>     <mailto:rcpp-devel at lists.r-forge.r-project.org>
>
>     To subscribe or unsubscribe via the World Wide Web, visit
>     https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
>     <https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel>
>
>     or, via email, send a message with subject or body 'help' to
>     rcpp-devel-request at lists.r-forge.r-project.org
>     <mailto:rcpp-devel-request at lists.r-forge.r-project.org>
>
>     You can reach the person managing the list at
>     rcpp-devel-owner at lists.r-forge.r-project.org
>     <mailto:rcpp-devel-owner at lists.r-forge.r-project.org>
>
>     When replying, please edit your Subject line so it is more specific
>     than "Re: Contents of Rcpp-devel digest..."
>
>
>     Today's Topics:
>
>        1. Re: using SparseSuite and RcppEigen in package (Martyn Plummer)
>
>
>     ----------------------------------------------------------------------
>
>     Message: 1
>     Date: Wed, 17 Jan 2018 17:23:18 +0000
>     From: Martyn Plummer <plummerm at iarc.fr <mailto:plummerm at iarc.fr>>
>     To: "simon.barthelme at gipsa-lab.fr
>     <mailto:simon.barthelme at gipsa-lab.fr>"
>     <simon.barthelme at gipsa-lab.fr <mailto:simon.barthelme at gipsa-lab.fr>>,
>             "edd at debian.org <mailto:edd at debian.org>" <edd at debian.org
>     <mailto:edd at debian.org>>,
>             "rcpp-devel at lists.r-forge.r-project.org
>     <mailto:rcpp-devel at lists.r-forge.r-project.org>"
>             <rcpp-devel at lists.r-forge.r-project.org
>     <mailto:rcpp-devel at lists.r-forge.r-project.org>>
>     Subject: Re: [Rcpp-devel] using SparseSuite and RcppEigen in package
>     Message-ID: <1516209796.843.99.camel at iarc.fr
>     <mailto:1516209796.843.99.camel at iarc.fr>>
>     Content-Type: text/plain; charset="utf-8"
>
>     I think it is worth asking Martin Maechler if he could expose more
>     SuiteSparse functionality through the Matrix package.
>
>     Martyn
>
>     On Wed, 2018-01-17 at 15:06 +0100, Simon Barthelm? wrote:
>     > Hi Dirk,
>     >
>     > Thanks for your suggestion - I had thought of doing that but it
>     requires
>     > tracking the versions of SuiteSparse used by Matrix, which means
>     extra
>     > maintenance work. OTOH maybe updates are rare enough that it's
>     not worth
>     > worrying about. It'd be nice if Matrix could expose more of
>     SuiteSparse,
>     > though, I'm sure I'm not the only one who needs that stuff.
>     >
>     > Best
>     >
>     > Simon
>     >
>     >
>     > Le 17/01/2018 ? 13:35, Dirk Eddelbuettel a ?crit :
>     > > On 17 January 2018 at 13:10, Simon Barthelm? wrote:
>     > > > I'm trying to use some CHOLMOD functionality inside an R package
>     > > > (specifically, sparse Cholesky updates/downdates). There's an
>     > > > CHOLMOD/Eigen interface for that, but unfortunately the
>     header I need is
>     > > > not shipped as part of either the Matrix package or the Rcpp
>     package.
>     > > > The file is cholmod_modify.h, and it does appear in the src/
>     directory
>     > > > of the Matrix package, but not in the include/ directory.
>     > > >
>     > > > If I include it by hand I risk version conflicts, because
>     the rest of
>     > > > CHOLMOD is provided by the Matrix package via RcppEigen.
>     What's the
>     > > > clean way of handling that? Thanks for your input!
>     > >
>     > > I know "some" (eg rstan) have completemented the BH package
>     with local
>     > > headers when BH was missing what they needed (as BH grew, I
>     think we by now
>     > > added all they need).  So you could just do that, being
>     careful to stick with
>     > > the same version.
>     > >
>     > > Or would Yixuan's RSpectra help?
>     https://cran.r-project.org/package=RSpectra
>     <https://cran.r-project.org/package=RSpectra>
>     > >
>     > > Dirk
>     > >
>     >
>     > _______________________________________________
>     > Rcpp-devel mailing list
>     > Rcpp-devel at lists.r-forge.r-project.org
>     <mailto:Rcpp-devel at lists.r-forge.r-project.org>
>     >
>     https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
>     <https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel>
>
>     ------------------------------
>
>     _______________________________________________
>     Rcpp-devel mailing list
>     Rcpp-devel at lists.r-forge.r-project.org
>     <mailto:Rcpp-devel at lists.r-forge.r-project.org>
>     https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
>     <https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel>
>
>     End of Rcpp-devel Digest, Vol 99, Issue 6
>     *****************************************
>
>
>
>
> _______________________________________________
> Rcpp-devel mailing list
> Rcpp-devel at lists.r-forge.r-project.org
> https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.r-forge.r-project.org/pipermail/rcpp-devel/attachments/20180118/81b387dd/attachment-0001.html>


More information about the Rcpp-devel mailing list