Default max check interval leads to missed nodes crossing for eccentric orbits
The NodeDetector class has a builtin default max check interval equal to
T/3, where T is the Keplerian period of the orbit.
This works well for near circular orbits as the nodes have roughly a T/2 separation (the max check interval is smaller, hence
no pairs of node can appear between two checks and no nodes are missed).
This is not true anymore for eccentric orbits. If for example an highly eccentric orbit has a perigee argument of 270 degrees, then the part of the orbit between a descending node and the next ascending node will be near the perigee and the time to go from descending to ascending node will be much smaller than the time to go from ascending to next descending node. It can happen than the two nodes are less than T/3 and a pair of nodes crossing may be missed by the detector.
(from redmine: issue id 158, created on 2013-12-24, closed on 2015-01-12)