Skip to content

Conversation

@leo-collins
Copy link
Contributor

allow assembly of uncoupled multi-domain problems

Copy link
Contributor

@connorjward connorjward left a comment

Choose a reason for hiding this comment

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

I wonder if all this logic should simply be

connorjward
connorjward previously approved these changes Dec 4, 2025
@leo-collins
Copy link
Contributor Author

Don't merge, it isn't right yet

@connorjward connorjward marked this pull request as draft December 4, 2025 13:59
@connorjward
Copy link
Contributor

Don't merge, it isn't right yet

Please leave this as a draft PR then

@leo-collins leo-collins marked this pull request as ready for review December 16, 2025 16:18
@leo-collins
Copy link
Contributor Author

@connorjward Can this be merged? The errors look unrelated.

@connorjward
Copy link
Contributor

I agree. @UZerbinati it looks like your merges into ngsPETSc have broken things. I will try to fix them when I move things over (imminently).

@connorjward connorjward merged commit 0b8184a into main Dec 17, 2025
5 of 7 checks passed
@connorjward connorjward deleted the leo/multi-domain-assemble branch December 17, 2025 15:10
@UZerbinati
Copy link
Contributor

UZerbinati commented Dec 17, 2025

I agree. @UZerbinati it looks like your merges into ngsPETSc have broken things. I will try to fix them when I move things over (imminently).

I don't see what I've broken, all Firedrake test's passed in ngsPETSc before merging.

@connorjward so the incriminated line seems to be:
mesh.geometric_dimension()
which doesn't raise any error in the Firedrake docker container which we use for testing in ngsPETSc. When did this behavior change ?

Also this error is not reproducible in my local machine with a new Firedrake installation :(

@connorjward
Copy link
Contributor

I don't see what I've broken, all Firedrake test's passed in ngsPETSc before merging.

They passed on Firedrake release branch, not main.

When did this behavior change ?

See #4629

@connorjward
Copy link
Contributor

I fixed this for ngsPETSc in NGSolve/ngsPETSc#94, before you made more changes.

It's fine. Release still works which is the most important thing. I'll sort this all out tomorrow hopefully.

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.

5 participants