[sage-support] Re: max and min evaluating symbolic expressions too soon

2009-09-25 Thread Iwan Lappo-Danilewski
This is a really nasty bug.. Symbolic maxima and minima are mathematical standard tools, they should at least be _callable_ in standard sage. One can see the problem this way: p = var("p") show( plot(max(p,3),(p,0,10)) ) show( plot(min(p,3),(p,0,10)) ) Could someone please post a quickhack to de

[sage-support] Re: max and min evaluating symbolic expressions too soon

2009-09-24 Thread Matt Rissler
I finally got back to looking at this thread. That does work, though it breaks calling plot3d with the following format: max_symbolic=MaxSymbolic() f(x,y)=sqrt(max_symbolic(9-x^2-y^2,0)) plot3d(f(x,y),(x,-3,3),(y,-3,3)) However plot3d(f,(-3,3),(-3,3)) works fine. So it's a fine work around.

[sage-support] Re: max and min evaluating symbolic expressions too soon

2009-09-17 Thread Burcin Erocal
On Wed, 16 Sep 2009 08:16:56 -0700 (PDT) kcrisman wrote: > > Might there be a way to do something that doesn't conflict with the > builtin max function in the same way as the (nearly reviewed) #3587 > seems to avoid conflict with the builtin sum function? This would be > pretty useful, as curr

[sage-support] Re: max and min evaluating symbolic expressions too soon

2009-09-16 Thread kcrisman
Might there be a way to do something that doesn't conflict with the builtin max function in the same way as the (nearly reviewed) #3587 seems to avoid conflict with the builtin sum function? This would be pretty useful, as currently: sage: var('x,y') (x, y) sage: max(x,y) x sage: f(x)=1+x;g(x)=2

[sage-support] Re: max and min evaluating symbolic expressions too soon

2009-09-16 Thread Burcin Erocal
Hi Matt, On Mon, 14 Sep 2009 05:02:54 -0700 (PDT) Matt Rissler wrote: > Is it possible to have max behave as you would expect with a symbolic > expression, i.e. wait until you evaluate it or restrict the domain to > check what is the maximum of the two or more values. Below is a quick implem