Recent changes to Forms? #4196
-
I have a firedrake code that I haven't run in a few months. After updating firedrake I am getting the following stack trace:
Any ideas about how to fix/update our code? The |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
I think this issue was introduced some time ago when |
Beta Was this translation helpful? Give feedback.
-
This does look like it is due to the changes in #3947, specifically the changes from #3922 that were also merged in that PR. You can see that (what I assume is) the equivalent argument in The default behaviour for dealing with boundary conditions was also changed in that PR - boundary conditions are assumed to already be enforced on the solution and the residual at boundary condition nodes is zeroed out - so you might have to make some changes there. You could compare your code to the the current On a separate note, if you have a version of |
Beta Was this translation helpful? Give feedback.
This does look like it is due to the changes in #3947, specifically the changes from #3922 that were also merged in that PR.
The
tensor
argument toassemble
now must be aCofunction
, whereas previously it was allowed to be aFunction
for backwards compatibility with pre-Cofunction code.You can see that (what I assume is) the equivalent argument in
firedrake.SCPC
is now aCofunction
:firedrake/firedrake/slate/static_condensation/scpc.py
Line 81 in 099ea9d
The default behaviour for dealing with boundary conditions was also changed in that PR - boundary conditions are assumed to already be enforced on the solution and the residual…