Firedrake meeting 2024 12 11 - firedrakeproject/firedrake GitHub Wiki

Date and time 2024-12-11 1600 UTC

Action Items

Pick Chair and Minuter (CW to pick)
ALL: (ongoing) triage the open issues and confirm if they are indeed still open (and perhaps provide labels)
~~CW (formerly JB): Move TSFC to firedrake and move FInAT to FIAT~~ (Done)
ALL: do things with SV's branches
DH: Email to Andreas to have 2 (+ others!!!) loopy PRs merged TODO: FIND OUT WHICH PRS THESE ARE
DH: Get Firedrake a docker open source account (link here)
DH: Talk to GregVernon about PR#2116.
JB: Enable merge queues (minutes)
LC: Try to merge RNH' PR: Movable VOM
~~ANY: Add Python 3.13 to PyOP2, TSFC, FIAT, FInAT CI (and others?)~~ (Done)
PB: Profile and speed up some tests (minutes, minutes)
RK: sort out Firedrake USA details and website before Christmas time
CW: fix PyOP2+TSFC failing tests
CW: Fix artefactsv3 issue

Present: CW (minuter), SM, RK, PB, IM, KS, DD, DH

Apologies: JHC

I have a PR with the Web page that's approved, but it's failing CI tests for seemingly unrelated things like PyOP2 and TSFC.
Update: we have a travel support request form, are waiting on a business office person to give us a registration link.
Merged.

Someone just reported that Firedrake fails with an int64 build. Since we don't test it we didn't notice. My proposal:

We should have a set of smoke tests that target a large surface where we encounter issues (e.g. libsupermesh, VoM, parallel, ...). This should take ~5 minutes to run (and we can even call it make check).
We can run a larger number of possible Firedrake configurations whenever we merge to master (e.g. int64, OpenMPI?, etc). We can also run them if we apply a sensible label like we do for MacOS (ci:macOS, ci:int64, etc). Using pip it only takes about 30 minutes for a workflow to run.
DH: Tentative approval.
Action point CW make this happen.

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

This would be better exposed via form_compiler_parameters. PR is not required.