Adaptive mesh refinement

[simbilod]

It is required for some applications, after the initial meshing, to remesh according to the result of simulations

Earlier versions of this code used callbacks for this, but it is too slow and approximate, because it makes a new mesh every time. Would be great to remesh the existing mesh.

See for example:

• gmsh background mesh,
• mmg,
• DEVSIM example
• Go through skfem refinement

The desired API could be similar to above:

• user gives a grid of (x, y, z, lc) coordinates, with lc the desired "mesh size" at the x, y, z positions;

or

• user gives a grid of (x, y, z) coordinates where the existing mesh should be split

@SkandanC

[simbilod]

I just learned about MMG and it seems the most promising, it is even on pypi https://pypi.org/project/pymmg/

[simbilod]

See some attempts to do this with the callback here https://github.com/gdsfactory/gdsfactory/pull/1074

[SkandanC]

Are these mesh updates done during run time? ie while a sim is running? or is it for upating and rerunning based on a previous sim.

---

From: Simon Bilodeau @.> Sent: Wednesday, July 19, 2023 1:43 PM To: simbilod/meshwell @.> Cc: Skandan Chandrasekar @.>; Mention @.> Subject: Re: [simbilod/meshwell] Adaptive mesh refinement (Issue #11)

See some attempts to do this with the callback here gdsfactory/gdsfactory#1074https://github.com/gdsfactory/gdsfactory/pull/1074

— Reply to this email directly, view it on GitHubhttps://github.com/simbilod/meshwell/issues/11#issuecomment-1642497752, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AX72Z237NGUXBCUPG4VHKPLXRAMEBANCNFSM6AAAAAA2QIJM3M. You are receiving this because you were mentioned.Message ID: @.***>

[simbilod]

I'm not sure there is a difference between these two cases. It's possible that you remesh during "one" simulation, but it would always be based on some intermediate output that would look a lot like the final output