Firedrake meeting 2025 07 02

Date and time 2025-07-02 1600 UTC

Action Items

1. Pick Chair and Minuter (LC not here, someone else pick)
2. ALL: (ongoing) triage the open issues and confirm if they are indeed still open (and perhaps provide labels)
3. ALL: do things with SV's branches
4. DH: Email to Andreas to have 2 (+ others!!!) loopy PRs merged TODO: FIND OUT WHICH PRS THESE ARE
5. DH: Talk to GregVernon about PR#2116.
6. JB: Enable merge queues (minutes)
7. LC: Try to merge RNH' PR: Movable VOM
8. PB: Profile and speed up some tests (minutes, minutes)
9. CW: More testing configurations (minutes)
10. All: Do post merge works (interpolate, abstract reduced functionals, etc.)
11. CW: Preliminary prep for PETSc User Meeting 2026 (minutes)

Agenda

Present:

Apologies: LC

CW: PETSc/SLEPc release woes

Example: https://github.com/firedrakeproject/firedrake/actions/runs/16026361480/job/45215200574

The problem is very obscure. I've identified it but the fix is to either always stick to the latest release or build petsc4py and slepc4py differently.

JHC: Attach OptionsManager to a single PETSc Object

petsctools #7

Each instance of OptionsManager is meant to be used for only one PETSc object, but this isn't enforced anywhere. In Firedrake the solver classes to connect one OptionManager to one PETSc object. This PR adds some free functions to make it easier to do this only with petsctools.

Merge PRs

Note that PRs put in this section should either be trivial or already have been reviewed. Discussion-worthy PRs should be separate agenda items.

Date of next meeting

1600 UTC 2025-07-09