Hi Christoph,

> Is anyone currently working on this? Or willing to start working on it?
I've collected some questions mentioned in this thread. As already said I would 
set up the survey. However, some time has passed and I just didn't find the 
time. But it's definitely on my list and I guess I can at least present a first 
draft in July (since I'm a student my obligations are heavily changing from 
time to time). 

> Another question which came up here:
> http://eigen.tuxfamily.org/bz/show_bug.cgi?id=1687
> 
>  Is anyone using/setting/changing Eigen-preprocessor directives such as 
> EIGEN_FAST_MATH?
> More generally anything from:
> http://eigen.tuxfamily.org/dox-devel/TopicPreprocessorDirectives.html 
> <http://eigen.tuxfamily.org/dox-devel/TopicPreprocessorDirectives.html>Thanks 
> for the suggestions, going to add them to the list. 

> An alternative (or addition) to the survey would be to comb through 
> open-source projects and -- if they use Eigen -- try to automatically analyze 
> things like what modules are used, what language standard is used, etc 
> (depending on the thoroughness this is probably more complicated than doing a 
> survey).
Thats an interesting idea. Do you think about crawling the major code hosting 
providers? The very different structure of individual project could make this 
very hard, though.

> If someone wants to handle this survey, do you need help in any form? Or 
> access to anything?
Regarding your idea above, is there a way to see where Eigen is used as a 
submodule? Any guesses if this is the main way of including Eigen into other 
projects?

Thanks,
David


> On 25. Jun 2019, at 20:30, Christoph Hertzberg 
> <[email protected]> wrote:
> 
> Hi!
> 
> Is anyone currently working on this? Or willing to start working on it?
> 
> Another question which came up here:
> http://eigen.tuxfamily.org/bz/show_bug.cgi?id=1687
> 
>  Is anyone using/setting/changing Eigen-preprocessor directives such as 
> EIGEN_FAST_MATH?
> More generally anything from:
> http://eigen.tuxfamily.org/dox-devel/TopicPreprocessorDirectives.html
> 
> Sub-question: Used in production/Only in legacy projects/Only for 
> "toy-projects" -- but that sub-question could be asked for every question 
> (and maybe makes the survey too complicated).
> 
> If someone wants to handle this survey, do you need help in any form? Or 
> access to anything?
> 
> An alternative (or addition) to the survey would be to comb through 
> open-source projects and -- if they use Eigen -- try to automatically analyze 
> things like what modules are used, what language standard is used, etc 
> (depending on the thoroughness this is probably more complicated than doing a 
> survey).
> 
> 
> Cheers,
> Christoph
> 
> 
> 
> On 21/02/2019 17.54, David Tellenbach wrote:
>> Hello together,
>> as discussed in another mail thread, this mail thread tries to gather 
>> questions that are suitable for a little survey among Eigen users and 
>> developers to find out how and with which tools Eigen is currently used and 
>> how and with which tools Eigen will be used in the future.
>> I think focussing on simple checkbox questions or questions that can be 
>> answered in one or two sentences is a good idea.
>> Cheers,
>> David
> 
> -- 
> Dr.-Ing. Christoph Hertzberg
> 
> Besuchsadresse der Nebengeschäftsstelle:
> DFKI GmbH
> Robotics Innovation Center
> Robert-Hooke-Straße 5
> 28359 Bremen, Germany
> 
> Postadresse der Hauptgeschäftsstelle Standort Bremen:
> DFKI GmbH
> Robotics Innovation Center
> Robert-Hooke-Straße 1
> 28359 Bremen, Germany
> 
> Tel.:     +49 421 178 45-4021
> Zentrale: +49 421 178 45-0
> E-Mail:   [email protected]
> 
> Weitere Informationen: http://www.dfki.de/robotik
>  -------------------------------------------------------------
>  Deutsches Forschungszentrum für Künstliche Intelligenz GmbH
>  Trippstadter Strasse 122, D-67663 Kaiserslautern, Germany
> 
>  Geschäftsführung:
>  Prof. Dr. Jana Koehler (Vorsitzende)
>  Dr. Walter Olthoff
> 
>  Vorsitzender des Aufsichtsrats:
>  Prof. Dr. h.c. Hans A. Aukes
>  Amtsgericht Kaiserslautern, HRB 2313
>  -------------------------------------------------------------
> 
> 
> 

Reply via email to