-
Notifications
You must be signed in to change notification settings - Fork 35
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
composed map: add permute to kwarg #723
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine to me. Happy for this to be merged assuming Firedrake tests pass.
acae6c5
to
b9c031a
Compare
Actually, a pyop2 test failed, which suggested a better fix. Could you have a look again? |
Rerunning Firedrake CI. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like lambdas as properties must be some sort of anti-pattern. Otherwise no issue and definitely better than before.
Co-authored-by: Connor Ward <[email protected]>
Co-authored-by: Connor Ward <[email protected]>
Indeed. Rerunning Firedrake CI. |
firedrakeproject/firedrake#3634
I found this bug when using the submesh branch with BCs on vector components. It is hard to test with our current usage of ComposedMap in Firedrake. I wonder this can just go in.