You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For simulations where the internal time-step is too large, the colliding particles will (at rare times) not flag the AMUSE collision stopping condition causing the integrator to break.
Depending on the internal timestep, "...Collision Detected..." is outputted. This isn't replicated with Hermite who detects the collision no matter the internal timestep.
My current fix is not too elegant, and is the following:
line 5 of Pairwise1PNPerturbation.h: I've added #include "StoppingConditions.h";
line 14 of Pairwise1PNPerturbation.h: I've added StoppingConditions m_StoppingCond;
line 14 of Pairwise1PNPerturbation.h: I've added bool m_ConditionsSet;
line 45 of Pairwise1PNPerturbation::Pairwise1PNPerturbation.cpp in the Pairwise1PNPerturbation::CalculateAccelerations functions: I've added m_ConditionsSet = m_StoppingCond.Check(model);
line 166 of EIHPerturbation.cpp in the EIH2dot5PNPerturbation::CalculateAccelerations functions: I've added m_ConditionsSet = m_StoppingCond.Check(model);
line 373 of EIHPerturbation.cpp in the EIH1PNPerturbation::CalculateAccelerations functions: I've added m_ConditionsSet = m_StoppingCond.Check(model);
I haven't tested the change in performance nor if it affects any of the physics (this I doubt. MY current changes results in amuse.support.exceptions.AmuseException: Unable to add a particle, because it was already part of this set.
Other solution is simply changing the collision radius.
The text was updated successfully, but these errors were encountered:
For simulations where the internal time-step is too large, the colliding particles will (at rare times) not flag the AMUSE collision stopping condition causing the integrator to break.
Small code to reproduce issue below:
Depending on the internal timestep, "...Collision Detected..." is outputted. This isn't replicated with Hermite who detects the collision no matter the internal timestep.
My current fix is not too elegant, and is the following:
line 5 of Pairwise1PNPerturbation.h: I've added
#include "StoppingConditions.h";
line 14 of Pairwise1PNPerturbation.h: I've added
StoppingConditions m_StoppingCond;
line 14 of Pairwise1PNPerturbation.h: I've added
bool m_ConditionsSet;
line 45 of Pairwise1PNPerturbation::Pairwise1PNPerturbation.cpp in the Pairwise1PNPerturbation::CalculateAccelerations functions: I've added
m_ConditionsSet = m_StoppingCond.Check(model);
line 166 of EIHPerturbation.cpp in the EIH2dot5PNPerturbation::CalculateAccelerations functions: I've added
m_ConditionsSet = m_StoppingCond.Check(model);
line 373 of EIHPerturbation.cpp in the EIH1PNPerturbation::CalculateAccelerations functions: I've added
m_ConditionsSet = m_StoppingCond.Check(model);
I haven't tested the change in performance nor if it affects any of the physics (this I doubt. MY current changes results in
amuse.support.exceptions.AmuseException: Unable to add a particle, because it was already part of this set
.Other solution is simply changing the collision radius.
The text was updated successfully, but these errors were encountered: