AngouriMath
answered
Field
Summary
The integrals already answered under the settings in force, so that the same question
is not worked out again.
is not worked out again.
Remarks
solvers overlap — substitution, partial fractions, splitting a sum and integration by
parts each decompose the integrand differently and produce pieces that coincide — and
across calls
rewritten candidate it generates. Traced on
elementary antiderivative and so runs the search to exhaustion, that is 562
top-level calls for 3 distinct integrands, one of them asked 500 times; on
repetition is: discarding them at the end of each top-level call leaves the 562 to be
paid in full. Measured on those three integrands, keeping them takes a
cold
https://github.com/asc-community/AngouriMath/issues/1156
Codomain decides whether the logarithms carry an
is scoped to a flow rather than to a thread, so "the settings have not changed" is not
something a per-thread cache can assume. SettingsState answers it
exactly, by comparing what every setting reads as rather than by counting changes —
which matters, because the library opens and closes thousands of balanced scopes while
simplifying and a change count is therefore never still.
asked (AnsweringTheQuestionAsked), or it and one or two levels below it
(AnsweringTheQuestionAskedOrOneBelow,
AnsweringTheQuestionAskedOrTwoBelow), and decline the same integrand
deeper, so a
shallower one. Held without the scope it was served there:
declined inside another rule's search, then asked for directly and declined from the
cache in two milliseconds. And held with the top told only from the rest, a decline at
depth three was served at depth two: the search for
again at depth two, and the integral was declined. The key carries the depth as far as
a scope reaches, ScopeDepth, and a lookup takes a decline only from its
own depth and an answer from any, since an antiderivative that was found is right
wherever it is asked for.
Angouri © 2019-2023 · Project's repo · Site's repo · Octicons · Transparency · 4862 pages online