I guess for your purpose, `VectorTools::point_values()` and `VectorTools::point_gradients()` are more useful and it works in parallel. If the location of the points do not change, they are cached in RemotePointEvaluation.
> If I am not refining the mesh, is there a more efficient why of accomplishing this? I assume by storing the specific cell that loc is in? Indeed, this is happening internally in RemotePointEvaluation. It stores the cell and the reference positions. In a second step the actual evaluation is done efficiently by FEPointEvaluation. If the interface is too high level for your purposes, you can take a look at the implementations of the setup routines, which uses GridTools::internal::distributed_compute_point_locations. Hope this helps, Peter On Thursday, 28 July 2022 at 22:15:43 UTC+2 andre...@gmail.com wrote: > I currently have the solution to a PDE stored in a Vector<double> solution. > I need to compute the solution at some Point<2> loc. I accomplish this > using the function > > VectorTools::point_value(dof_handler, solution, loc, val); > > which fills val with the value I care about. Similarly, I get the > gradient with point_gradient. > > This accomplishes what I need but if I have a lot of points like loc and > have to do this every timestep then it quickly becomes a computational > bottleneck. > > If I am not refining the mesh, is there a more efficient why of > accomplishing this? I assume by storing the specific cell that loc is in? > -- The deal.II project is located at http://www.dealii.org/ For mailing list/forum options, see https://groups.google.com/d/forum/dealii?hl=en --- You received this message because you are subscribed to the Google Groups "deal.II User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to dealii+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dealii/0b0b141a-5f0d-4793-9ca1-12414bb8f779n%40googlegroups.com.
