geopulse.exceptions
Custom exception hierarchy for GeoPulse.
All GeoPulse exceptions inherit from GeoPulseError so users can
catch all of them with a single except clause.
Exceptions
Raised when a configuration file is invalid or missing. |
|
Raised when an iterative solver fails to converge. |
|
Raised when input data is malformed, missing, or has wrong units. |
|
Base exception for all GeoPulse errors. |
|
|
Raised for features that are in the roadmap but not yet coded. |
Raised when array shapes do not match the expected contract. |
- exception geopulse.exceptions.GeoPulseError[source]
Bases:
ExceptionBase exception for all GeoPulse errors.
- exception geopulse.exceptions.ConfigurationError[source]
Bases:
GeoPulseErrorRaised when a configuration file is invalid or missing.
- exception geopulse.exceptions.DataError[source]
Bases:
GeoPulseErrorRaised when input data is malformed, missing, or has wrong units.
- exception geopulse.exceptions.ShapeMismatchError[source]
Bases:
DataErrorRaised when array shapes do not match the expected contract.
- exception geopulse.exceptions.ConvergenceError[source]
Bases:
GeoPulseErrorRaised when an iterative solver fails to converge.
- exception geopulse.exceptions.NotImplementedYetError(feature, work_package='TBD')[source]
Bases:
GeoPulseErrorRaised for features that are in the roadmap but not yet coded.
Includes the work-package reference so users know when to expect it.