From: Roy S. <roy...@ic...> - 2005-08-23 15:20:59
|
On Tue, 23 Aug 2005, John Peterson wrote: > At the risk of repeating an existing idea or muddling the discussion > further, Dave and I have been thinking of something like a map<string, > CachedData*> The string keys can be generated in a logical way, e.g. > > "QUAD4_LAGRANGE_SIDE0" I'd make the map a static member of each FE class and leave the FE type out of the key... or at least that's what I'd do in an inheritance-based class tree. Is it possible to overload static members based on template argument? > Or whatever names are more appropriate. This seems to be a smaller > issue than the question of what to cache and where (i.e. what type > of class CachedData is). Depends on what we can cache. For most elements, that's phi, dphidxi, d2phidxi2, and higher dimension counterparts - am I missing anything? For a few elements (Clough, IIRC Hierarchic) we can't really cache dphidxi and d2phidxi2, but we can use the same amount of space to cache data which would make calculating dphidxi and d2phidxi2 faster. --- Roy |