Deals with the possible exceptions in py4vasp.
The design goal is that all foreseeable exceptions in py4vasp issue an exception of the Py4VaspException class. Any other kind of exception would indicate a bug in the code. If possible the part standard users interact with should not raise any exception, but should give advice on how to overcome the issue.
DataMismatch
()
The data provided is not suitable to be processed by the called function.
FileAccessError
()
Exception raised when error occurs during accessing the HDF5 file.
IncorrectUsage
()
The user provided input is not suitable for processing
ModuleNotInstalled
()
Exception raised when a functionality is used that relies on an optional
dependency of py4vasp but that dependency is not installed.
NoData
()
Exception raised when certain data is not present, because the corresponding
INCAR flags have not been set.
NotImplemented
()
Exception raised when a function is called that is not implemented.
OutdatedVaspVersion
()
Exception raised when the py4vasp features used are not available in the
used version of Vasp.
ParserError
()
Exception raised when the parser encounters an error.
Py4VaspError
()
Base class for all exceptions raised by py4vasp
RefinementError
()
When refining the raw dataclass into the class handling e.g. reading and
plotting of the data an error occurred
StopExecution
()
Exception raised when an error occurred in the user interface. This prevents
further cells from being executed.