Comment #2 on issue 2418 by matt...@gmail.com: Interval.evalf() returns a
mpmath interval
http://code.google.com/p/sympy/issues/detail?id=2418
And remove interval_evalf() from sympy/solvers/inequalities.py.
--
You received this message because you are subscribed to the Google Groups
Comment #3 on issue 2418 by asmeurer: Interval.evalf() returns a mpmath
interval
http://code.google.com/p/sympy/issues/detail?id=2418
Yeah, interval_evalf() should become Interval.evalf().
--
You received this message because you are subscribed to the Google Groups
sympy-issues group.
To
Comment #11 on issue 2406 by renato.c...@gmail.com: improve Tuple
constructor
http://code.google.com/p/sympy/issues/detail?id=2406
I just sent a pull request: https://github.com/sympy/sympy/pull/352
The fromiter() function just sympifies its args and pass on to
Basic.__new__. As it is,
Updates:
Labels: NeedsReview
Comment #12 on issue 2406 by renato.c...@gmail.com: improve Tuple
constructor
http://code.google.com/p/sympy/issues/detail?id=2406
(No comment was entered for this change.)
--
You received this message because you are subscribed to the Google Groups
Comment #23 on issue 1620 by renato.c...@gmail.com: Allow derivatives of
unknown functions evaluated at a point
http://code.google.com/p/sympy/issues/detail?id=1620
I implemented an Eval class (not sure about the name, though):
Updates:
Labels: ness987 NeedsReview
Comment #5 on issue 2387 by ness...@googlemail.com: Evalf of trig functions
with imaginary arguments
http://code.google.com/p/sympy/issues/detail?id=2387
Pull request: https://github.com/sympy/sympy/pull/354
--
You received this message because
Comment #24 on issue 1620 by ronan.l...@gmail.com: Allow derivatives of
unknown functions evaluated at a point
http://code.google.com/p/sympy/issues/detail?id=1620
Rather than Eval(f(x), x, x0), can't you use Eval(Lambda(x, f(x)), x0)?
That way, you wouldn't have to duplicate the logic of
Status: Accepted
Owner: ronan.l...@gmail.com
Labels: Type-Defect Priority-High Milestone-Release0.7.0 Simplify
New issue 2420 by ronan.l...@gmail.com: Refactor EPath
http://code.google.com/p/sympy/issues/detail?id=2420
This got in with several major issues unresolved:
* Bad module name ('tools'
Status: Accepted
Owner: smi...@gmail.com
Labels: Type-Defect Priority-Medium
New issue 2421 by smi...@gmail.com: python(expr) issues
http://code.google.com/p/sympy/issues/detail?id=2421
h[6] print python(Eq(a,b))
a = Symbol('a')
b = Symbol('b')
e = a == b
But a == b is a bool
Comment #25 on issue 1620 by renato.c...@gmail.com: Allow derivatives of
unknown functions evaluated at a point
http://code.google.com/p/sympy/issues/detail?id=1620
I thought about that, but decided not to do it because I wanted Eval to
auto-expand whenever possible (I pushed this behavior
Comment #26 on issue 1620 by ronan.l...@gmail.com: Allow derivatives of
unknown functions evaluated at a point
http://code.google.com/p/sympy/issues/detail?id=1620
I see. It feels wrong not to use Lambda somehow, but we can deal with that
later, once we get Eval to work (we might actually
Updates:
Status: Started
Labels: -Priority-Medium Priority-High Milestone-Release0.7.0
Comment #1 on issue 2411 by ronan.l...@gmail.com: Revert _op_priority
deletion
http://code.google.com/p/sympy/issues/detail?id=2411
This needs to be resolved before the release, BTW. I'm
Updates:
Status: Started
Labels: NeedsReview
Comment #1 on issue 2420 by ronan.l...@gmail.com: Refactor EPath
http://code.google.com/p/sympy/issues/detail?id=2420
https://github.com/sympy/sympy/pull/356
--
You received this message because you are subscribed to the Google
Comment #27 on issue 1620 by asmeurer: Allow derivatives of unknown
functions evaluated at a point
http://code.google.com/p/sympy/issues/detail?id=1620
I would call it Subs, not Eval. And since it's an Uppercase unevaluated
class, I think it shouldn't try to split out terms automatically.
Comment #2 on issue 2411 by asmeurer: Revert _op_priority deletion
http://code.google.com/p/sympy/issues/detail?id=2411
Will that be ready soon, or should we just revert the reversion?
--
You received this message because you are subscribed to the Google Groups
sympy-issues group.
To post to
Comment #3 on issue 2411 by ronan.l...@gmail.com: Revert _op_priority
deletion
http://code.google.com/p/sympy/issues/detail?id=2411
Yes, it's ready soon.
--
You received this message because you are subscribed to the Google Groups
sympy-issues group.
To post to this group, send email to
Status: Accepted
Owner: sean.v@gmail.com
Labels: Type-Defect Priority-Medium WrongResult
New issue 2423 by sean.v@gmail.com: Rotation.d function incorrect
evaluation
http://code.google.com/p/sympy/issues/detail?id=2423
from sympy.physics.quantum.spin import Rotation
Updates:
Labels: ness987 NeedsReview
Comment #5 on issue 2387 by ness...@googlemail.com: Evalf of trig functions
with imaginary arguments
http://code.google.com/p/sympy/issues/detail?id=2387
Pull request: https://github.com/sympy/sympy/pull/354
--
You received this message because
Updates:
Status: Started
Labels: NeedsReview
Comment #1 on issue 2420 by ronan.l...@gmail.com: Refactor EPath
http://code.google.com/p/sympy/issues/detail?id=2420
https://github.com/sympy/sympy/pull/356
--
You received this message because you are subscribed to the Google
Updates:
Labels: NeedsReview
Comment #4 on issue 2411 by ronan.l...@gmail.com: Revert _op_priority
deletion
http://code.google.com/p/sympy/issues/detail?id=2411
https://github.com/sympy/sympy/pull/359
--
You received this message because you are subscribed to the Google Groups
On 24 Mai, 03:58, Aaron S. Meurer asmeu...@gmail.com wrote:
{x: Interval(-1, 1)}
The problem is that in general the components of the solutions might
depend on each other.
Vinzent
--
You received this message because you are subscribed to the Google Groups
sympy group.
To post to this group,
On 24 Mai, 05:08, Matthew mrock...@gmail.com wrote:
You're right - it's unclear if this should be an event or a random
variable. Thanks for the heads up on 'or'. I was hoping to use | for
'given' in the future. I'll figure this out when I get there. Isn't
'==' ok to use though? Isn't it
On Tue, May 24, 2011 at 10:44, Vinzent Steinberg
vinzent.steinb...@googlemail.com wrote:
On 24 Mai, 05:08, Matthew mrock...@gmail.com wrote:
You're right - it's unclear if this should be an event or a random
variable. Thanks for the heads up on 'or'. I was hoping to use | for
'given' in the
Hi all,
I have been trying to simplify expressions with floating point numbers
and I noticed that the results are quite unpredictable. In many cases
the calculation took indefinite time (until I killed it) or produced
wrong results (infinity or other incorrect expressions). Here is an
example:
On Tue, May 24, 2011 at 11:42 AM, Robert Kern robert.k...@gmail.com wrote:
On Tue, May 24, 2011 at 10:44, Vinzent Steinberg
vinzent.steinb...@googlemail.com wrote:
On 24 Mai, 05:08, Matthew mrock...@gmail.com wrote:
You're right - it's unclear if this should be an event or a random
variable.
Quite strange indeed.
On my Mac Python 2.7, sympy.__version__ = 0.6.7 I get:
In [17]: expr = (2.1 - 2.1*y**2 + 2*x)/x**3
In [18]: sympy.simplify(expr)
Out[18]: -inf
In [19]: expr = (2.1*x*(1-y)**2+2*y*x)/ x**3
In [20]: sympy.simplify(expr)
Out[20]: (2.1 - 2.2*y + 2.1*y**2)/x**2
In [21]: expr
Le mardi 24 mai 2011 à 12:28 -0500, Andy Ray Terrel a écrit :
On Tue, May 24, 2011 at 11:42 AM, Robert Kern robert.k...@gmail.com wrote:
On Tue, May 24, 2011 at 10:44, Vinzent Steinberg
vinzent.steinb...@googlemail.com wrote:
On 24 Mai, 05:08, Matthew mrock...@gmail.com wrote:
You're
Andy Ray Terrel wrote:
Quite strange indeed.
On my Mac Python 2.7, sympy.__version__ = 0.6.7 I get:
In [17]: expr = (2.1 - 2.1*y**2 + 2*x)/x**3
In [18]: sympy.simplify(expr)
Out[18]: -inf
This raises an error for me:
raise ValueError(can't raise polynomial to a negative power)
Presumably mateusz (or aaron) know better than me, but the problem is
simply that polys does not really work well with Floats.
There is also an open issue (2384) related to this.
On 24.05.2011 20:13, Chris Smith wrote:
Andy Ray Terrel wrote:
Quite strange indeed.
On my Mac Python 2.7,
That's basically correct. The problem is that certain polynomial algorithms
(in this case, polynomial division) rely on the ability to determine zero
equivalence in the coefficients. But floating point numbers, as we all know,
have the problem where they will often give something like 1e-14
Hi all,
Thanks for the quick reply. I thought that a sensible solution might
be to introduce a new floating point type (for example, Float) which
does the round off by itself (with given precision). Basically, one
could write the equation like this:
expr =
I see that a test which is proving difficult to verify was deleted in
the commit that made this change:
def test_1st_homogeneous_coeff_ode2():
eq1 = f(x).diff(x) - f(x)/x+1/sin(f(x)/x)
eq2 = x**2 + f(x)**2 - 2*x*f(x)*f(x).diff(x)
eq3 = x*exp(f(x)/x) + f(x) - x*f(x).diff(x)
What is the SHA1 of the commit?
Aaron Meurer
On May 24, 2011, at 3:38 PM, smichr wrote:
I see that a test which is proving difficult to verify was deleted in
the commit that made this change:
def test_1st_homogeneous_coeff_ode2():
eq1 = f(x).diff(x) - f(x)/x+1/sin(f(x)/x)
eq2 =
Hi Everyone,
I'm revamping Sets a bit as a precursor to my GSoC project. The first part
of this is creating a FiniteSet object to go along with Intervals (like (0,
1] ) and Unions (like [-1,0) U (0, 1] ).
I changed the default behavior of Interval(1,1) (interval from 1 to 1
inclusive, i.e. [1,
Hi.
On May 24, 2011, at 5:50 PM, Matthew Rocklin wrote:
Hi Everyone,
I'm revamping Sets a bit as a precursor to my GSoC project. The first part of
this is creating a FiniteSet object to go along with Intervals (like (0, 1] )
and Unions (like [-1,0) U (0, 1] ).
I changed the default
Hi,
On 24 May 2011 17:42, Aaron S. Meurer asmeu...@gmail.com wrote:
Hi.
On May 24, 2011, at 5:50 PM, Matthew Rocklin wrote:
Hi Everyone,
I'm revamping Sets a bit as a precursor to my GSoC project. The first
part of this is creating a FiniteSet object to go along with Intervals (like
Cool. I'm going ahead with the changes. I'm currently blocking on the
reduce_poly_inequalities function.
It assumes that it's dealing with a list of Intervals which it then
will return or turn into a relational. I have generalized this
as_relational process to all sets but am having difficulty
Hi,
On 24 May 2011 18:41, Matthew mrock...@gmail.com wrote:
Cool. I'm going ahead with the changes. I'm currently blocking on the
reduce_poly_inequalities function.
It assumes that it's dealing with a list of Intervals which it then
will return or turn into a relational. I have generalized
Oops, removing inexact arithmetic does cause errors.
On May 24, 8:41 pm, Matthew mrock...@gmail.com wrote:
Cool. I'm going ahead with the changes. I'm currently blocking on the
reduce_poly_inequalities function.
It assumes that it's dealing with a list of Intervals which it then
will return
On May 24, 2011, at 7:41 PM, Matthew wrote:
Cool. I'm going ahead with the changes. I'm currently blocking on the
reduce_poly_inequalities function.
It assumes that it's dealing with a list of Intervals which it then
will return or turn into a relational. I have generalized this
My problem seems to be different from what is discussed in the issue.
I'm succeeding in interactive mode but not when run from the shell.
I'm also dealing with tests, not doctests.
My process is fishy though. I'm opening up either isympy or ipython
and then runing the test to get all of the
e12fb20c2405b4fdcac8dff980c0b6637c46ec06
--
You received this message because you are subscribed to the Google Groups
sympy group.
To post to this group, send email to sympy@googlegroups.com.
To unsubscribe from this group, send email to
sympy+unsubscr...@googlegroups.com.
For more options,
For whatever reason the problem is no longer around (maybe I was
confused before)?
all tests pass
I've changed the behavior of Interval.evalf() to produce an Interval
with evalf'ed endpoints rather than produce a multi-precision-
interval. It doesn't seem to break anything.
One of the problems I am running into with polys is this:
p1,p2=[(x - 5)**2 + (y - 5)**2 - 4, -(-x + 5)*(-x - 2*2**(1/
S(2)) + 5) - (-y
+ 5)*(-y + 5)]
solve([p1,p2])
Traceback (most recent call last):
File stdin, line 1, in module
File sympy\solvers\solvers.py, line
Just a reminder to students that this means that you need to blog at some point
this week. You don't have to do it until the end of the day on Saturday. But
it's just a reminder that it needs to be done.
If you don't have anything to blog about because you haven't done much yet,
then a
45 matches
Mail list logo
