1 ACCEPTED SOLUTION
Accepted Solutions
The reason is that Primes new symbolic engine does not assume variables to be (possibly) non-real by default.
The simplification is correct for real values.
Unfortunately adding "assume, ALL=complex" does not help at all. I think it should help so feel free to call and report it as a bug.
I also tried using the predefined function "abs" and a user-defined function using squaring and root, but to no avail:
So I can't think of a suitable workaround (other than using a different software for that kind of symbolic calcs).
BTW, the legacy engine (muPad, included up to Prime 6) was assuming complex (possibly non-real) values by default unless otherwise told. This was in some cases annoying but of course in case of your example muPad does a better job:
I just came across another example how the "new" symbolic compares to the "old" one:
The reason is that Primes new symbolic engine does not assume variables to be (possibly) non-real by default.
The simplification is correct for real values.
Unfortunately adding "assume, ALL=complex" does not help at all. I think it should help so feel free to call and report it as a bug.
I also tried using the predefined function "abs" and a user-defined function using squaring and root, but to no avail:
So I can't think of a suitable workaround (other than using a different software for that kind of symbolic calcs).
BTW, the legacy engine (muPad, included up to Prime 6) was assuming complex (possibly non-real) values by default unless otherwise told. This was in some cases annoying but of course in case of your example muPad does a better job:
I just came across another example how the "new" symbolic compares to the "old" one:
