Sharing an implementation of ALE for large-deformation thermoplasticity

23 views
Skip to first unread message

Maien Hamed

unread,
Jan 10, 2026, 2:59:20 AM (3 days ago) Jan 10
to deal.II User Group
Hello deal.II community,

I would like to share a research codebase that may be of interest to users working on large-deformation solid mechanics, constitutive modeling, or axisymmetric formulations.

This repository contains a deal.II-based implementation of a finite-strain thermo-viscoplasticity solver using an arbitrary Lagrangian–Eulerian (ALE) formulation. It corresponds to the core implementation described in this article (https://doi.org/10.1007/s00466-023-02303-0) and my PhD thesis on numerical simulation of friction welding processes.

In addition to the constitutive and geometric nonlinearities, the code includes explicit MPI interprocess communication to account for mesh motion in distributed-memory runs, including consistent updating and remapping of nodal fields and quadrature point history variables under reference motion. This may be of interest to users dealing with ALE formulations or other problems where history-dependent material models interact with mesh motion, remeshing, or mesh refinement and coarsening.

The code may also serve as a concrete reference for implementing axisymmetric geometries in deal.II, including rotational symmetry handling and field discretization. Questions about axisymmetric formulations come up periodically on the mailing list, and I hope this example is useful in that context.

Below are screenshots from visualizations taken from the solutions of a Taylor anvil impact problem and an elastoplastic metal necking problem.

The code is research-oriented and not packaged as a tutorial, but it is complete enough to be read, built, and adapted by experienced users.

Comments, questions, or feedback are welcome.

Best regards,

Maien

Screenshot from 2026-01-10 00-20-15.pngScreenshot from 2026-01-10 00-30-19.png

Wolfgang Bangerth

unread,
Jan 11, 2026, 9:40:56 PM (2 days ago) Jan 11
to dea...@googlegroups.com

Maien:
very cool! And yes, we'd love to help make your code accessible to the
community. There are basically two choices:
* It could be part of the code gallery at
https://dealii.org/gallery_applications/code_gallery/
* We can link to it from this page:
https://dealii.org/gallery_applications/applications/

The former category is probably best if you don't intend to do any further
significant work on the code. We do our best to keep these codes compiling
with newer deal.II releases so that it continues to remain useful to the
community. If you think this would be interesting to you, take a look here:
https://github.com/dealii/code-gallery

The latter category is mostly for codes that continue to be developed.

Would any of these work for you?

Best
W.


On 1/9/26 00:59, Maien Hamed wrote:
> *** Caution: EXTERNAL Sender ***
>
> Hello deal.II community,
>
> I would like to share a research codebase that may be of interest to users
> working on large-deformation solid mechanics, constitutive modeling, or
> axisymmetric formulations.
>
> Repository:
> https://github.com/maieneuro/plasticitylab <https://
> nam10.safelinks.protection.outlook.com/?
> url=https%3A%2F%2Fgithub.com%2Fmaieneuro%2Fplasticitylab&data=05%7C02%7CWolfgang.Bangerth%40colostate.edu%7C0a78ac2b452b470810bb08de501e2d90%7Cafb58802ff7a4bb1ab21367ff2ecfc8b%7C0%7C0%7C639036288165280529%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=pAj3viIbiU0yaRptTmH%2BsdPDalhMz59G%2FtX3wXx%2BBAM%3D&reserved=0>
>
> This repository contains a deal.II-based implementation of a finite-strain
> thermo-viscoplasticity solver using an arbitrary Lagrangian–Eulerian (ALE)
> formulation. It corresponds to the core implementation described in this
> article (https://doi.org/10.1007/s00466-023-02303-0) <https://
> nam10.safelinks.protection.outlook.com/?
> url=https%3A%2F%2Fdoi.org%2F10.1007%2Fs00466-023-02303-0&data=05%7C02%7CWolfgang.Bangerth%40colostate.edu%7C0a78ac2b452b470810bb08de501e2d90%7Cafb58802ff7a4bb1ab21367ff2ecfc8b%7C0%7C0%7C639036288165312308%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=ihD2cwmlxX1OLgzcaNOx1dIdcFO65F7ubd740rLaFJM%3D&reserved=0> and my PhD thesis on numerical simulation of friction welding processes.
>
> In addition to the constitutive and geometric nonlinearities, the code
> includes explicit MPI interprocess communication to account for mesh motion in
> distributed-memory runs, including consistent updating and remapping of nodal
> fields and quadrature point history variables under reference motion. This may
> be of interest to users dealing with ALE formulations or other problems where
> history-dependent material models interact with mesh motion, remeshing, or
> mesh refinement and coarsening.
>
> The code may also serve as a concrete reference for implementing axisymmetric
> geometries in deal.II, including rotational symmetry handling and field
> discretization. Questions about axisymmetric formulations come up periodically
> on the mailing list, and I hope this example is useful in that context.
>
> Below are screenshots from visualizations taken from the solutions of a Taylor
> anvil impact problem and an elastoplastic metal necking problem.
>
> The code is research-oriented and not packaged as a tutorial, but it is
> complete enough to be read, built, and adapted by experienced users.
>
> Comments, questions, or feedback are welcome.
>
> Best regards,
>
> Maien
>
> Screenshot from 2026-01-10 00-20-15.pngScreenshot from 2026-01-10 00-30-19.png
>
> --
> The deal.II project is located at http://www.dealii.org/ <https://
> nam10.safelinks.protection.outlook.com/?
> url=http%3A%2F%2Fwww.dealii.org%2F&data=05%7C02%7CWolfgang.Bangerth%40colostate.edu%7C0a78ac2b452b470810bb08de501e2d90%7Cafb58802ff7a4bb1ab21367ff2ecfc8b%7C0%7C0%7C639036288165333500%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=1zvVwwJad4IXMkXAOTxGPl51cg8rA7iGLHklu%2FJ08oo%3D&reserved=0>
> For mailing list/forum options, see https://groups.google.com/d/forum/dealii?
> hl=en <https://nam10.safelinks.protection.outlook.com/?
> url=https%3A%2F%2Fgroups.google.com%2Fd%2Fforum%2Fdealii%3Fhl%3Den&data=05%7C02%7CWolfgang.Bangerth%40colostate.edu%7C0a78ac2b452b470810bb08de501e2d90%7Cafb58802ff7a4bb1ab21367ff2ecfc8b%7C0%7C0%7C639036288165354434%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=6BxsHBBf6na0QYhsQ%2FASphuiWAdZgP5Aj6%2BrFBDBZ%2FA%3D&reserved=0>
> ---
> You received this message because you are subscribed to the Google Groups
> "deal.II User Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dealii+un...@googlegroups.com
> <mailto:dealii+un...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/
> dealii/8e503860-7607-4cf8-a80c-d04fa4c6a264n%40googlegroups.com <https://
> nam10.safelinks.protection.outlook.com/?
> url=https%3A%2F%2Fgroups.google.com%2Fd%2Fmsgid%2Fdealii%2F8e503860-7607-4cf8-
> a80c-
> d04fa4c6a264n%2540googlegroups.com%3Futm_medium%3Demail%26utm_source%3Dfooter&data=05%7C02%7CWolfgang.Bangerth%40colostate.edu%7C0a78ac2b452b470810bb08de501e2d90%7Cafb58802ff7a4bb1ab21367ff2ecfc8b%7C0%7C0%7C639036288165375183%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C40000%7C%7C%7C&sdata=UvgJyED88N6E0u0kO83byobavrVcRTUqFBigAvj0dt8%3D&reserved=0>.

Maien Hamed

unread,
Jan 12, 2026, 3:10:39 PM (19 hours ago) Jan 12
to deal.II User Group

Hi Wolfgang,

thank you for the suggestion and for the offer to help make the code more accessible.

At this point, the codebase is largely stable and research-complete. I do not anticipate major new feature development, though I may apply small fixes or updates if issues are identified. Given that, the code gallery option sounds like the best fit, especially if it helps keep the code building against newer deal.II releases over time.

I will take a closer look at the code-gallery repository and follow up if I have questions about the process or any adjustments needed on my side.

Best regards,
Maien

Reply all
Reply to author
Forward
0 new messages