Hi Doug!
Your scenario indeed revealed a bug: Currently, we set and send
`active_fe_indices` based on the refinement flags on the Triangulation
object. However, p4est has the last word on deciding which cells will be
refined -- and in your specific scenario p4est makes use of it. I came up
On 8/23/19 7:33 AM, Konrad wrote:
>
> Thanks, I see this class makes it possible to identify cells globally in a
> distributed triangulation. I don't see though how the objects in the std::map
> are distributed among cluster nodes as the cells are. Am I missing something
> here?
Yes, the data
On 8/22/19 11:58 PM, Phạm Ngọc Kiên wrote:
>
> I have a question for parallel::distributed::Triangulation
> When 2 cells share 1 edge, but they are living in 2 different MPI processes,
> how can I choose only 1 cell containing the common edge from them.
Is your goal to make sure that only one
Hi Daniel,
> You could create an std::map using CellId (
> https://www.dealii.org/developer/doxygen/deal.II/classCellId.html) as key
> if you need to identify cells uniquely globally.
>
> Best,
> Daniel
>
Thanks, I see this class makes it possible to identify cells globally in a
KIen,
Hi colleagues,
> I have a question for parallel::distributed::Triangulation
> When 2 cells share 1 edge, but they are living in 2 different MPI
> processes, how can I choose only 1 cell containing the common edge from
> them.
> I think I have to set material id for the cell in the first
