[beaminteraction]Add postprocess routine for Dual Lagrange Multipliers - #2129
Open
dharinib98 wants to merge 1 commit into
Open
[beaminteraction]Add postprocess routine for Dual Lagrange Multipliers#2129dharinib98 wants to merge 1 commit into
dharinib98 wants to merge 1 commit into
Conversation
dharinib98
changed the title
mayrmt
reviewed
Jul 15, 2026
mayrmt
left a comment
mayrmt
left a comment
Member
There was a problem hiding this comment.
@dharinib98 is it true, that this change is related to the runtime output? If yes, please add an output test.
isteinbrecher
left a comment
isteinbrecher
left a comment
Contributor
There was a problem hiding this comment.
Thanks for the contribution @dharinib98.
I have two additional questions:
- How is the post processing actually done? (Maybe we should talk about this internally)
- Why are there no adapted test results / failing tests with this change?
| point_coordinates.push_back(Core::FADUtils::cast_to_double(X(dim))); | ||
| displacement.push_back(Core::FADUtils::cast_to_double(u(dim))); | ||
| lambda_vis.push_back(Core::FADUtils::cast_to_double(lambda_discret(dim))); | ||
| lambda_postprocessed_vis.push_back( |
Contributor
There was a problem hiding this comment.
Can we do this in the constextpression if before?
| auto& visualization_data = visualization_writer->get_visualization_data(); | ||
| visualization_data.register_point_data<double>("displacement", 3); | ||
| visualization_data.register_point_data<double>("lambda", 3); | ||
| visualization_data.register_point_data<double>("lambda_postprocessed", 3); |
Contributor
There was a problem hiding this comment.
We now initialize this even, if we don't need the postprocessed lambda. We should not do this postprocessing in cases where we don't need it. We can either automatically do the post processing for the dual shapefuctions or have an input file option postprocess_lambda that allows to turn this on/off (I prefer the input file option).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description and Context
This PR implements post-processing of the Lagrange multipliers obtained with the dual LM approach(see #2009), enabling the visualization of smooth Lagrange multiplier curves. The implementation follows the reconstruction described in Equations (34) and (35) of Seitz et al., “Isogeometric dual mortar methods for computational contact mechanics.”
Related Issues and Pull Requests