Skip to content

Allow fully traction-free boundaries for elasticity problem#466

Draft
masterleinad wants to merge 1 commit intoadamantine-sim:masterfrom
masterleinad:allow_traction_free_boundary
Draft

Allow fully traction-free boundaries for elasticity problem#466
masterleinad wants to merge 1 commit intoadamantine-sim:masterfrom
masterleinad:allow_traction_free_boundary

Conversation

@masterleinad
Copy link
Copy Markdown
Collaborator

Restricting translation modes seems to be sufficient for MueLU/ML to converge.

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a crucial enhancement to the elasticity problem solver by automatically handling fully traction-free boundary conditions. It ensures the stability and convergence of numerical methods, particularly for multigrid solvers like MueLU/ML, by implicitly restricting rigid body translation modes when no explicit boundary constraints are defined.

Highlights

  • Traction-Free Boundaries: Implemented logic to automatically apply affine constraints for translation modes when no explicit boundary conditions are provided, addressing fully traction-free elasticity problems.
  • Solver Convergence: Enhanced the robustness of the elasticity solver by ensuring convergence for cases with unconstrained boundaries, specifically benefiting multigrid solvers like MueLU/ML.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request introduces logic to automatically apply affine constraints to a boundary node when no explicit boundary IDs are provided, executed on MPI rank 0, to prevent rigid body modes. The current method for selecting and constraining a node on the boundary is identified as potentially fragile and difficult to maintain due to its reliance on internal deal.II DoF ordering, and a more robust approach by explicitly selecting a vertex for constraints has been suggested.

Comment on lines +149 to +162
const dealii::FiniteElement<dim> &fe = cell->get_fe();

const unsigned int dofs_per_face = fe.n_dofs_per_face(face);
std::vector<dealii::types::global_dof_index> face_dof_indices(
dofs_per_face);
cell->face(face)->get_dof_indices(face_dof_indices,
cell->active_fe_index());

std::array<unsigned int, dim> boundary_dofs;
for (unsigned int i = 0; i < dofs_per_face; ++i)
boundary_dofs[fe.face_system_to_component_index(i, face).first] =
face_dof_indices[i];
for (int i = 0; i < dim; ++i)
_affine_constraints.add_line(boundary_dofs[i]);
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

The logic to select a node on the boundary for constraining is difficult to follow. It relies on implementation details of DoF ordering on a face, which makes it fragile and hard to maintain.

A more direct and robust approach is to explicitly select a vertex on the boundary face and constrain its degrees of freedom. This makes the code's intent clear and is less dependent on internal deal.II orderings.

            // Pin the first vertex of the face to remove translational rigid body modes.
            const unsigned int vertex_on_face = 0;
            const unsigned int vertex_on_cell =
                cell->face_vertex_index(face, vertex_on_face);
            for (unsigned int c = 0; c < dim; ++c)
              _affine_constraints.add_line(
                  cell->vertex_dof_index(vertex_on_cell, c));

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.

1 participant