GitLab

Allows selecting output format for PETScSparseMatrix object

See merge request !395

Kohl/moc

See merge request !394

* The classes' print function now accepts a second optional argument of
  type PetscViewerFormat. Any valid format is possible, as this will just
  be passed on to PETSc. Default value is PETSC_VIEWER_ASCII_MATRIXMARKET.
* The exportOperator() function now requires the format as an argument; it
  now also lives in the petsc namespace.
* The exportOperatorMatrix app allows to select either MATRIXMARKET or
  MATLAB format on the command-line.

CouplingCountTest

See merge request !393

Change ci combinations

See merge request !392

Coupling Count

See merge request !391

Fixes out-of-bounds error in initialisation of std::array

* fixes signedness of loop counter in show_mesh.cpp
* declutters refCellCouplingCount

Adds sub-test for P2-P1 Taylor Hood Stokes operator in 3D to
CouplingCountTest test.

Commit brings a correct implementation for the 3D case of the EdgeDoF to
EdgeDoF coupling counting.

By passing the argument P2EDGEMASS we can now export the mass matrix for
the edge dofs of a P2 element only.

Commit extends the free-function so that is can also work with scalar
EdgeDoFOperators.

Tests now work for P2 functions on a single tetrahedron. We still are
missing some couplings though when we have meshes with multiple macro-
cells.

The app now also counts EdgeDoF to VertexDoF couplings and makes some
statistics.

The implementation gives correct results for the case of a single
macro-cell, but is untested for more complicated meshes, yet.

Determining the number of couplings of type EdgeDoF-EdgeDoFs and
EdgeDoF-Vertex-DoF is tricky in 3D. This app does this for a single
tetrahedron and performs some verifications, too.

Currently only investigates EdgeDoF-EdgeDoF couplings.

We can now also ask the app to print the number of vertex and edge dofs
for a given mesh on a speficied refinement level.

The idea of this function is to return for a given operator
the number of couplings between degrees of freedom. Modulo
elimination of Dirichlet boundary conditions and zero coupling
weights this will correspond to the number of non-zeros in
the sparsity pattern of the associated matrix.

Note that the coupling counts will only depend on the function
spaces involved, but not on the specifics of the operator resp.
bilinear form.

Thus, getNumberOfDoFCouplings() is a driver that in turn relies
on the actual counting being done in the countLocalDoFCouplings()
function. Its purpose is mostly to determine from the operator
the underlying sub-operators and function spaces.

This commit implements the functionality for 2D and for
P1Operators in 3D.

Further work on coupling count

- 2D case works now for P1-P1 for the "All" case
- In 3D the results are incorrect
- Started adding BC stuff, but will remove that again, as it get's
  too complicated; we would need to discard not only the to but also
  the from couplings on those primivites.

Coupling count now works also for scalar P2 operators in 2D

* Implemented the basic VertexDoFFunction and EdgeDoFFunction combos as
  building blocks.
* Removed all boundary condition stuff.

Makes getNumberOfGlobalDoFCouplings() a free-function

The reason for this is that inside the Operator class we do not have
enough information to compute the number of couplings for block operators
such as Stokes. For those cases it is not only the supports of the
ansatz functions that determine the number of couplings, but also the
block structure of the operator itself.

CouplingCountTest now also works for P2-P1Taylor-Hood-Stokes operators
in 2D.

Fixes problem with CouplingCountTest when building w/o PETSc

Completes implementation of countLocalDoFCouplings for P1Functions in 3D

The CouplingCountTest now runs through for a P1Operator on the 3D mesh
pyramid_4el.msh. Thanks to Nils for pointing out to use getLocalEdgeID()
to get the edge into cell couplings right.

Method will return the number of nonzero matrix entries; is implemented
for PETScSparseMatrixInfo class.

PETSc functions and namespace consistency

See merge request !390

* Commit moves createMatrix() functions from edgedof, EdgeDoFToVertexDoF
  and VertexDoFToEdgeDoF namespaces to petsc namespace.
* Additionally the applyDirichletBC() and createFunctionFromVector()
  functions in edgedof are also transfered to petsc namespace.
* This is consistent with the way it is handled for the P1 and P2 cases
  and allows to create PetscSparseMatrix objects also for these operators
  by calling the corresponding class method.

The EdgeDoFFunction class was missing the valueType and FunctionType
member definitions that we have in the P1Function and P2Function.
Commit adds them for consistency and completeness.

Fixes / extensions for exportOperatorMatrix app

See merge request !389

* Elimination of DoFs associated with Dirichlet boundary conditions
  was not working correctly. Fixed this by inserting a call to set
  the primitive flags correctly via setMeshBoundaryFlagsOnBoundary()
* The exportOperator() function now allows to ask for unsymmetric
  elimination, which we can use from within the app.
* App is now more robust and will detect wrong operator names on cli.