← Back to team overview

yade-dev team mailing list archive

Re: Energy tracing vs. multithread?

 

> Thank you, I'll look at this template.
> I realize using the FOREACH macro by default everytime we have a loop is 
> perhaps not a good idea. What about this loop in GSTimeStepper, with 
> stiffnesses a class member?
> 
> FOREACH(const shared_ptr<Interaction>& contact, *rb->interactions){
> [...]
> stiffnesses [contact->getId1()]+=diag_stiffness;
> stiffnesses [contact->getId2()]+=diag_stiffness;

What about it...? GSTS is not run in parallel normally. Did I miss the
point?





Follow ups

References