Hi Simon,
You could call GridTools:: find_cells_adjacent_to_vertex() with the
triangulation instead of a DoFHandler, and then just convert the returned
iterators to the type used by each DoFHandler using the method outlined here:
https://github.com/dealii/dealii/wiki/Frequently-Asked-Questions#c
And the file is here.
On Saturday, May 1, 2021 at 12:07:13 AM UTC-4 Corbin Foucart wrote:
> Hello all,
>
> When I attempt to use the GDB 'print' command to print information about a
> Point object, I'm having some trouble. For example, suppose I've defined
>
> const Point p_ex(1, 1);
>
>- I
Hello all,
When I attempt to use the GDB 'print' command to print information about a
Point object, I'm having some trouble. For example, suppose I've defined
const Point p_ex(1, 1);
- If I run GDB and attempt 'print p_ex[0]' the output is 'Could not find
operator[]'
- If I attempt '
Hello Wolfgang,
I actually have a Time Measurement in my code implemented.
For my current computations the difference (one call vs two calls per
vertex) is neglible. But my model will become much bigger and therefore I'd
like to avoid unnecessary calls to that function.
Since I can pass only one
On 4/30/21 10:13 AM, Simon wrote:
auto cells_ref = GridTools::find_cells_adjacent_to_vertex(dof_handler_ref,
/*vertex*/);
auto cells_tmp = GridTools::find_cells_adjacent_to_vertex(dof_handler_tmp,
/*vertex*/);
I am not sure how "expensive" this function actually is. I have to call this
func
Dear all,
the mentioned function is exactly doing the right thing for me, i.e.
returning an vector of iterators to all cells, which share this vertex.
After calling this function I will loop over these cells and compute
certain things ...
My problem is that I have to work with two different d
