On Thu, Mar 3, 2011 at 9:01 PM, Vijay S. Mahadevan <vija...@gmail.com> wrote: > Roy, > > I think it would be advisable that all libMesh users update themselves > to atleast petsc/slepc 3.0-p0. There are so many fixes/changes from > 2.3.3.->3.0 that it feels like they dont utilize the full potential of > the solvers. Of course, the petsc_macro preprocessor routines would > shield the user anyhow but my point is, should we actually encourage > this ?
I don't think it's a matter of "encouraging" users to continue on 2.3.3 or even to pick up 2.3.3, but rather of maintaining compatibility with 2.3.3 as a libmesh "feature". The relatively minimal (2.3.3 isn't changing any more after all!) amount of work required to maintain this feature is worthwhile and especially beneficial to large install bases where it will still take some time (and system administration) to switch to the 3.x series, even if that switch-over is currently in progress. -- John ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
