Libmesh 0.6.2 0.6.3 changelog
From libMesh Wiki
| Line 1: | Line 1: | ||
The first release candidate of libMesh 0.6.3 is now available for | The first release candidate of libMesh 0.6.3 is now available for | ||
| - | download. New features include: | + | download. |
| + | |||
| + | (Also available, a [[Media:Changelog_062_063.pdf|PDF]] version.) | ||
| + | |||
| + | '''New features include:''' | ||
Continuing experimental ParallelMesh development | Continuing experimental ParallelMesh development | ||
Revision as of 15:53, 18 August 2008
The first release candidate of libMesh 0.6.3 is now available for download.
(Also available, a PDF version.)
New features include:
Continuing experimental ParallelMesh development
More internal parallelization
Operator overloading on scalar/vector/tensor operations with mixed underlying types
Exception throwing, stack trace file output on errors
More norm options for some library methods
Better PETSc nonlinear solver integration
Better line search in libMesh NewtonSolver
You can now force LibMesh to use quadrature rules with positive weights
Grundmann-Moller quadrature rules
Changed/added quadrature rules for TRIs at almost every order, preferring rules with fewer points and positive weights
QMonomial quadrature class for cheaper integration rules for monomial/XYZ bases on QUADs
Recomputed Gauss and Jacobi quadrature rules out to 32 significant digits
Updated Exodus library
Expanded Exodus I/O support, including subdomain ids, multiple timesteps per file
Improved libMesh file formats
Assorted bug fixes, compatibility fixes, efficiency improvements
A few backwards-incompatible API changes have been made:
The macro error() has been replaced with libmesh_error() to avoid name conflicts, and internal assert() calls have been replaced by libmesh_assert() to enable exception-throwing and tracefile output on assertion failures.
The libMesh::init()/close() methods have been replaced by a libMeshInit object's constructor and destructor, to simplify application code slightly and to provide better cleanup behavior when an uncaught exception is thrown. The old methods are now deprecated and will eventually be removed.
