[sage-devel] Re: unexpected equality

2016-09-19 Thread Ralf Stephan
On Sunday, September 18, 2016 at 11:27:17 PM UTC+2, rjf wrote: > > looks to me like you should use some kind of decision procedure that gets > the right answer. > Doesn't it boil down to where functions have rational or algebraic versus irrational or transcendental values? -- You received this

[sage-devel] Re: unexpected equality

2016-09-18 Thread rjf
looks to me like you should use some kind of decision procedure that gets the right answer. Apparently you are using some part of maxima that does numerical evaluation, which part is inappropriate for this use. maybe is(equal(sin(1+2^-200),sin(1))); which returns true. Actually, I'd call that a b

Re: [sage-devel] Re: unexpected equality

2016-09-17 Thread Vincent Delecroix
Define serious work. On 17 September 2016 at 14:53, Ralf Stephan wrote: > In other words your example was correctly determined as undecidable > in the default domain CIF but Maxima then said the relation is true so > __nonzero__ took that. > > sage: from sage.symbolic.relation import test_relatio

[sage-devel] Re: unexpected equality

2016-09-17 Thread Ralf Stephan
In other words your example was correctly determined as undecidable in the default domain CIF but Maxima then said the relation is true so __nonzero__ took that. sage: from sage.symbolic.relation import test_relation_maxima sage: test_relation_maxima(sin(1 + 2^-200) == sin(1)) True This means fo

[sage-devel] Re: unexpected equality

2016-09-17 Thread Ralf Stephan
On Saturday, September 17, 2016 at 1:48:14 PM UTC+2, vdelecroix wrote: > > Is there anything reliable about __nonzero__ for expressions? > Define expression. For any type there is likely a performance tradeoff. sage: (sin(1 + 2^-100) == sin(1)).test_relation(domain=CIF) NotImplemented sage: (s