Package org.orekit.estimation.measurements.generation

Class ContinuousScheduler<T extends ObservedMeasurement<T>>

  • Type Parameters:
    T - the type of the measurement
    All Implemented Interfaces:
    Scheduler<T>
    public class ContinuousScheduler<T extends ObservedMeasurement<T>>
extends AbstractScheduler<T>
    Scheduler generating measurements sequences continuously.

    Continuous schedulers continuously generate measurements following a repetitive pattern. The repetitive pattern can be either a continuous stream of measurements separated by a constant step (for example one measurement every 60s), or several sequences of measurements at high rate up to a maximum number, with a rest period between sequences (for example sequences of up to 256 measurements every 100ms with 300s between each sequence).

    Since:
    9.3
    Author:
    Luc Maisonobe

    • Constructor Detail

      • ContinuousScheduler

        public ContinuousScheduler​(MeasurementBuilder<T> builder,
                           DatesSelector selector)
        Simple constructor.

        BEWARE! Dates selectors often store internally the last selected dates, so they are not reusable across several instances. A separate selector should be used for each scheduler.

        This constructor calls ContinuousScheduler(MeasurementBuilder, DatesSelector, Predicate) whith the predicate set to accept all generated measurements.

        Parameters:
        builder - builder for individual measurements
        selector - selector for dates (beware that selectors are generally not reusable across several instances, each selector should be dedicated to one scheduler

      • ContinuousScheduler

        public ContinuousScheduler​(MeasurementBuilder<T> builder,
                           DatesSelector selector,
                           Predicate<EstimatedMeasurementBase<T>> filter)
        Simple constructor.

        BEWARE! Dates selectors often store internally the last selected dates, so they are not reusable across several instances. A separate selector should be used for each scheduler.

        Parameters:
        builder - builder for individual measurements
        selector - selector for dates (beware that selectors are generally not reusable across several instances, each selector should be dedicated to one scheduler
        filter - predicate for a posteriori filtering of generated measurements (measurements are accepted if the predicates evaluates to true)
        Since:
        13.0