|Re: [eigen] Allocation policy of eigen decompositions|
[ Thread Index | Date Index | More lists.tuxfamily.org/eigen Archives ]
2010/4/15 Adolfo Rodríguez Tsouroukdissian <adolfo.rodriguez@xxxxxxxxxxxxxxxx>:
> Hi Eigen devs,I was about to propose delaying beta1 and/or turning it into an alpha..
> After a couple of weeks disconnected from the dev branch, and with the date
> of the Beta1 tag fast approaching,
It is still planned, it is not yet implemented.
> I'd like to ask about the status of a
> couple of topics that have been discussed in this (and another) thread:
> - It was mentioned that decompositions would have a constructor with size
> parameters. Is this API addition still on?. I just checked the two SVD's on
> tip and it is not yet the case
Both still planned, both not yet implemented.
> - What's the status on computing decompositions in place, and the
> possibility of making this work on blocks?
Yes, on linux we are using stack allocation there. There are plans to
> - Will optimized matrix products between smallish matrices (size < 50x50)
> involve heap allocations?. A previous post said that on Linux (which is my
> case) alloca() is used so no heap (but rather stack) allocations. Am I
> understanding this correctly?
do that on MSVC too. The threshold is controlled by
EIGEN_STACK_ALLOCATION_LIMIT. See Core/util/Memory.h.
Roadmap-wise, here's how things are looking for me:
- i'm currently knee deep in very deep changes with the class
hierarchy, storage orders, and fully supporting 0 and 1 sizes.
- once i'm done i want to finish the cleanup of renaming "Matrix" to
"Object" wherever needed, etc
- once i'm done i must do the new SVD
That i'm sure to be able to do by early May. Then I start my new job
so will have less time.
Help with the above-discussed items is very welcome :)
> Thanks and cheers,
> Adolfo Rodríguez Tsouroukdissian, Ph. D.
> Robotics engineer
> PAL ROBOTICS S.L
> Tel. +34.93.414.53.47
> AVISO DE CONFIDENCIALIDAD: Este mensaje y sus documentos adjuntos, pueden
> contener información privilegiada y/o confidencial que está dirigida
> exclusivamente a su destinatario. Si usted recibe este mensaje y no es el
> destinatario indicado, o el empleado encargado de su entrega a dicha
> persona, por favor, notifíquelo inmediatamente y remita el mensaje original
> a la dirección de correo electrónico indicada. Cualquier copia, uso o
> distribución no autorizados de esta comunicación queda estrictamente
> CONFIDENTIALITY NOTICE: This e-mail and the accompanying document(s) may
> contain confidential information which is privileged and intended only for
> the individual or entity to whom they are addressed. If you are not the
> intended recipient, you are hereby notified that any disclosure, copying,
> distribution or use of this e-mail and/or accompanying document(s) is
> strictly prohibited. If you have received this e-mail in error, please
> immediately notify the sender at the above e-mail address.
|Mail converted by MHonArc 2.6.19+||http://listengine.tuxfamily.org/|