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

MueLu: Fix node-based interface aggregation for >1 DoFs per dual node #13859

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

PhilipOesterlePekrun
Copy link

@trilinos/muelu

Motivation

In the current state, it was found that the interface aggregation algorithm, which is based on a dual node to primal node mapping, fails for block matrix systems with dual (Lagrange multiplier) nodes with greater than 1 degree of freedom.

Description

This commit fixes the issue by adding dual amalgamation info and fixing the computation of the dual node map. The necessary structure of the input ParameterLists for this case required a slight adaptation as well.

Testing

A mesh tying test, MeshTyingBlocked_NodeBased_simpleSmoother_3dualDofs, is included in this commit and works in serial and in parallel (MPI_1, MPI_4).

@mayrmt
@maxfirmbach

@PhilipOesterlePekrun PhilipOesterlePekrun requested a review from a team as a code owner March 8, 2025 06:11
@trilinos-autotester
Copy link
Contributor

Status Flag 'Pre-Test Inspection' - - This Pull Request Requires Inspection... The code must be inspected by a member of the Team before Testing/Merging
NO INSPECTION HAS BEEN PERFORMED ON THIS PULL REQUEST! - This PR must be inspected by setting label 'AT: PRE-TEST INSPECTED'.

Copy link
Contributor

Choose a reason for hiding this comment

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

Can we use a smaller matrix for the test?

Copy link
Contributor

Choose a reason for hiding this comment

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

I would encourage you to use Kokkos data structures where possible for new code.

@maxfirmbach
Copy link
Contributor

maxfirmbach commented Mar 8, 2025

@PhilipOesterlePekrun @mayrmt I would personally like to see a unit test, which directly tests the implemented functionality with it's dedicated input and output. The framework test is a nice addition, but doesn't exactly proof if the implementation is correct.

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