Exceptions and Warnings¶
Exceptions¶
Errors derive from Exception or another custom error. Custom errors are only needed if standard errors, for example ValueError or TypeError, are not accurate descriptions of the cause for the error.
Error when parsing a docstring. |
|
Error due to perfect prediction in discrete models |
|
Error locating the X13 binary |
|
Error when running modes using X13 |
Warnings¶
Warnings derive from either an existing warning or another custom
warning, and are often accompanied by a string using the format
warning_name_doc that services as a generic message to use when the
warning is raised.
Unexpected conditions when using X13 |
|
Resource not deleted |
|
Non-fatal import error |
|
Base internal Warning class to simplify end-user filtering |
|
Nonlinear optimizer failed to converge to a unique solution |
|
Attempting to write to a read-only cached value |
|
Iteration limit reached without convergence |
|
Test not applicable to model |
|
Non-fatal function non-implementation |
|
Function output contains atypical values |
|
Variables are not compliant with required domain constraints |
|
Non-fatal out-of-range value given |
|
Unexpected condition encountered during estimation |
|
Non-fatal matrix inversion affects output results |
|
Issue occurred when performing hypothesis test |
|
Table granularity and limits restrict interpolation |
|
Numerical implementation affects precision |
|
Non-fatal model specification issue |
|
Hessian noninvertible and standard errors unavailable |
|
Variables are highly collinear |