On 12/4/20 6:18 AM, shahab.g...@gmail.com wrote:
Not here, but it other functions it would be very useful to be able to map
back to the owning particle.
I suspect that in that case, it wouldn't be cheaper to loop over particles and
map back to particles, but that you could as well loop over particles to begin
with.
In fact, I have to treat local and ghost particles differently. In terms of
updating properties, I only need to update the properties of local particles.
This is where things get difficult. The PropertyPool doesn't know which
particle properties correspond to locally owned or ghost cells -- and I'd
argue that it shouldn't know that either. PropertyPool is really just a
slightly more intelligent way to allocate memory on the heap. What the
*meaning* of what it stores is not something it knows about, and I don't think
it should.
If you needed to do something different between locally owned or ghost
particles, you'd have to store information in duplicate in some way, and that
presents the potential for things to go out of sync.
Best
W.
--
------------------------------------------------------------------------
Wolfgang Bangerth email: bange...@colostate.edu
www: http://www.math.colostate.edu/~bangerth/
--
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/15633ff5-245f-e536-c087-b35a8ec83ceb%40colostate.edu.
