If one wanted to observe a target early, say within some air mass range, then again late within the same air mass range, it would be great to allow Monitor Mode to reschedule after less than a whole day.

This turned out to be a bad idea. Consider a Plan that becomes eligible early in the evening, but does not actually run until much later. As it is, the current logic for Monitor Interval = 1 day resubmits the Plan at the beginning of the next night. But if we were to change the meaning of the monitor interval into "resubmit xx time after the last time it ran" that would cause the plan to be resubmitted at the same "much later" time at which it actually ran the previous night.



The original impetus for this was to allow a Plan to run more than once a night. Bottom line: Submit two Plans with appropriate constraints or link a couple of Observations with appropriate Time After and Time Tolerance.

Needs a change to the database schema. The MonitorInterval column needs to change from INTEGER to SINGLE (FLOAT). Also, the check for Monitor resubmit needs to go into the Schedule pass. And this forces our hand in making the logic into a stored query. Linked this issue to SCHEDULER-287.