AngouriMath

Symbolics for .NET


Table of contents

AngouriMath

Navigation
Home Quick start Wiki Almanac Research What's new Try Use Angouri.org GitHub Report a bug Donate Contacts

BudgetOutcome

← Back to list of classes

Description

Summary

What a bounded computation spent, and what stopped it if anything did.

Remarks

The point of it is that Reason survives. A computation that gives up
on a resource and a computation that concluded there is nothing to find both hand the
caller nothing, and the library has had no way to tell those apart —
#896 is that
gap reported as a defect. An outcome is the "because" that goes with the shrug.
 It does not say what to do next, and deliberately makes no attempt to. Which ceiling
fired was measured against whether the fall-through then terminates, on
#896's own
corpus, and the same ceiling appears on both sides: two systems the fall-through
solves in seconds and one it cannot finish at all all decline on the quotient
dimension. So this is a report, not a routing decision.

Parameter "Where"

Which computation this is about, for a reader — not a stable identifier to switch on.

Parameter "Reason"

What stopped the computation — a ceiling it reached, or a shape it could not work
with — or null where it ran to its own end. Named rather than
enumerated because most of these belong to one algorithm and mean nothing outside it.

Parameter "Steps"

Units of work charged.

Parameter "Elapsed"

How long it took, whether or not a clock bounded it.

Parameter "IsDeterministic"

Whether this outcome is a function of the input alone. False exactly when a wall-clock
ceiling is what stopped it, in which case a faster machine would have got further.

Members

























Angouri © 2019-2023 · Project's repo · Site's repo · Octicons · Transparency · 4378 pages online