On Sep 3, 3:38 pm, William Cauchois wrote:
> By the way, you can make your original example work by using a lambda
> instead of a symbolic expression:
>
> sage: plot3d(lambda x, y: abs(e^(pi*i*x)+e^(pi*i*y)), (0,1), (0,1))
Oh, yes, I know. And I try to avoid using lambda notation whenever
pos
By the way, you can make your original example work by using a lambda
instead of a symbolic expression:
sage: plot3d(lambda x, y: abs(e^(pi*i*x)+e^(pi*i*y)), (0,1), (0,1))
Should work. (Although I'm getting the error "plot variables should be
distinct", which I think is a bug; workaround is to c
2009/9/1 Robert Bradshaw
>
> On Sep 1, 2009, at 8:58 PM, William Cauchois wrote:
>
> > It seems to me that the error comes from feeding a function which uses
> > i into fast_float (called by the plotting functions to compile the
> > function to be plotted into an optimized form). I tried a simple
> The code leaves a lot to be desired. For example, now that we have
> fast_callable, with CDF support, we should be using that. Actually,
> we're using the helper function setup_for_eval_on_grid (to normalize
> the boundaries) and then ignoring the returned function, so this
> check is c
On Sep 1, 2009, at 8:58 PM, William Cauchois wrote:
> It seems to me that the error comes from feeding a function which uses
> i into fast_float (called by the plotting functions to compile the
> function to be plotted into an optimized form). I tried a simpler
> function using i and got the same
It seems to me that the error comes from feeding a function which uses
i into fast_float (called by the plotting functions to compile the
function to be plotted into an optimized form). I tried a simpler
function using i and got the same error:
sage: plot3d(x + y + i, (x, 0, 1), (y, 0, 1))
Traceb
