Skip to content

Move __future__ interpolation into interpolation.py #4346

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 26 commits into from
Jul 3, 2025
Merged

Conversation

leo-collins
Copy link
Contributor

Description

Moves new interpolation behaviour from firedrake.__future__ into firedrake.interpolation and updated docs and demos.

dham
dham previously approved these changes Jun 26, 2025
@dham dham merged commit 6f853a7 into master Jul 3, 2025
18 of 21 checks passed
@dham dham deleted the new-interpolate branch July 3, 2025 13:46
@@ -182,8 +176,7 @@ def interpolate(
to zero. Ignored if interpolating within the same mesh or onto a
:func:`.VertexOnlyMesh`.
:kwarg ad_block_tag: An optional string for tagging the resulting assemble block on the Pyadjoint tape.
:returns: a new :class:`.Function` in the space ``V`` (or ``V`` if
it was a Function).
:returns: A synbolic :class:`.Interpolate` object
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo

@@ -1,14 +1,11 @@
import firedrake.assemble as assemble
import firedrake as fd
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure whether we want to import firedrake as fd within the source code. Usually we resolve circular imports with assemble by importing it inside the functions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants