Skip to content
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

Firedrake warnings #137

Open
ReHoss opened this issue Feb 28, 2024 · 3 comments
Open

Firedrake warnings #137

ReHoss opened this issue Feb 28, 2024 · 3 comments

Comments

@ReHoss
Copy link

ReHoss commented Feb 28, 2024

Running Firedrake (0.13.0+6053.g93d4834ff) freshly downloaded from their installation script, I get the following deprecation warnings, I think the interpolation part can be fixed easily by applying the recommended replacement instruction. I could try to make a Pull Request for the interpolation part. However, I don't know Firedrake very much.

/home/firedrake/firedrake/src/firedrake/firedrake/function.py:325: FutureWarning: The .split() method is deprecated, please use the .subfunctions property instead
warnings.warn("The .split() method is deprecated, please use the .subfunctions property instead", category=FutureWarning)
/home/firedrake/firedrake/src/firedrake/firedrake/interpolation.py:385: FutureWarning: The use of interpolate to perform the numerical interpolation is deprecated.
This feature will be removed very shortly.

Instead, import interpolate from the firedrake.__future__ module to update
the interpolation's behaviour to return the symbolic ufl.Interpolate object associated
with this interpolation.

You can then assemble the resulting object to get the interpolated quantity
of interest. For example,

from firedrake.__future__ import interpolate
...

assemble(interpolate(expr, V))

Alternatively, you can also perform other symbolic operations on the interpolation operator, such as taking
the derivative, and then assemble the resulting form.

@jcallaham
Copy link
Collaborator

Can you try pulling main and see if you still get these? This should have been resolved by #133, although I don't think we've rebuilt the Docker images yet.

Copy link
Collaborator

Currently rebuilding all the containers, we should hopefully be on top of the warnings soon.

@ReHoss
Copy link
Author

ReHoss commented Feb 28, 2024

Can you try pulling main and see if you still get these? This should have been resolved by #133, although I don't think we've rebuilt the Docker images yet.

I use my own container with the last main hydrogym branch from 2-3 weeks ago. I am going to pull the last hydrogym main branch and let you know.

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

No branches or pull requests

3 participants