In order to understand and make productive use of a lack of success, it is necessary to precisely specify the reason for and nature of the lack of success. The SZS no-success ontology provides status values for describing the reasons. Note that no-success is not the same as failure: failure means that the software has completed its attempt to process the logical data and could not establish a success ontology value. In contrast, no-success might be because the software is still running, or that it has not yet even started processing the logical data.
NoSuccess (NOS):
The logical data has not been processed successfully (yet).
Unknown (UNK):
A success value for the ATP problem has never been established.
Stopped (STP):
Software attempted to process the data, and stopped without a success status.
InProgress (INP):
Software is still running.
NotTried (NTT):
Software has not tried to process the data.
NotTriedYet (NTY):
Software has not tried to process the data yet, but might in the future.
Error (ERR):
Software stopped due to an error.
Forced (FOR):
Software was forced to stop by an external force.
GaveUp (GUP):
Software gave up of its own accord.
OSError (OSE):
Software stopped due to an operating system error.
InputError (INE):
Software stopped due to an input error.
SyntaxError (SYE):
Software stopped due to an input syntax error.
SemanticError (SEE):
Software stopped due to an input semantic error.
TypeError (TYE):
Software stopped due to an input type error (for typed logical data).
Unsemantic (USM):
The semantics makes no sense (for semantics specifications).
UsageError (USE):
Software stopped due to an ATP system usage error.
User (USR):
Software was forced to stop by the user.
ResourceOut (RSO):
Software stopped because some resource ran out.
Timeout (TMO):
Software stopped because a time limit ran out.
CPUTimeout (CTO):
Software stopped because the CPU time limit ran out.
WCTimeout (WTO):
Software stopped because the wall clock time limit ran out.
MemoryOut (MMO):
Software stopped because the memory limit ran out.
Incomplete (INC):
Software gave up because it's incomplete.
Inappropriate (IAP):
Software gave up because it cannot process this type of data.
Incorrect (ICT):
Software gave an incorrect answer.
Assumed (ASS(U,S)):
The success ontology value S has been assumed because the actual value is unknown for the no-success ontology reason U. U is taken from the subontology starting at Unknown in the no-success ontology.
Open (OPN):
A success value for the abstract problem has never been established.
NotVerified (NVE):
The solution output has not been verified.
FailedVerified (FVE):
The solution output failed verification.