-
Fix all Npred integration precision to 1e-5 as this is needed for accurate results. Do not use m_eps for the integration precision anymore as each integrator may be optimized individually.
-
Deadtime correction was applied in npred() and npred_radial(), npred_elliptical() and npred_diffuse(). The latter three methods all call npred() at the end, which led to a double correction of the deadtime. This has been corrected now.
-
This reverts commit 7247c9a0b5f5976fb11206d4861f96d11f44a4c5.
-
The precision parameter allows setting the number of digits after the comma.
-
Conflicts: ChangeLog NEWS
-
Now, GCaldb only reads the CALDB environment variable when needed. This allows changing the CALDB environment variable during runtime. Rename GCaldb::dir to GCaldb::rootdir.
-
The gammalib::filepath combines a path name and a file name into a string. If the path name is empty, the file name is returned.
-
The method converts the selection strings to upper case before comparison.
-
Instead of passing a string providing the calibration database path, the GCTAObservation and GCTAResponse classes now take a GCaldb object. This allows for a more flexible handling and selection of response functions through passing the corresponding calibration database object. The rmffile member and method has become obsolete in GCTAResponse, so it was deleted. Now everything is handled by the GCTAEdisp class.
-
The GCaldb::filename method returns an absolute IRF filename based on a set of selection criteria. The selection criteria are still very simple, and a more sophisticated should be implemented in the futur. For the time being, the method does the job.
-
The results of the Python unit test were not correctly tracked due to some subtle problems related to the way how C++ code is called through the Python interface. A kluge has been found and added to GTestSuite.i to retrieve the Python test results and to propagate them to the C++ test suite, so now Python test results are also written into the XML file, and the Python tests signal failure in case that something goes wrong.
-
GTestSuite::run starts with creating a test case that collects the total time spent in a test and that also collects any failures of the individual test cases. Before, this test case was appended AFTER running the individual test cases, which led to an XML file out of order. Now the general test case is appended BEFORE running the test cases.