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

Add "MFEM in the Real World" page to showcase application/project examples #204

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

hauten
Copy link
Contributor

@hauten hauten commented Dec 29, 2022

  • Closes Add a page for MFEM-based applications #195 (or at least provides a starting place)
  • Adds new page and link in site menu (under Community)
  • Provides three example projects on the page, with images
  • Includes a template for contributors to add their project to the page

@tzanio tzanio requested a review from acfisher December 29, 2022 20:16
@tzanio
Copy link
Member

tzanio commented Dec 29, 2022

Thanks @hauten!


<img src="../img/rodin.png" align="left" style="margin-top: 2px; margin-right: 10px" width="225" alt="colorful simulation on a complex mesh">

[Rodin](https://cbritopacheco.github.io/rodin/) is a lightweight, modular shape, density, and topology optimization framework written in C++, enabling the rapid prototyping of shape optimization algorithms. Rodin provides many of the associated functionalities needed when implementing shape and topology optimization algorithms. These functionalities range from refining and remeshing the underlying shape, to providing elegant mechanisms to specify and solve variational problems. Rodin allows for easy specification and resolution of variational problems, provides uniform class interfaces and transparent conversions between different types of meshes and grid functions, enforces semantic rules related to weak formulations, and adds functionalities of its own on top of wrapped classes. The software library uses MFEM for solving and assembling the linear systems related to the weak formulations.
Copy link
Member

Choose a reason for hiding this comment

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

I would change the order in the last sentence to "assembling and solving".


<img src="../img/wellbore.png" align="left" style="margin-top: 2px; margin-right: 10px" width="225" alt="cylindrical wellbore surrounded by a rainbow-colored mesh on gray 3D grid">

[OpenSim Technology](https://opensim.technology/) models subsurface wellbores to prevent collapse. The project’s equations solve for mechanical equilibrium linear elasticity, using PyMFEM to implement the solution. OpenSim’s synthetic well model requires a refined mesh around the wellbore itself to accurately capture stress points, then a coarser mesh farther away from that focal point. The model can compute a second grid of concentric rings, which depict stresses around the cylindrical wellbore and identify failure zones. The team has implemented performance speedups with parallel processing, and they are working on a web app for engineers to use in the field.
Copy link
Member

Choose a reason for hiding this comment

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

I think this could use some rewording:
models the structural mechanics of subsurface wellbores to prevent collapse. The project uses pyMFEM to solves the equations of linear elasticity for mechanical equalibrium. OpenSim’s synthetic well model requires a refined mesh around the wellbore itself to accurately capture stress points, and uses a coarser mesh farther away from that focal point in order to keep the computational cost down. The model can compute a second grid of concentric rings, which depict stresses around the cylindrical wellbore and identify failure zones. The team continues to develop this code and has recently implemented performance speedups with parallel processing, and they are working on a web app for engineers to use in the field.


<img src="../img/placeholder.png" align="left" style="margin-top: 2px; margin-right: 10px" width="225" alt="placeholder image">

Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo. Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt. Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim ad minima veniam, quis nostrum exercitationem ullam corporis suscipit laboriosam, nisi ut aliquid ex ea commodi consequatur.
Copy link
Member

Choose a reason for hiding this comment

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

I like how you used the actual Cicero here rather than the usual mangled Lorem Ipsum! I believe that last sentence should end in a question mark, and I recommend finishing out the passage for all of the Cicero lovers out there:
Quis autem vel eum iure reprehenderit qui in ea voluptate velit esse quam nihil molestiae consequatur, vel illum qui dolorem eum fugiat quo voluptas nulla pariatur?

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.

Add a page for MFEM-based applications
3 participants