Make getMaxCheckInterval() of an EventDetector adaptable
Currently, when using an EventDetector, one has to provide a maxCheck parameter that is used to divide the propagation period into small parts in order to detect the event via root finding. For certain events (e.g. visibility), a small maxCheck setting (e.g. 1 min) is necessary to safely detect any occurring events. For longer propagation periods this can lead to long calculation times, which is not ideal for certain use-cases.
Taking into account, that it may be possible to roughly know when certain events occur (or better, when no event is expected), the search algorithm could be improved by using larger check periods at times no event is expected, while reducing the check period around expected event times. The EventDetector implementation could give a hint for this, making the whole search adaptive to the current state of the propagation.
(from redmine: issue id 87, created on 2012-04-02, closed on 2012-04-02)