Opened 17 months ago

Last modified 17 months ago

#23992 new defect

solve() doesn't solve some system solvable by (standalone) Maxima's solve()

Reported by: charpent Owned by:
Priority: major Milestone: sage-8.1
Component: symbolics Keywords: maxima, symbolics, interfaces
Cc: Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Description

Short story : Sage's solve(), which uses Maxima's solve() doesn't solve some systems solvable by Maxima's solve when used standalone.

See the long story and an example in this sage-support post.

The prime suspects are the initializations we use to set Maxima up for use with sage. I already tried to set domain to real (which is the default when Maxima is used standalone, whereas we use complex with Sage), to no avail.

Change History (2)

comment:1 follow-up: Changed 17 months ago by dimpase

Did you try with the latest Maxima (5.41)?

(It's probably time to upgrade Sage's Maxima anyway...)

comment:2 in reply to: ↑ 1 Changed 17 months ago by charpent

Replying to dimpase:

Did you try with the latest Maxima (5.41)?

Nope : I have only 5.40 (as packaged by Debian), and Debian is late packaging 5.41...

But my point is that our Maxima (5.39), invoked from the command line, is able to get a solution. The problem lies in our way to call Maxima's solve() from a Sage session.

(It's probably time to upgrade Sage's Maxima anyway...)

Indeed. Isq that complicated ? I saw a message announcing an (your ?) intention to package it, but didn't saw a related ticket (I didn't look specifically for that, so I may have missed it).

Note: See TracTickets for help on using tickets.