MUMPS ICNTL(14)=200 in the default direct solver parameters never reaches MUMPS
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 72/100
Línea de trabajo
Empieza en firedrake/petsc.py, alrededor de _DEFAULT_DIRECT_SOLVER_PARAMETERS y _DEFAULT_KSP_PARAMETERS, y ejecuta después el reproductor de MUMPS proporcionado con -options_left. La corrección estará completa cuando el valor predeterminado llegue a MUMPS como ICNTL(14)=200 y no se informe de ninguna opción de PETSc no utilizada correspondiente.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Describe the bug
The default direct-solver parameters set ICNTL(14) = 200 for MUMPS, but the option never reaches MUMPS: it is composed into pc_factor_mat_mumps_icntl_14, which PETSc reports as an unused option. MUMPS therefore runs with its own default ICNTL(14) = 20.
This silently removes the intended 200% working-space relaxation, making INFOG(1) = -9 ("main internal real/complex workarray too small") more likely on problems with significant extra fill-in — which is exactly the failure mode the default was added to protect against.
Steps to Reproduce
from firedrake import *
from firedrake.petsc import PETSc
mesh = UnitSquareMesh(8, 8)
V = FunctionSpace(mesh, "CG", 1)
u, v = TrialFunction(V), TestFunction(V)
uh = Function(V)
problem = LinearVariationalProblem(
inner(grad(u), grad(v))*dx, inner(Constant(1), v)*dx,
uh, bcs=DirichletBC(V, 0, "on_boundary"))
solver = LinearVariationalSolver(problem) # defaults only
print("solver.parameters:", dict(solver.parameters))
prefix = solver.snes.getOptionsPrefix() or ""
pc = solver.snes.getKSP().getPC()
# ask MUMPS to print its own ICNTL table
PETSc.Options().setValue(prefix + "mat_mumps_icntl_4", "2")
solver.solve()
print("factor Mat prefix:", repr(pc.getFactorMatrix().getOptionsPrefix()))
Run with -options_left:
python3 mwe.py -options_left
Expected behavior
MUMPS reports ICNTL(14) = 200.
Actual behavior
solver.parameters: {'mat_type': 'aij', 'ksp_type': 'preonly', 'ksp_rtol': 1e-07,
'pc_type': 'lu', 'pc_factor_mat_solver_type': 'mumps',
'pc_factor_mat_mumps_icntl_14': 200, 'snes_type': 'ksponly'}
snes prefix: 'firedrake_1_'
factor Mat prefix: 'firedrake_1_'
ICNTL(14) Percentage of memory relaxation = 20
ICNTL(14) Memory relaxation = 20
Unused PETSc option: firedrake_1_pc_factor_mat_mumps_icntl_14
Analysis
The value itself is set with the correct key in _DEFAULT_DIRECT_SOLVER_PARAMETERS:
https://github.com/firedrakeproject/firedrake/blob/main/firedrake/petsc.py#L120-L122
if DEFAULT_DIRECT_SOLVER == "mumps":
_DEFAULT_DIRECT_SOLVER_PARAMETERS["mat_mumps_icntl_14"] = 200
but that whole dict is then nested under a "pc_factor" key and flattened:
https://github.com/firedrakeproject/firedrake/blob/main/firedrake/petsc.py#L137-L143
_DEFAULT_KSP_PARAMETERS = petsctools.flatten_parameters({
"mat_type": "aij",
"ksp_type": "preonly",
"ksp_rtol": 1e-7,
"pc_type": "lu",
"pc_factor": _DEFAULT_DIRECT_SOLVER_PARAMETERS
})
so {"pc_factor": {"mat_mumps_icntl_14": 200}} becomes pc_factor_mat_mumps_icntl_14.
The pc_factor_ nesting is right for mat_solver_type (pc_factor_mat_solver_type is a genuine PCFactor option and does take effect), but MUMPS ICNTL options are not in the PCFactor namespace — they belong to the factored Mat, whose options prefix is just the solver prefix (firedrake_1_ above, with no pc_factor_ segment). The factored matrix looks for <prefix>mat_mumps_icntl_14, so the composed key can never match.
Consistent with that, putting the key at the top level does work:
solver_parameters = {"ksp_type": "preonly", "pc_type": "lu",
"pc_factor_mat_solver_type": "mumps",
"mat_mumps_icntl_14": 77,
"mat_mumps_icntl_4": 2}
# -> ICNTL(14) Percentage of memory relaxation = 77
So the two kinds of options in _DEFAULT_DIRECT_SOLVER_PARAMETERS need different prefixes and cannot be flattened under a single "pc_factor" key.
This is related to, but distinct from, #2250 (user-supplied mg_coarse_mat_mumps_icntl_XX ignored in the multigrid coarse solver): that one is about propagating user options into a sub-solver, whereas this is Firedrake's own default silently not applying.
Environment
- Firedrake 2026.4.1
- PETSc 3.25
- MUMPS 5.8.2
- macOS (arm64)
Verified against main at the time of writing: firedrake/petsc.py lines 122 and 137–143 are unchanged from the installed version.
- 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
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de firedrakeproject/firedrake
-
BUG: NonlinearVariationalSolver errors with adj_kwargsPosiblemente ocupada @dham la tomó hace 151 días. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
firedrakeproject/firedrake#5186 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
firedrakeproject/firedrake#5091 ·
Los mantenedores suelen responder en 1 día
-
documentation
Dificultad 1/5 1-3 horas Aptitud para principiantes 82/100
firedrakeproject/firedrake#3556 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 4/5 3-5 días Aptitud para principiantes 22/100
firedrakeproject/firedrake#5644 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Function.assign on a subset fails with a Constant, a Real Function or abs in the expressionPosiblemente ocupada @connorjward la tomó hace 2 días. Abierto
firedrakeproject/firedrake#5643 · 1 asignado ·
Los mantenedores suelen responder en 1 día
Todos los issues de firedrakeproject/firedrake
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
alltheplaces/alltheplaces#20570 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Los mantenedores suelen responder en 1 día
-
area:ci bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
catincloud-labs/dagster-dex#206 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
number_to_words raises ValueError with threshold= for ordinals ("12th") and comma-grouped strings ("1,000")Posiblemente ocupada @hemtilva la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Los mantenedores suelen responder en 1 día
-
providers security
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
agentbreeder/agentbreeder#1031 ·
Los mantenedores suelen responder en 1 día