-
All likelihood ctools now derive from the ctlikelihood base class. This avoids code duplication and provides all likelihood tools with a uniform interface.
-
The GCTAEventCube::map() method has been renamed to GCTAEventCube::counts() (#1789)
-
The publish parameter has been added to the following tools: - ctbin - ctbkgcube - ctcubemask - ctexpcube - ctmodel - ctskymap - cttsmap
-
Although the get_obs() method was put back, ctmodel used the dummy cube (which consisted of a single pixel) instead of a cube defined from the input parameters. This was due to an internal change of the logic, that now has been corrected for.
-
Without the energy margin, roundoff errors may lead to the exclusion of the energy bin in case that a single energy bin is used.
-
…d in observation ebounds. Also added some improvements to csspec.
-
…lso modified consistently, csresmap can now also take two maps (cnt and model) as input and compute the residuals directly. The algorithm parameter has been made unhidden
-
…(see #1360 for details).
-
…)-function of individual ctools
-
…d scave() methods to ctool interface. Add read_ahead() method to handle reading of task parameters at the beginning of the task execution. Remove all m_read_ahead members from the derived classes.
-
…esponse for all CTA observation in the container that have not yet a response using the task parameters.
-
ctmodel now always produces a single model cube on output. There are two important input parameters: "infile" and "obsfile". "infile" specifies a counts or model cube that is used to define the binning of the model cube. The functionnality for this parameter is as before. If "infile=NONE", the cube will be defined according to task parameters that specify the spatial and the energy binning. The "obsfile" parameter is new and allows specifying the observation definition for which the model cube should be computed. If an event list or a counts cube is presented, the pointing and Good Time Intervals will be extracted from the FITS file header. If an observation definition XML file is presented, ctmodel will now loop over all CTA observations in the file and add the model values to the model cube. If no response information is associated to the "obsfile" (which is typically the case for event lists or counts cubes), the "caldb" and "irf" parameters will be used to identify the response.