If you have a design for writing the whole thing
from scratch, then that would be worth writing down.
It is not that Sage has to be fixed to call Maxima "the right way".
It is that Macsyma / Maxima does not have a suitable
design. Nor does Mathematica or Maple or (so far
as I can tell) sympy or F
On 11/29/19 7:41 PM, rjf wrote:
>
> Perspective: you can diddle with trying to set domains
> "right" but you have probably missed the boat in the
> system design and are unlikely to be able to patch it.
> ...
>
> Sorry for being such a pessimist, but some of us have
> been there.
>
There is no
I mentioned in answer to another thread about Maxima/domain/integration
the caution that this is likely missing the point.
Setting a domain or passing this setting to Maxima is not a solution.
It is likely a symptom that you are making a mathematical error.
quoting in part..
Since log() is in gen
On 11/29/19 2:01 PM, Emmanuel Charpentier wrote:
> Dear list,
>
> We have a non inconsiderable stock of tickets whose analysis ends up
> with someting amounting to "bug due the domain:complex option in
> Maxima", and no solution in view.
Which tickets? Are they all integration?
> Couldn't we wo
Fri 2019-11-29 19:01:15 UTC, Emmanuel Charpentier:
>
> Since the symbolic integration methods have recently
> gained an "algorithm=" keyword, an alternative would
> be to propose an "algorithm="maxima_real" option.
I like this idea.
--
You received this message because you are subscribed to the
On Friday, November 29, 2019 at 12:45:45 PM UTC-8, Jonathan Kliem wrote:
>
> The following leads to a TypeError:
>
> sage: K2. = QuadraticField(2)
> sage: K3. = QuadraticField(3)
> sage: sqrt2 + sqrt3
>
> Both of them are real embedded by default, so coercion should work (at least
> this is my o
The following leads to a TypeError:
sage: K2. = QuadraticField(2)
sage: K3. = QuadraticField(3)
sage: sqrt2 + sqrt3
Both of them are real embedded by default, so coercion should work (at least
this is my opinion).
This can be fixed by specifying that both of them are embedded into the
algebr
A big thank you for your help, which was absolutely necessary. Synthesis:
1) Vincent Neiger's proposal works ; I have been able to obtain acceptable
duplications of Maxima's pade results in a small sample of test cases
(mostly by treating the "shifts" symmetrically).
However, the overall combin
Dear list,
We have a non inconsiderable stock of tickets whose analysis ends up with
someting amounting to "bug due the domain:complex option in Maxima", and no
solution in view.
Couldn't we work around this problem by offering a "domain=" option
(default value =complex") which, when set, woul
Hello Erik,
Would you make a ticket and upload a branch on trac, please ?
Frederic
Le jeudi 23 mai 2019 18:41:04 UTC+2, E. Madison Bray a écrit :
>
> Something I've wanted for a long time in the Sage doctest runner is
> progress bars, so I hacked up a prototype (see screenshot). It works
> ev
10 matches
Mail list logo
