sqrt(1+i)

[moonbeam]

(deleted by author)

[parisse]

You must write your own program to do that. I have disabled exact sqrt of complex numbers on the Prime because it could freeze the calculator too easily (computations with algebraic extension becoming much too complicated and difficult to interrupt).

[Helge Gabert]

Can you re-write as

e^(1/2*LN(1+i)) ?

That would be consistent with (1+i)^(1/3), (1+i)^(1/4), etc. which result in

e^(1/3*LN(1+i)), e^(1/4*LN(1+i)), etc.

Better solution than to force an approximate result in CAS! Thanks.

[dg1969]

Math is not my favorite hobby all my excuse if the comment does not provide a real alternative...




very strange... With

Code:

SQRT(1+i)

on the command line the prime provide an approx answer at the enter key press... but if you select the same "sqrt(1+i)" on the history (left side of the screen) by a touch screen and then press simplify...

[Helge Gabert]

Interesting. Thanks for the tip. The result is exact and correct.

But now try sqrt(sqrt(1+i)) . . . That is probably the reason why Bernard resorted to the approximations.

[Helge Gabert]

Interesting. If the TI-92 can do it, maybe that will provide an incentive for the HP Prime development team

[Erwin]

(10-04-2016 12:41 PM)moonbeam Wrote:  

(09-27-2016 04:19 AM)Helge Gabert Wrote:  But now try sqrt(sqrt(1+i)) . . . That is probably the reason why Bernard resorted to the approximations.

I concur that the exact results aren't likely to have practical use for all but the simplest cases and I recall from another thread that the Prime doesn't provide enough support to CAS to let it fail gracefully.

Having said that, I've installed the XCAS desktop app and sqrt(1+i) crashes it. I'm not sure if this is a bug or user error.

Getting intrigued, I tried it on my HP-50g. sqrt(1+i) works, sqrt(sqrt(1+i)) crashes it hard. My ancient TI-92Plus on the other hand just keeps chugging along when nesting sqrt functions; I got bored after eight...

Hi,

on a HP71B the result for sqr(sqr(1+j)): 1,06955393236 +0,212747504726j No problem with the ancient calculator :-) interesting, that ist could be a problem on the newer one - or I misunderstand the question

[Helge Gabert]

Yes, you are misunderstanding. The idea is to obtain an exact, symbolic result, please see above posts. The 71B does not have a built-in CAS.

[parisse]

(10-04-2016 12:41 PM)moonbeam Wrote:  Having said that, I've installed the XCAS desktop app and sqrt(1+i) crashes it. I'm not sure if this is a bug or user error.

Strange, the current version of Xcas work with sqrt(1+i) and also sqrt(sqrt(1+i)) (but the answer is very complicated)

[Tim Wessman]

(10-04-2016 03:44 PM)Erwin Wrote:  on a HP71B the result for sqr(sqr(1+j)): 1,06955393236 +0,212747504726j No problem with the ancient calculator :-) interesting, that ist could be a problem on the newer one - or I misunderstand the question

It is exclusively when dealing with exact, symbolic results (which keep getting larger and larger the more you apply them).

Prime returns the approximated result identically to the 71.

[Joe Horn]

(10-04-2016 12:41 PM)moonbeam Wrote:  Getting intrigued, I tried it on my HP-50g. sqrt(1+i) works, sqrt(sqrt(1+i)) crashes it hard.

After 11.37 seconds, my 50g returns an exact result for 'sqrt(sqrt(1+i))' EVAL. Perhaps our settings differ?

[parisse]

(10-04-2016 07:35 PM)moonbeam Wrote:  

(10-04-2016 06:34 PM)parisse Wrote:  Strange, the current version of Xcas work with sqrt(1+i) and also sqrt(sqrt(1+i)) (but the answer is very complicated)

The versions I downloaded are about ten days old. The examples above make it crash on the Windows box I used, but apparently not on a Mac. I haven't tried Linux.

I tried the windows 64, linux 64 and mac os versions without problems. Which version of xcas do you have?

[roadrunner]

I created a little program to return the exact result for nested square roots of a complex number:

Code:


#pragma mode( separator(.,;) integer(h32) )

rootroot(a,n);

#cas
rootroot(a,n):=
BEGIN
 local x,y,ra,ia;
 ra:=RE(a);
 ia:=IM(a); 
 y=√(-ra+√(ra^2+ia^2))/√2;
 x=ia/(2*y);
 if n==1 then return x+y*i; end;
 return rootroot(x+y*i,n-1);
END;
#end

It crashes the emulator for values of n 6 or greater. Example:

rootroot(1+i,5) works but rootroot(1+i,6) crashes.

However, approx(rootroot(1+i,6)) returns the correct approximate answer, which tells me the program is returning a correct answer but the display can't handle it, and sits there with an hour glass in the corner.

What am I doing wrong?

-road
-edited a grammatical error

[parisse]

It has been reported that the windows 32 bits version of xcas works on windows 10 while the 64 bits version crashes.

[DedeBarre]

Hi..i am a new user here. In my case it crashes the emulator for values of n 6 or greater. rootroot(1+i,5) works but rootroot(1+i,6) crashes.However, approx(rootroot(1+i,6)) returns the correct approximate answer, which tells me the program is returning a correct answer but the display can't handle it, and sits there with an hour glass in the corner.

pcb assembly usa

[parisse]

(10-05-2016 02:59 PM)compsystems Wrote:  I think the rules of simplifications on the ti68k calculators are more powerful in many cases

This is your opinion, I don't share it. As a counterexample try simplifying 4*atan(1/5)-atan(1/239) on your ti.
The handling of sqrt in Xcas is based on the more general concept of algebraic extension of Q (rootof in Xcas), where the emphasis is on recognizing 0 in a deterministic manner. Internally, there is no embedded sqrt inside Xcas, only a common algebraic extension for all the coefficients. Since displaying rootofs would scare many users, simple algebraic extensions are converted to more standard sqrt after computations, but as a side effect this does not necessarily *look* as simple (especially for embedded sqrt). And you can rework sqrt(1+i): for example if you want real or imaginary part: normal(re(sqrt(1+i))); normal(im(sqrt(1+i)))

[compsystems]

(10-05-2016 07:24 PM)parisse Wrote:  

(10-05-2016 02:59 PM)compsystems Wrote:  I think the rules of simplifications on the ti68k calculators are more powerful in many cases

.... As a counterexample try simplifying 4*atan(1/5)-atan(1/239) on your ti.
The handling of sqrt in Xcas is based on the more general concept of algebraic extension of Q (rootof in Xcas), where the emphasis is on recognizing 0 in a deterministic manner. Internally, there is no embedded sqrt inside Xcas, only a common algebraic extension for all the coefficients. Since displaying rootofs would scare many users, simple algebraic extensions are converted to more standard sqrt after computations, but as a side effect this does not necessarily *look* as simple (especially for embedded sqrt). And you can rework sqrt(1+i): for example if you want real or imaginary part: normal(re(sqrt(1+i))); normal(im(sqrt(1+i)))

ok, but they are more steps (input) to get to the same output,



ti68k:
input (approx mode): √(1.0+i)
output x+y*i: 1.09868411347 + 0.455089860562*i

input (exact mode): √(1+i)
output x+y*i: sqrt(2*(sqrt(2)+1))/2 + (sqrt(2*(sqrt(2)+1))/2)*i


Xcas
input: normal(re(√(1+i))) + normal(im(√(1+i)))*i
output: (√2*√(√2+1)+(1+i)*√(√2+1))/(√2+2) not is a x + y * i form
fabulous if you include a flag in xcas to see the output of a complex expression in the form x + y * i Good Idea?

Xcas (next realease) =)
input (exact mode and new flag): √(1+i)
output: sqrt(2*(sqrt(2)+1))/2 + (sqrt(2*(sqrt(2)+1))/2)*i

another way to transform the output to x+y*i
√(1+i) -> (1+i)*√(√2+1)/(√2)
substituting i -> x
coeff( (1+x)*√(√2+1)/(√2),x) coeff separates the real and complex part
poly1[√2*√(√2+1)/2, √2*√(√2+1)/2]
Ans .* poly1[1, i]
poly1[√2*√(√2+1)/2, √2*√(√2+1)/2*i]
ΣLIST(poly1[√2*√(√2+1)/2, √2*√(√2+1)/2*i])
sqrt(2*(sqrt(2)+1))/2 + (sqrt(2*(sqrt(2)+1))/2)*i


we also need a version of QPI-ROOT cmd

Code:

QPIROOT(normal(re(√(1+i)))+normal(im(√(1+i)))*i)

-> sqrt(2*(sqrt(2)+1))/2 + (sqrt(2*(sqrt(2)+1))/2)*i