We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We should provide a detailed interface for symbolic relations:
bool(rel)
(not)(LHS-RHS).is_trivial_zero()
satisfiable(rel)
(Yes,example)/No/Undecidable/NotImplemented
solve(rel)
satisfiable=Yes
is(rel)
True
False
NotImplementedError
ex.is_zero(simplify=False)
bool(ex==0)
ex.is_zero(simplify=True)
prove(rel)
Tickets:
ex.__nonzero__
satisfiable()
See also https://trac.sagemath.org/wiki/symbolics/nonzero
CC: @videlec @slel
Component: symbolics
Issue created by migration from https://trac.sagemath.org/ticket/19162
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We should provide a detailed interface for symbolic relations:
bool(rel)
equivalent to(not)(LHS-RHS).is_trivial_zero()
for ==,!= ; and for <, >, <=, >= the result follows alpha order of lhs and rhssatisfiable(rel)
returning(Yes,example)/No/Undecidable/NotImplemented
solve(rel)
in case ofsatisfiable=Yes
returning the full solution setis(rel)
attempting simplification/proof, returningTrue
/False
, throwingNotImplementedError
ex.is_zero(simplify=False)
(default) calling the fastbool(ex==0)
(Fix usage of symbolic comparison in several places #24992)ex.is_zero(simplify=True)
attempting simplification/proof (Fix usage of symbolic comparison in several places #24992)prove(rel)
showing more or less steps of simplification (which is out of reach for the moment)Tickets:
ex.__nonzero__
into resp. member functionssatisfiable()
See also https://trac.sagemath.org/wiki/symbolics/nonzero
CC: @videlec @slel
Component: symbolics
Issue created by migration from https://trac.sagemath.org/ticket/19162
The text was updated successfully, but these errors were encountered: