Skip to main content
replaced http://scicomp.stackexchange.com/ with https://scicomp.stackexchange.com/
Source Link

In light of thisthis question and some stuff I read online I am wondering if large FE libs (e.g., deal.ii, libmesh etc.) that do AMR keep the entire mesh or possibly a coarse version of the entire mesh on each core. Also, does this limit the size of the problems that can be solved on machines with low RAM per core.

Finally how is load balancing performed? Is the entire mesh repartitioned after each refinement/coarsening step?

In light of this question and some stuff I read online I am wondering if large FE libs (e.g., deal.ii, libmesh etc.) that do AMR keep the entire mesh or possibly a coarse version of the entire mesh on each core. Also, does this limit the size of the problems that can be solved on machines with low RAM per core.

Finally how is load balancing performed? Is the entire mesh repartitioned after each refinement/coarsening step?

In light of this question and some stuff I read online I am wondering if large FE libs (e.g., deal.ii, libmesh etc.) that do AMR keep the entire mesh or possibly a coarse version of the entire mesh on each core. Also, does this limit the size of the problems that can be solved on machines with low RAM per core.

Finally how is load balancing performed? Is the entire mesh repartitioned after each refinement/coarsening step?

Tweeted twitter.com/#!/StackSciComp/status/441296561667342336
Source Link
stali
  • 1.8k
  • 1
  • 10
  • 13

Meshes in codes that do AMR

In light of this question and some stuff I read online I am wondering if large FE libs (e.g., deal.ii, libmesh etc.) that do AMR keep the entire mesh or possibly a coarse version of the entire mesh on each core. Also, does this limit the size of the problems that can be solved on machines with low RAM per core.

Finally how is load balancing performed? Is the entire mesh repartitioned after each refinement/coarsening step?