Open rwst opened 6 years ago
Description changed:
---
+++
@@ -1 +1 @@
-Evaluation of `elliptic_f(asin((-b<sup>(1/3)*(c+d*x)</sup>(1/3)+(b*c-a*d)<sup>(1/3)*(1+sqrt(3)))/(-b</sup>(1/3)*(c+d*x)<sup>(1/3)+(b*c-a*d)</sup>(1/3)*(1-sqrt(3)))),-7+4*sqrt(3))` by Sage takes surprising 9 sec on a fast system, although no computation should be involved (in==out). Reason is the elliptic eval function tries to prove that `asin...` is nonzero. For the general problem and solution see https://trac.sagemath.org/wiki/symbolics/nonzero
+Evaluation of e.g. `elliptic_f(asin((-b<sup>(1/3)*(c+d*x)</sup>(1/3)+(b*c-a*d)<sup>(1/3)*(1+sqrt(3)))/(-b</sup>(1/3)*(c+d*x)<sup>(1/3)+(b*c-a*d)</sup>(1/3)*(1-sqrt(3)))),-7+4*sqrt(3))` by Sage takes surprising 9 sec on a fast system, although no computation should be involved (in==out). Reason is the elliptic eval function tries to prove that `asin...` is nonzero. For the general problem and solution see https://trac.sagemath.org/wiki/symbolics/nonzero
Author: Ralf Stephan
Branch pushed to git repo; I updated commit sha1. New commits:
c0df369 | 25101: bypass Expression.__nonzero__ |
update milestone 8.3 -> 8.4
red branch => needs_work
Setting new milestone based on a cursory review of ticket status, priority, and last modification date.
Setting a new milestone for this ticket based on a cursory review.
Evaluation of e.g.
elliptic_f(asin((-b<sup>(1/3)*(c+d*x)</sup>(1/3)+(b*c-a*d)<sup>(1/3)*(1+sqrt(3)))/(-b</sup>(1/3)*(c+d*x)<sup>(1/3)+(b*c-a*d)</sup>(1/3)*(1-sqrt(3)))),-7+4*sqrt(3))
by Sage takes surprising 9 sec on a fast system, although no computation should be involved (in==out). Reason is the elliptic eval function tries to prove thatasin...
is nonzero. For the general problem and solution see https://trac.sagemath.org/wiki/symbolics/nonzeroComponent: performance
Author: Ralf Stephan
Branch/Commit: u/rws/slow_trivial_elliptic_f_evaluation @
c0df369
Issue created by migration from https://trac.sagemath.org/ticket/25101