AW: [eigen] ThreadSafety of Eigen?

["Schmidt, Michael" <Michael.Schmidt@xxxxxxxxxxxxxxxxxxx>]

Hi,

that is really good news. Thanks for the fast answer!

Michael

-----Ursprüngliche Nachricht-----
Von: Listengine [mailto:listengine@xxxxxxxxxxxxxxxxx] Im Auftrag von Benoit Jacob
Gesendet: Mittwoch, 31. März 2010 13:47
An: eigen@xxxxxxxxxxxxxxxxxxx
Betreff: Re: [eigen] ThreadSafety of Eigen?

Hi,

Eigen is state-less, hence completely thread-safe in the sense that if
you have two matrices m1 and m2, then you can have thread1 working on
m1 and thread2 working on m2 without any interference. Also, all
functions/methods are reentrant (no static variables...).

But if you let 2 threads work on the same matrix, Eigen by itself
doesn't do anything (like locking) to prevent bad stuff from
happening.

Benoit

2010/3/31 Schmidt, Michael <Michael.Schmidt@xxxxxxxxxxxxxxxxxxx>:
> Hi,
>
>
>
> I am working at a research institute in the field of medical image analysis
> and would like to use the Eigen library for some of my image processing
> algorithms for the calculation of eigenvalues- and vectors of hessian
> matrices of 3D medical images. Can you give me some hints on the
> thread-safety of the Eigen-library in general or the use of simple
> Matrix-types (e.g. Matrix3f) in conjunction with the SelfAdjointEigenSolver
> in special? I know I could try to investigate it on my own, but then again
> there are so many possible pitfalls in threadsafe development that I wanted
> to ask here first.
>
>
>
> Best regards,
>
>
>
> Michael
>
>
>
>
>
> Dipl.-Inf.  Michael Schmidt
>
> Fraunhofer MEVIS
> Institute for Medical Image Computing
> Universitaetsallee 29
> 28359 Bremen, Germany
>
> Tel.:  + 49 421 218 2959
> Fax.: + 49 421 218 4236
>
> michael.schmidt@xxxxxxxxxxxxxxxxxxx
> www.mevis.fraunhofer.de
>
>