-
The fixed number of iterations has not been correctly taken into account in the convergence testing. If alternatively the integration precision was reached, the code stopped anyways.
-
…ethod will sort these boundaries and returns the sum of the integral over all boundaries. This allows easy splitting of an integration range into two pieces by adding an internal node.
-
Before, 0 was returned in case of inaccurate results. This is bad. We want some result, even if it's not accurate.
-
A new integrator has been implemented together with a unit test.
-
… integration methods. Any warning occuring during integration are now stored in an internal data member string that is accessible using the message() method. If a warning or error occured, the isvalid() method will return false. Otherwise, and if the integration result is valid, the isvalid() method returns true.
-
The coding and design conventions (CDC) document was also updated.
-
Add GChatter argument to print() method. The print() method now takes an argument of type GChatter to control the chattiness of the output in a homogenous manner. Pass NORMAL chatter level in __str__ method. Add chatter argument to print() methods. Use GLog::chatter() method to control the chattiness of the log stream operator. Add chatter() methods and provide member access through const references. Add chatter() methods, provide member access through const references, and declare one liners as inline methods. The chatter() methods control the new m_chatter attribute that is used to control the chattiness of the object's print() methods. name() and version() methods return const references. logFileOpen() method now sets the chattiness from the applications's chatter parameter, and name() and version() methods now return a const reference.
-
The ostream and GLog functions are not defined at the GBase level.
-
For some reasons an empty exception was thrown in case of convergence problems by the romb() method. I guess this was done for debugging purposes, but this should not be the general behaviour of the method. I thus commented the throw directiv so that just warnings are issued but the code continues working.
