Updates:
Status: Started
Comment #3 on issue 1323 by mattpap: integrate(1/sqrt(16 + 4*x**2), x) fails
http://code.google.com/p/sympy/issues/detail?id=1323
Yep, Poly._decompose() shouldn't get algebraic functions. The problem is in
putting
expressions into a normal form, especially expre
Comment #10 on issue 1321 by fredrik.johansson: trigonometric functions of
floating-point numbers should return floating-point numbers
http://code.google.com/p/sympy/issues/detail?id=1321
Functions should automatically evalf when passed Real instances (or
Real+Real*I).
That's all, really.
-
Updates:
Cc: mattpap
Comment #2 on issue 1323 by ondrej.certik: integrate(1/sqrt(16 + 4*x**2),
x) fails
http://code.google.com/p/sympy/issues/detail?id=1323
I think the decompose should not get sqrt(4+x**2) in the first place, e.g.
there is
some mistake in the algorithm. Or maybe I a
Comment #1 on issue 1323 by plaes800: integrate(1/sqrt(16 + 4*x**2), x)
fails
http://code.google.com/p/sympy/issues/detail?id=1323
Testcase:
Poly._decompose(sqrt(4 + x**2), x)
So, how should Poly._decompose manage it?
--
You received this message because you are listed in the owner
or CC f
Comment #9 on issue 1321 by Vinzent.Steinberg: trigonometric functions of
floating-point numbers should return floating-point numbers
http://code.google.com/p/sympy/issues/detail?id=1321
+1 (sorry for annoying you, "other users")
The precision should be in my opinion 15 (or 16) digits (mach
Comment #8 on issue 1321 by ondrej.certik: trigonometric functions of
floating-point numbers should return floating-point numbers
http://code.google.com/p/sympy/issues/detail?id=1321
What I meant is that
0.1 should be converted to Real first. We can discuss with what precision,
I suggest
th
Status: Accepted
Owner:
Labels: Type-Defect Priority-Medium
New issue 1323 by Vinzent.Steinberg: integrate(1/sqrt(16 + 4*x**2), x) fails
http://code.google.com/p/sympy/issues/detail?id=1323
>>> integrate(1/sqrt(16 + 4*x**2), x)
Traceback (most recent call last):
File "", line 2, in
F
Comment #7 on issue 1321 by fabian.seoane: trigonometric functions of
floating-point numbers should return floating-point numbers
http://code.google.com/p/sympy/issues/detail?id=1321
I think we should use machine precision for the result, so the output of
sin(0.1)
would simply be
In [1]: fl
Updates:
Cc: fredrik.johansson
Comment #6 on issue 1321 by Vinzent.Steinberg: trigonometric functions of
floating-point numbers should return floating-point numbers
http://code.google.com/p/sympy/issues/detail?id=1321
I think we should always use full float precision (15 or 16 digits)
Comment #5 on issue 1321 by fabian.seoane: trigonometric functions of
floating-point numbers should return floating-point numbers
http://code.google.com/p/sympy/issues/detail?id=1321
response to #2 and #4:
sympy already does convert 0.1 to 0.1000, so you'll inevitably
get
roundi
Updates:
Summary: solve(Eq(cos(x), sin(x)), x) should be atan(1)
Labels: -Type-Defect Type-Enhancement
Comment #11 on issue 1120 by Vinzent.Steinberg: solve(Eq(cos(x), sin(x)),
x) should be atan(1)
http://code.google.com/p/sympy/issues/detail?id=1120
(No comment was entered for
Comment #4 on issue 1321 by Vinzent.Steinberg: trigonometric functions of
floating-point numbers should return floating-point numbers
http://code.google.com/p/sympy/issues/detail?id=1321
Interpreting sin('0.1') as "about 0.1" is ok, but for sin(0.1) it's wrong,
because
sympy can't distinguis
12 matches
Mail list logo
