I am using a very simple fly-by of two stars. When plotting their orbits, the periastron should be their closest approach, if I am not mistaken. However, when adding "periastron=True" the line now appears nowhere near the very obvious periastron of the encounter.
It now appears to point to the COM of that snapshot (as this changes when plotting different snapshots), even though the orbit of the perturbing star is plotted correctly, so the periastron distance can be calculated and T (time of periastron) is still given properly as well.
This used to provide a plot showing the periastron, which in this case would be ~11-12 au. However the periastron line does not connect with this.
Adding sim.move_to_com() just moves the encounter and then the periastron line is clearly pointing to the COM (which is then at 0,0,0). This seems to be a recent change as it used to be plotted properly
I am using a very simple fly-by of two stars. When plotting their orbits, the periastron should be their closest approach, if I am not mistaken. However, when adding "periastron=True" the line now appears nowhere near the very obvious periastron of the encounter.
It now appears to point to the COM of that snapshot (as this changes when plotting different snapshots), even though the orbit of the perturbing star is plotted correctly, so the periastron distance can be calculated and T (time of periastron) is still given properly as well.
This used to provide a plot showing the periastron, which in this case would be ~11-12 au. However the periastron line does not connect with this.
Adding sim.move_to_com() just moves the encounter and then the periastron line is clearly pointing to the COM (which is then at 0,0,0). This seems to be a recent change as it used to be plotted properly