Add support for TimeRange to RTML and the web UI. This will cause a point rev to RTML, and documentation changes. [edit] This will use the existing RTML TImeRange which maps to the Plan earliest/latest/fixed-time parameters. This will give the most flexibility.



At some later date (see SCHEDULER-696) we'll reorganize RTML, but only after exhaustive input from users, particularly with regard to time series.

This is done now, as part of SCHEDULER-691

OK, the time range controls are already in the new ACP web UI Photometry form. See SCHEDULER-691.

Rather than use the new TimeRange constraint, this will use the existing TimeRange elements of RTML 2.3, and the earliest/latest provisions in Plans that have been designed in from the outset. These are more flexible. The TImeRange constraint was a special purpose addition for AAVSO BSM project.  WIll edit the task description accordingly.

Results from the new TimeRange constraint