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
Hello Shahab,
I would wait before trying to do some changes. Rene has started looking
more deeply into the particle structure (see
: https://github.com/dealii/dealii/pull/11314) and this will, most likely,
fix your problem.
On Friday, December 4, 2020 at 8:18:11 a.m. UTC-5
Not here, but it other functions it would be very useful to be able to map
back to the owning particle.
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. When the maximum displacement of a
On 12/3/20 4:13 PM, shahab.g...@gmail.com wrote:
I want to iterate through all the particles in each iteration of my solver and
update some of the properties. The problem is iterating through particles
using particle_handler() is rather computationally expensive. I am looking for
a way to
Thanks for the reply.
I want to iterate through all the particles in each iteration of my solver
and update some of the properties. The problem is iterating through
particles using particle_handler() is rather computationally expensive. I
am looking for a way to update the properties without
On 12/3/20 1:19 PM, shahab.g...@gmail.com wrote:
Can you please write an example of accessing memory pool handles, iterating
them and converting the handles to particle properties?
The way we think about it is that the MemoryPool stores the data in some way
that should not be of any concern
Hi,
Can you please write an example of accessing memory pool handles, iterating
them and converting the handles to particle properties?
Thanks in advance.
Best regards,
Shahab
On Monday, October 19, 2020 at 10:57:26 PM UTC-4 Wolfgang Bangerth wrote:
> On 10/19/20 9:03 AM, blais...@gmail.com
On 10/19/20 9:03 AM, blais...@gmail.com wrote:
I am not sur if I fully understand the memory structure of the Property Pool
(or at least I am still confused by it).
If I understand correctly, the properties of all the particles are stored in a
single Handle array and the get_properties of a
I am not sur if I fully understand the memory structure of the Property
Pool (or at least I am still confused by it).
If I understand correctly, the properties of all the particles are stored
in a single Handle array and the get_properties of a single particle
returns an array view pointing to
On 10/19/20 4:58 AM, blais...@gmail.com wrote:
The issue is that this code is being called a lot (in our case every
iteration, so 100k to 10M times) and each iteration is very fast (1k iteration
is a second or so). Consequently, we've had some severe issue when timing in
parallel.
If nothing
The issue is that this code is being called a lot (in our case every
iteration, so 100k to 10M times) and each iteration is very fast (1k
iteration is a second or so). Consequently, we've had some severe issue
when timing in parallel.
If nothing is wrong with the code I guess what I am seeing
On 10/17/20 3:50 PM, blais...@gmail.com wrote:
Maybe it is callgrind that is playing tricks on me.
Here is the code :
for (auto particle = particle_handler.begin();
particle != particle_handler.end();
++particle)
{
// Getting properties of particle as local variable
auto particle_properties =
Maybe it is callgrind that is playing tricks on me.
Here is the code :
for (auto particle = particle_handler.begin();
particle != particle_handler.end();
++particle)
{
// Getting properties of particle as local variable
auto particle_properties = particle->get_properties();
// Reinitializing
I was wondering if there was a more optimal way to do this? I have profiled it
with callgrind and it seems that getting the properties array view from the
particle can be really expensive.
Since what we want to achieve is just to set one of these properties to zero,
I was wondering if there
Dear all,
I hope you are well :).
We are currently facing a weird bottle neck. There are some operation which
require us to set a particle property to zero and I think we are doing
something which is not optimal at all. Right now, we loop over the
particles, then we get the properties array
15 matches
Mail list logo
