Dear all
There are lot of vector<vector> stuffs in the FE and FEMap classes. Why do
we use this instead of a well defined matrix class. I think there are
several drawbacks to use vector<vector> as a matrix. There is a discussion
on this at stackexchange.
http://scicomp.stackexchange.com/questions/3159/is-it-a-good-idea-to-use-vectorvectordouble-to-form-a-matrix-class-for-high/3182#3182
Several drawbacks people mentioned
1. redundant data structures (multiple rows points)
2. scattered memory.
3. bad cache efficiency
Is there any reason to use vector<vector>? Thanks.
BTW, I'm confused about the difference between the template class
FEGenericBase and pure virtual class FEAbstract. Why do we need FEAbstract?
It seems that we can put everything from FEAbstract into FEGenericBase.
Since all FE class just inherits from FEGenericBase. Why add an extra level
to the class inheritance hierarchy?
Sincerely Yours,
Lei Shi
----------
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
