Re: [eigen] Proposal: documentation for Eigen3 |

[ Thread Index | Date Index | More lists.tuxfamily.org/eigen Archives ]

*To*: eigen@xxxxxxxxxxxxxxxxxxx*Subject*: Re: [eigen] Proposal: documentation for Eigen3*From*: David Roundy <roundyd@xxxxxxxxxxxxxxxxxxxxxxx>*Date*: Sat, 5 Jun 2010 07:39:17 -0700*Dkim-signature*: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=utrNX3lj0EP4wuvOAjPBnfZcBkvL/Iu1ES8GRy00yUQ=; b=ZIHE5XZuvkEGBcmr2Lw+jOAddJo/d1ismRuWSbmfljLMv95xXjhrq6+4eSLPEw2HZv lJgimXw77j/Z+Vuh7GMir+WwzOWioxiO7rPyNRrujEu8rlxrY7B2G7gn3A4oq8mhvkOb lsXW1d14F27+RLqCpCZST/schNF1deV0qe/yU=*Domainkey-signature*: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=clL/+05xlRKmk7INSne9cYki87ofBejo1/17anM0fE6CWtJ7YgVqDLfSQ0L57K3M0u I9A5hTSvpGTlLo2A4NfRRG9HOprGexQWsrbC2ZB8qYnH9N9M9k7ECXwDhqA1zkWtkQIx MnQUfP9uQrZxkMFaDNO4QIGQpBpcBxwdg/O+E=

Hello, I've just recently started using eigen2 (and I've been lurking on this list for a while), so I can't add much in the way of documentation suggestions for eigen3, but thought I'd add a bit of what I've found missing in the eigen2 documentation. There isn't any discussion of how to create one's own classes. In particular, I'd like to create a class that inherits from MatrixBase (or whatever is necessary) such that I can do arithmetic on this class. It's mostly going to be a large array, but will also contain a bit of metadata. I could, of course, include the array as a data member, but then I wouldn't be able to do vector arithmetic on the objects directly, which would uglify the code. I also wonder if there is a way to create classes such as subclasses of Vector3d, which retain their distinct identity, so you couldn't add together two different such classes. In particular, I'd like to be able to distinguish between real-space and reciprocal-space vectors, and I'd also like to distinguish Cartesian vectors from those which are relative to lattice vectors (which won't be orthogonal in the general case, so dot products shouldn't be used. It'd be nice to have this feature, but if it doesn't really work (e.g. because the sum of two vectors loses its type, or because I lose the ability to take advantage of template expressions), then I'd want to just use plain old Vector3ds, possibly with a few typedefs with which to document which sort of vector a particular object actually is. Anyhow, it'd be nice to have some general discussion of what can and cannot be done in terms of subclassing and extending, suitable for persons who aren't template gurus. Or a discussion of why this sort of thing is a bad idea, if it is. David Roundy (for my current code, see http://github.com/droundy/dafty)

**Follow-Ups**:**Re: [eigen] Proposal: documentation for Eigen3***From:*joel falcou

**Re: [eigen] Proposal: documentation for Eigen3***From:*Benoit Jacob

**References**:**[eigen] Proposal: documentation for Eigen3***From:*Benoit Jacob

**Messages sorted by:**[ date | thread ]- Prev by Date:
**[eigen] Proposal: documentation for Eigen3** - Next by Date:
**Re: [eigen] Proposal: documentation for Eigen3** - Previous by thread:
**[eigen] Proposal: documentation for Eigen3** - Next by thread:
**Re: [eigen] Proposal: documentation for Eigen3**

Mail converted by MHonArc 2.6.19+ | http://listengine.tuxfamily.org/ |