Re: [Cppqed-support] Eigen

[Andras V. <and...@ui...>]

Hi Raimar,
Thanks, that sounds straightforward indeed.
 Please keep the feature branch, since there is one point left to take care
of: Eigen::Matrices can adopt previously allocated data through Eigen::Map
obejcts with the funny ’new’ syntax that you see exemplified in
GeneralDickeImaginaryEvolution. They will still try to free this chunk of
memory when they get destructed, so one has to make sure that they readopt
their original data before running out of scope … (That’s why you see two
pairs of ’new’ constructs in the script. At least, this is my present
understanding.) This worked for me in some tests, but now in
GeneralDickeImaginaryEvolution, when I do it for Eigen::Vector, it causes a
crash with segmentation fault. (For Eigen::Matrix it’s still fine.)
Best regards,
András



On Tue, Nov 19, 2013 at 2:54 PM, Raimar Sandner
<rai...@ui...>wrote:

> Dear András,
>
> wow, that was quick!
>
> #include <Eigen/Core> is definitely right. Eigen3 distributes a
> FindEigen3.cmake, therefore find_package(Eigen3) will set all the required
> variables and we only have to call
> include_directories(Eigen3_INCLUDE_DIRS) in
> order to have /usr/include/eigen3 in the include path (or whatever the
> right
> path is on the specific distribution).
>
> I will update the cmake build system accordingly. Should I then already
> merge
> it to Development or leave it in the feature branch for now?
>
> Raimar
>
> On Tuesday, November 19, 2013 02:25:04 PM Andras Vukics wrote:
> > Dear Raimar,
> > I have now completed migration to Eigen3, and it seems to work fine. I
> have
> > pushed the feature branch named Eigen to SourceForge (only core & scripts
> > affected).
> > Could you please fetch the branch and update cmake such that it looks for
> > Eigen3 instead of FLENS? If not found, DO_NOT_USE_EIGEN should be set.
> > Two points to note:
> > * EIGEN_NO_DEBUG should be set for release mode but the documentation of
> > Eigen states that it gets set if NDEBUG is set, so in principle we do not
> > need to care about this.
> > * Under ARCH (and Ubuntu also, I think), Eigen3 gets installed under a
> > directory called eigen3, so that the main include files can be pulled in
> as
> > #include <eigen3/Eigen/Core>
> > for example. However, in the documentation they only use
> > #include <Eigen/Core>
> > It would be nice to have this latter, especially because this eigen3
> > directory will not necessarily exist in all distributions. Hence, if
> Eigen3
> > is found, this eigen3 directory should be put into the include path.
> > Thanks, with best regards,
> > András
> >
> >
> > Dr. Andras Vukics
> > Institute for Theoretical Physics
> > University of Innsbruck
>
>
>
> ------------------------------------------------------------------------------
> Shape the Mobile Experience: Free Subscription
> Software experts and developers: Be at the forefront of tech innovation.
> Intel(R) Software Adrenaline delivers strategic insight and game-changing
> conversations that shape the rapidly evolving mobile landscape. Sign up
> now.
> http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
> _______________________________________________
> Cppqed-support mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppqed-support
>