On Wed, May 30, 2012 at 11:19 AM, Paul T. Bauman <ptbau...@gmail.com> wrote: > All, > > I've attached a patch and two files for step 0 on this (drop fe_abstract.h > and fe_abstract.C in include/fe and src/fe respectively - svn cp doesn't > really yield proper patches). You can also find them here if the list > filters them out: http://users.ices.utexas.edu/~pbauman/fe_abstract/ > > This moves common stuff into the newly created FEAbstract class from which > FEBase now derives (and future FEVectorBase will derive). Things that > directly call get_phi() etc, are still in FEBase - with the exception of the > geometry maps which always instantiate Lagrange elements, so they got left > in FEAbstract.
One question about the design here: H(div) elements will presumably require a different type of mapping [0] than what FEBase currently does with Lagrange. So, should the geometry mapping stuff really be moved up into FEAbstract, or would it be better to have virtual interfaces for that which can be redefined by FEVectorBase? [0] http://www.math.uh.edu/~rohop/spring_11/downloads/Chapter7.pdf, pg. 17 -- John ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
