# MOOSE Newsletter (April 2021)

## MooseTools

We are working on separating many of our support tools (e.g., testing, docs, GUI) into a separate
repository: [moosetools](https://github.com/idaholab/moosetools). This is being motivated by the
desire for non-MOOSE projects to use these tools. This migration will be ongoing for the next few
months and we will do our best to minimize the impact to users.

The effort will include major improvements with respect to portability, extensiblity, and
documentation. The end product will be more robust and useful for MOOSE and non-MOOSE applications.


## Bug Fixes

- When users call `FEProblemBase/DisplacedProblem::reinitElem/NeighborPhys` with
  a vector of physics points, we now only do the reinit with the requested
  problem. Previously when `FEProblemBase::reinitElem/NeighborPhys` was called,
  in the general case, we would attempt to reinit both the undisplaced and
  displaced problems. This would often lead to failed inversion errors out of
  libmesh because a set of physical points may lie within the mesh subdomain for
  the undisplaced problem but not for the displaced problem, or vice versa.

# MOOSE Newsletter (April 2021)

## MooseTools

We are working on separating many of our support tools (e.g., testing, docs, GUI) into a separate
repository: [moosetools](https://github.com/idaholab/moosetools). This is being motivated by the
desire for non-MOOSE projects to use these tools. This migration will be ongoing for the next few
months and we will do our best to minimize the impact to users.

The effort will include major improvements with respect to portability, extensiblity, and
documentation. The end product will be more robust and useful for MOOSE and non-MOOSE applications.


## Bug Fixes

- When users call `FEProblemBase/DisplacedProblem::reinitElem/NeighborPhys` with
  a vector of physics points, we now only do the reinit with the requested
  problem. Previously when `FEProblemBase::reinitElem/NeighborPhys` was called,
  in the general case, we would attempt to reinit both the undisplaced and
  displaced problems. This would often lead to failed inversion errors out of
  libmesh because a set of physical points may lie within the mesh subdomain for
  the undisplaced problem but not for the displaced problem, or vice versa.

## libMesh-level changes

- The NEDELEC\_ONE vector-valued space now supports Tet10 elements
- Added accessors to easily get global sets of boundary or subdomain ids
- User vectors' parallel type is now stored, for more robust restarts
- MetaPhysicL types can now be compatibly nested in Eigen types
- Enabled std::move of data in TIMPI parallel\_sync.h push and pull
- Fixes for wider PETSc version compatibility
- Bugfix in Elem::is\_child\_on\_edge
- Memory leak fix in PetscMatrix::matrix\_matrix\_mult
- Configure option fix for --enable\_petsc\_required

Add libmesh-level changes from the Apr 7 update
Add libmesh-level changes from the Apr 7 update
