Closed MilevaE closed 6 years ago
Thanks for catching that. I just pushed an update which should fix the issue. Feel free to reopen the issue if that's not the case!
Hi Hanno,
thanks a lot for your super-fast answer. I upgraded and works partially.
Now seems that both values sim.t
and lastcollision
have different accuracy, so they don't satisfy the condition if p.lastcollision == sim.t:
here what I obtain:
sim.t = 695.726
lastcollision = 695.725297086
So, the collision is caught, but I still can not identify which particles were involved.
Thanks a lot for your help
That's expected as Mercurius takes many small timesteps during close encounters. You'd need to add some extra logic in your collision routine to say if the collision happened within the last timestep.
ok! thanks a lot!
Hi,
I'm having problems with the
lastcolision
function. I have defined an integration like that:So, what I'm doing here is to define my own collision resolve rutine, after a collision exception is caught by the exception. My problem is that depending if I use IAS15 or Mercurius,
lastcollision
is not working. In both the exception is caught, so I guess that the collision happens and both integrators "see" it, but using Mercurius,lastcollision
is 0 instead the time when the collision happened.Any idea why I could be having this problem? suggestions to solve it?
I would prefer use Mercurius because is much faster than IAS15..
best, Mil