Dear Developers,
I'm in the process of upgrading my code to libmesh 1.0.0
In doing so I found a new behavior of of the
constrain_element_matrix_and_vector.
My problem is as follows:
I solve a system and I have to define some periodic boundary conditions
and some Dirichlet boundary conditions.
On Tue, 29 Nov 2016, Michael Povolotskyi wrote:
> in libmesh one can set communicator in the LibMeshInit and in the Mesh
> constructor.
>
> Imagine, that my Mesh is serial, defined on MPI_COMM_SELF, exists on
> every MPI process.
>
> I want to solve the system only on one MPI process, then I will
On Tue, 29 Nov 2016, Salazar De Troya, Miguel wrote:
On 11/17/16, 7:56 AM, "Roy Stogner" wrote:
I'd say:
Add a DiffSolver::linear_solver() API for returning a reference to a
LinearSolver, and add NewtonSolver and PetscDiffSolver
implementations.
For the PETSc case, that LinearSolver would
Dear developers,
in libmesh one can set communicator in the LibMeshInit and in the Mesh
constructor.
Imagine, that my Mesh is serial, defined on MPI_COMM_SELF, exists on
every MPI process.
I want to solve the system only on one MPI process, then I will
broadcast solution.
Which communicator
On 11/17/16, 7:56 AM, "Roy Stogner" wrote:
>I'd say:
>
>Add a DiffSolver::linear_solver() API for returning a reference to a
>LinearSolver, and add NewtonSolver and PetscDiffSolver
>implementations.
For the PETSc case, that LinearSolver would need to grab the KSP from the
SNES so we can reuse th
