nate
November 3, 2022, 6:26pm
2
I believe this is because elements of type Real are not supported by dolfinx. There’s a great deal of discussion of the best way to do this. The main problem is that populating an entire row of a matrix kills performance.
Perhaps @mscroggs or @dokken know more.
opened 11:02AM - 02 Feb 22 UTC
enhancement
`ufcx_dofmap` has a `global_support_dofs` property, which I believe the aim of w… hich is to support Real spaces (spaces with one DOF for the entire mesh). Currently this option is unused in DOLFINx.
I've been attempting to implement real spaces in the branch https://github.com/FEniCS/dolfinx/tree/mscroggs/real-space (and https://github.com/FEniCS/ffcx/tree/mscroggs/real-space)
opened 09:46PM - 28 Oct 18 UTC
bug
performance
Snippet
```python
import dolfin
mesh = dolfin.UnitSquareMesh(dolfin.MPI.comm_… world, 2, 2)
dolfin.FunctionSpace(mesh, ("Real", 0)).dofmap().dofs(mesh, 2)
```
returns
```python
array([0, 1, 2, 3, 4, 5, 6, 7], dtype=int32)
```
but should return (as in 2018.1.0)
```python
array([0, 0, 0, 0, 0, 0, 0, 0], dtype=int32)
```
In other words, `Real` works now as `DG0`, having one scalar per each cell, instead of one scalar per whole domain.
1 Like