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.

ParseError	Error when parsing a docstring.
PerfectSeparationError	Error due to perfect prediction in discrete models
X13NotFoundError	Error locating the X13 binary
X13Error	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.

X13Warning	Unexpected conditions when using X13
IOWarning	Resource not deleted
ModuleUnavailableWarning	Non-fatal import error
ModelWarning	Base internal Warning class to simplify end-user filtering
ConvergenceWarning	Nonlinear optimizer failed to converge to a unique solution
CacheWriteWarning	Attempting to write to a read-only cached value
IterationLimitWarning	Iteration limit reached without convergence
InvalidTestWarning	Test not applicable to model
NotImplementedWarning	Non-fatal function non-implementation
OutputWarning	Function output contains atypical values
DomainWarning	Variables are not compliant with required domain constraints
ValueWarning	Non-fatal out-of-range value given
EstimationWarning	Unexpected condition encountered during estimation
SingularMatrixWarning	Non-fatal matrix inversion affects output results
HypothesisTestWarning	Issue occurred when performing hypothesis test
InterpolationWarning	Table granularity and limits restrict interpolation
PrecisionWarning	Numerical implementation affects precision
SpecificationWarning	Non-fatal model specification issue
HessianInversionWarning	Hessian noninvertible and standard errors unavailable
CollinearityWarning	Variables are highly collinear