-
Remove ctools::time_reference constant and handle the time reference for MET either by using the time reference from the input observation, or by adding a hidden "mjdref" parameter. The following tools transparently use the time reference of the input observation: * ctselect (apply time reference of each input observation) * ctbin (apply time reference of first input observation) * csobsselect (apply time reference of each input observation) A "mjdref" parameter was added the following tools: * ctobssim * cslightcrv * cspull * csviscube * csobsdef
-
Removed dynamic scheduling as it introduces a small amount of overhead (it was only done so that the observations would be analyzed in numerical order) Added caching of sky directions for each pixel to prevent the need to re-convert the positions from index for each observation. Fill cached sky positions with RA,Dec values to prevent need to convert between galactic->celestial every time the distance is compute a distance from an observation ROI.
-
Updated headers in log file to reflect what is actually going on. Changed omp scheduling to 'dynamic' so each observation is filled sequentially.
-
Finalized a workaround to the python wrapper issue that caused the 'ctbin::run()' method to crash.
-
Added check on whether observation is null or a CountsCube, which was done automatically before when calling 'next_unbinned_observation', but needs to be done explicitly now.
-
Added critical region when incrementing the bins of the counts cube. This didn't impact the computation time, but may improve the reliability of filling the cube if the same bin is being filled by two different observations.
-
Parallelized computation over different observations.
-
The ctobservation::first_unbinned_observation() and ctobservation::next_unbinned_observation() methods implement an unbinned CTA observation iterator. Using this iterator avoids code duplication and generates a uniform interface for tools to loop over CTA events lists.
-
Since the new GApplication logger methods are more compact than the old format the "logTerse()" etc. constructs have been replaced by the new logger methods. At the same time, the chattiness levels have been reviewed with the following behaviour: - TERSE: only headers - NORMAL: standard output, only main results or computations - EXPLICIT: detailed output - VERBOSE: verbose output, mainly for diagnostics