Skip to content

Fix dual adjoint BC setter#1612

Open
ebchin wants to merge 5 commits into
bugfix/ebchin/fe-dual-movefrom
bugfix/ebchin/fix-dual-adjoint-bcs
Open

Fix dual adjoint BC setter#1612
ebchin wants to merge 5 commits into
bugfix/ebchin/fe-dual-movefrom
bugfix/ebchin/fix-dual-adjoint-bcs

Conversation

@ebchin

@ebchin ebchin commented Jun 2, 2026

Copy link
Copy Markdown
Member
  • Improves parsing of dual adjoint BC field names (first tries to match in derived class, then calls base class version)
  • Makes the "contact_force" dual adjoint BC work correctly (so you can calculate sensitivities w.r.t. all of the contact forces)

@ebchin ebchin self-assigned this Jun 2, 2026
/// @overload
const FiniteElementState& dualAdjoint(const std::string& dual_name) const override
{
if (isAggregateContactForceName(dual_name)) {

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I would vote for us not supporting aggregated contact interaction forces at all. it makes no sense to me personally as an output in the first place and LiDO users can just compute it themselves by summing contact interactions if they ever come up with some justification. I think it adds too much unneeded complications.

@ebchin ebchin changed the base branch from develop to bugfix/ebchin/fe-dual-move June 8, 2026 18:51
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.

2 participants