BUG: Real Space Forms are sometimes assembled incorrectly

Abierto
#5,480 1 comentario 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@connorjward ya está trabajando en esto.

Desde el 23/9/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

bug

Forms are sometimes assembled incorrectly. See the MWE below.

This is probably an important issue. It was causing instabilities in an Irksome script of mine, since Irksome internally uses real spaces in the MeshConstant class.

I presume the issue is due to compiler optimisations; the problem goes away by setting PYOP2_CFLAGS=-fno-tree-loop-vectorize.

from firedrake import *

mesh = UnitSquareMesh(5, 5)

# Create a vector function, and a real function
U = VectorFunctionSpace(mesh, "CG", 2)
u = Function(U).interpolate(as_vector((1, 0)))

R = FunctionSpace(mesh, "R", 0)
alpha = Function(R).assign(0)

# Compute errors between functionals, using different measures
def errors(measure):

    # Create two functionals acting on Q = CG1
    Q = FunctionSpace(mesh, "CG", 1)
    q = TestFunction(Q)

    F = dot(u, grad(q))*measure     # This functional is non-zero
    zero_term = alpha*q*measure     # This functional is zero

    # Form the Riesz representers of the functionals
    combined = assemble(F + zero_term).riesz_representation("l2")
    original = assemble(F).riesz_representation("l2")
    zero = assemble(zero_term).riesz_representation("l2")

    return errornorm(combined, original), norm(zero)

# Compute errors for default and degree-15 measures
default = errors(dx)
degree_15 = errors(dx(degree=15))

print(f"default:   difference={default[0]:.3e}, zero term={default[1]:.3e}")
print(f"degree 15: difference={degree_15[0]:.3e}, zero term={degree_15[1]:.3e}")

# SCRIPT OUTPUT:
# default:   difference=7.676e-18, zero term=0.000e+00
# degree 15: difference=3.546e-03, zero term=0.000e+00
Lenguaje dominante
Python
Estrellas
684
Forks
204
Merge medio
4 d 14 h
PR fusionados (30 d)
46

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de firedrakeproject/firedrake

Todos los issues de firedrakeproject/firedrake

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.