PyBADS 1.5.1

Changes since PyBADS 1.5.0.

Fixed

• Objective exceptions. Exceptions raised by the objective retain their original args. On Python 3.11 and later, a note identifies the point at which the exception was raised.
• Messages. The errors and warnings about a value or a noise SD that the objective returns, about the bounds and about the starting point say what is wrong, at which point or variables, and what is expected, and each error is printed once; failures that a run recovers from, such as a failed Cholesky decomposition while fitting the Gaussian process, are no longer logged as warnings. Without final samples, a noisy run reports the observation at its returned point. Messages no longer include prefixes such as bads:pbUnspecified or FunctionLogger:InvalidFuncValue.
• Documentation. Notebook launch and edit links point to their repository sources. The FAQ and API reference clarify noisy results with few or no final samples, timing and function logger return values. Building the documentation requires sphinx-book-theme 1.0 or newer.