I tested the implementations with the example from step 12, but refinement
after one step ist not allowed (else I will get the error "ou are trying to
access the matrix entry with index <>", which means that either my code is
wrong, or something else is not working correctly. The question is:
> Is there a reason then that there are several examples using
> integration_loop(), but (afaik) only one using mesh_loop?
Yes. mesh_loop is more recent w.r.t. integration_loop.
mesh_loop was introduced to address some of the oddities that are in
integration_loop, that make its use somewhat
Is there a reason then that there are several examples using
integration_loop(), but (afaik) only one using mesh_loop?
Am Montag, 18. März 2019 19:46:41 UTC+1 schrieb Luca Heltai:
>
> Take a look at this PR for a few examples of usage of mesh_loop:
>
> https://github.com/dealii/dealii/pull/7806
Take a look at this PR for a few examples of usage of mesh_loop:
https://github.com/dealii/dealii/pull/7806
The function WorkStream::run
takes (a minimum of) 5 arguments:
WorkStream::run(cell, endc, cell_worker, copier, scratch, copy);
initial and final iterator, a worker function, a copier
I was wondering about the difference between calling mesh_loop (from
MeshWorker) and run (from WorkStream). According to the documentation it is
possible to simply replace run() with mesh_loop() when only looping about
own cells, while still having the possibility to extend the program later
