All,
Sorry if this is a stupid question, but why are dphidx, dphidy, etc. being
explicitly stored in FEGenericBase? We are duplicating what's stored in
dphi and d2phi. What's wrong with just returning dphi[i][qp].slice(0) for
dphidx, etc.? AFAICT, dphidx etc. are only ever set, they're never
explicitly used in the library. We can remove them and still preserve the
API. Am I missing something?
Motivation (beyond reduced storage): makes my FETransformation API much
cleaner, particularly for hessians.
If I'm not missing anything, any objections to me cooking up a patch?
Thanks,
Paul
------------------------------------------------------------------------------
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
