Dear Michael,
On Dec 17, 9:08 pm, mabshoff wrote:
> The 0.07 seconds is the CPU time we spend on the Sage side to
> communicate with Maxima, the rest is probably starting Maxima,
> communicating and then the solve on Maxima's side also. As you well
> know there is this general slowdown effect wh
On Dec 17, 2008, at 11:49 AM, David Joyner wrote:
>
> On Wed, Dec 17, 2008 at 2:41 PM, Simon King jena.de> wrote:
>>
>> Dear Sage supporters,
>>
>> inspired by http://groups.google.com/group/sage-support/
>> browse_thread/thread/729f4a557d970195?hl=en,
>> I was playing around with the solve com
On Dec 17, 11:41 am, Simon King wrote:
> Dear Sage supporters,
Hi Simon,
> 2. Why does it take so long to return the solution dictionary?
> From the solve-docstring:
> sage: ct=cputime()
> sage: time solve([x^2+y^2 == 1, y^2 == x^3 + x + 1], x, y,
> solution_dict=True)
> CPU times: user
On Wed, Dec 17, 2008 at 2:41 PM, Simon King wrote:
>
> Dear Sage supporters,
>
> inspired by
> http://groups.google.com/group/sage-support/browse_thread/thread/729f4a557d970195?hl=en,
> I was playing around with the solve command.
>
> I found two questions:
> 1. How can one add assumptions (such
