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

A priori evaluation of the time / amount of work needed by Mmg to adapt an input mesh and metric #61

Open
4 tasks
Algiane opened this issue Dec 1, 2022 · 0 comments
Labels
part: mmg3d / mesh specific to mmg3d code part or meshing techniques priority: medium linked to strong improvements or to a medium-term deadline

Comments

@Algiane
Copy link
Member

Algiane commented Dec 1, 2022

At each iteration of ParMmg we have to wait until all groups are adapted by Mmg. If work is not well balanced, we end up with MPI processes waiting.

As load-balancing is less important than forcing the interfaces migration (because non adapted interfaces lead to additional iterations), we would like to have the best load balancing that guarantees the migration of interfaces possible.

For now, load-balancing tries to balance the input number of element. We may want to find a better approximation of the workload from the input mesh and metric. We may want to investigate several tracks:

  • evaluation of the targeted number of elements
  • difference between input and targeted number of elements
  • map of area that needs to be refined and area that needs to be coarsen and evaluation of the adaptation time (coarsening takes longer than refinement)
  • etc.
@Algiane Algiane added part: mmg3d / mesh specific to mmg3d code part or meshing techniques priority: medium linked to strong improvements or to a medium-term deadline labels Dec 1, 2022
@Algiane Algiane moved this to Todo in ParMmg efficiency Dec 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
part: mmg3d / mesh specific to mmg3d code part or meshing techniques priority: medium linked to strong improvements or to a medium-term deadline
Development

No branches or pull requests

1 participant