Moved some sections to alternative to keep proposal short
@@ -113,15 +113,6 @@ a user would execute the following code::
time_step = 5.0 * u.min
time_bins = constant_time_bins(time_start, time_stop, time_step)
-Alternatively, we could rely on ``astropy.timeseries`` if we force the dependency to astropy v>3.2.
-This would look like::
-
- from astropy.timeseries import BinnedTimeSeries
- times = BinnedTimeSeries(time_bin_start="2006-07-29 20:00:00.000",
- time_bin_size=5 * u.min)
- print(times.time_bin_start)
- print(times.time_bin_end)
-
Data reduction
--------------
@@ -177,38 +168,34 @@ The results are returned as a ``gammapy.time.LightCurve`` instance (the current
container class for light curves) that, so far, essentially holds the integrated flux +
errors and the time_min/time_max of each time bin. There are many other quantities
which could be stored, such as the energy range of the flux, the number of excess
-events in the time bin considered, etc. In particular, for lightcurves with spectral
-variability studies, columns for other model parameters and associated errors would
-be necessary.
+events in the time bin considered, etc.
The current container class already provides some methods to study variability, such as
chi-square test, fractional variance estimation. But these methods are more general
than the specific case of gammapy.
-This container is based on an ``astropy.table.Table`` object. It could therefore
-be improved by using the ``astropy_timeseries.BinnedTimeSeries`` object which
-itself inherits from ``Table`` and provides support for row selection with time,
-rebinning and more complex methods for detailed timing studies such as Lomb-Scargle
-periodograms.
-
Discussion / Alternatives
=========================
-The outline described above would require changes in the
-`gammapy.data.data_store`, `gammapy.time.lightcurve` and
-`gammapy.scripts.SpectrumAnalysisIACT` modules. The `gammapy.background` and
-`gammapy.spectrum` modules would remain unchanged.
-
-Instead of preparing new `~gammapy.data.ObservationList` for each time bin,
-which leaves the filtering/selection of the events and IRFs to the
-`LightCurveEstimator` class, we could also do the filtering/selection in the
-`~gammapy.background` and `~gammapy.spectrum` modules by means of the GTI table
-(`good time interval`_) already present in the
-`gammapy.data.DataStoreObservation` object. At the moment this table is not used
-at all. A drawback of this approach would be the necessity of changes in the
-`~gammapy.background` and `~gammapy.spectrum` modules. Even though i have not
-worked out any specifics of this approach yet, i think this would be a less
-elegant way.
+Time bins
+^^^^^^^^^
+
+To work with time bins, we could also rely on ``astropy.timeseries`` if we force the dependency to astropy v>3.2.
+This would look like::
+
+ from astropy.timeseries import BinnedTimeSeries
+ times = BinnedTimeSeries(time_bin_start="2006-07-29 20:00:00.000",
+ time_bin_size=5 * u.min)
+ print(times.time_bin_start)
+ print(times.time_bin_end)
+
+Lightcurve
+^^^^^^^^^^
+The ``Lightcurve`` contains an ``astropy.table.Table`` object. It could
+be improved by using the ``astropy_timeseries.BinnedTimeSeries`` object which
+itself inherits from ``QTable`` and provides support for row selection with time,
+rebinning and more complex methods for detailed timing studies such as Lomb-Scargle
+periodograms.
Task list
=========
