Open DaveWitteMorris opened 2 years ago
Giac also gives a wrong answer, but a different one:
sage: lim(D, x=0, algorithm="giac")
+Infinity
I think sage only shares its assumptions with maxima and pynac, so giac cannot know that m
is an integer. The answer +Infinity
is correct generically, but it is the wrong answer in the special case that we are interested in.
Sympy gives an error, instead of an answer:
sage: lim(D, x=0, algorithm="sympy")
<snip>
RuntimeError: indeterminate expression: 0 * infinity encountered.
Description changed:
---
+++
@@ -2,6 +2,7 @@
sage: m = var('m'); +sage: assume(m, 'integer') sage: with hold: ....: assume(cos((4pim+pi)/2) == 0) ....:
This is now tracked at maxima bug #4004
Changed upstream from Not yet reported upstream; Will do shortly. to Reported upstream. No feedback yet.
Description changed:
---
+++
@@ -1,3 +1,16 @@
+The following limit should obviously be `1`, but sagemath says it is `0`. This is a maxima bug that has been reported upstream.
+
+```
+sage: a = var("a")
+sage: assume(a == 0)
+sage: limit(a/x + 1, x=0)
+0
+```
+
+---
+
+Here is the original ticket description:
+
It is not difficult to see that the value of the following limit is `4*m + 1`. However, sagemath says the value is `0`:
Changed upstream from Reported upstream. No feedback yet. to Reported upstream. Developers acknowledge bug.
The following limit should obviously be
1
, but sagemath says it is0
. This is a maxima bug that has been reported upstream.Here is the original ticket description:
It is not difficult to see that the value of the following limit is
4*m + 1
. However, sagemath says the value is0
:This is a maxima bug:
This is an offshoot of #29616 (maxima asks for assumption but then rejects it as redundant).
Upstream: Reported upstream. Developers acknowledge bug.
Component: calculus
Keywords: limit, maxima
Issue created by migration from https://trac.sagemath.org/ticket/34140