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

Parallel Solver for Semi-Implicit Navier-Stokes solver #635

Closed
bodhinandach opened this issue May 14, 2020 · 3 comments
Closed

Parallel Solver for Semi-Implicit Navier-Stokes solver #635

bodhinandach opened this issue May 14, 2020 · 3 comments

Comments

@bodhinandach
Copy link
Contributor

bodhinandach commented May 14, 2020

Summary

This RFC is to propose an enhancement of the Navier-Stokes solver in branch solver/navier-stokes and RFC #634. A parallel solver based on PETSc library is planned to be added to the implementation to solve a large scale linear systems of equation in branch solver/navier-stokes-parallel.

Motivation

To add parallel capabilities to the NS solver so that it can be used to solve problems with large number of particles.

Design Detail

The following classes and functionality were implemented:

  1. A specific assembler of NS scheme for parallel usage.
  2. Wrapper to include the capability of PETSc solver to CB-Geo. This includes the capability to wrap Eigen matrices and vectors to PETSc data structures and rank-to-global index mapping.
  3. Integration of NS solver with domain-decomposition and halo-exchange features.
  4. (To be done) Parallel free-surface detection.
  5. (To be done) Add the capability of dynamic load-balancing.
  6. (To be done) To implement parallel incomplete cholesky preconditioner for faster convergence.

Drawbacks

No drawbacks in performance at the moment. It extended the capability of running the semi-implicit solver in a distributed memory machine. The current max number of particles reached 2.4 million, which can be completed in 1 hour for 1000 steps, running in 256 MPI tasks. Further optimization can definitely be done to improve performance.

@kks32
Copy link
Contributor

kks32 commented May 25, 2020

@bodhinandach Could you please add code outlines and details? Please add details for current and future features.

@stale
Copy link

stale bot commented Jul 24, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jul 24, 2020
@bodhinandach
Copy link
Contributor Author

I am closing this RFC and going to merge it together with the RFC #634

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants