Yes, as long as I don't need to solve equations and such, I work on HOME mode too. It is smoother (and it is HP 100% code). In CAS, the trig functions work in DEG mode, but the ARG function continues to return radians, that is why, in CAS, I advise my students to work in RAD mode, safer that way.
I never calculate in degrees, because physics formula mostly use radians and you always can convert by foot. What happens, if you don't remove the EXACT flag? Of course I can try myself. ;)
Actually, I set the EXACT flag back on. With it on, the answers come out as "exact" expressions with integers and rational numbers, and the occasional root. Then, to get the floating point value that I use in engineering, I need to use either evalf(), or the approx key (shift enter). If it is not too much extra hassle, leave the EXACT mode on. I did.
Happily, I think the XCAS community (it's open source), corrected that bug in its latest release. However, I still use my own argd() p2r() and r2p() functions. They are very much part of my workflow. And the payoff has been great, less grief when phases are in degrees, but I need to compute a value at a point in time (for which I need the4 phase in radians).
I’ve noticed that. Acctually, there is a few issues with CAS and complex numbers. I always switch to Home screen during complex calculations.
Yes, as long as I don't need to solve equations and such, I work on HOME mode too. It is smoother (and it is HP 100% code). In CAS, the trig functions work in DEG mode, but the ARG function continues to return radians, that is why, in CAS, I advise my students to work in RAD mode, safer that way.
Thank you for sharing that info.
My pleasure!
There is no function that simply convert degrees to radians?
180_deg STO 1_rad
(press the Sto> button, either from the screen or {Shift} {EEX} button)
I never calculate in degrees, because physics formula mostly use radians and you always can convert by foot.
What happens, if you don't remove the EXACT flag? Of course I can try myself. ;)
Actually, I set the EXACT flag back on. With it on, the answers come out as "exact" expressions with integers and rational numbers, and the occasional root. Then, to get the floating point value that I use in engineering, I need to use either evalf(), or the approx key (shift enter). If it is not too much extra hassle, leave the EXACT mode on. I did.
good
Thanks
Thanks for the video. I try to reproduce this with the April 2023 firmware and can't. Anyone else?
Happily, I think the XCAS community (it's open source), corrected that bug in its latest release. However, I still use my own argd() p2r() and r2p() functions. They are very much part of my workflow. And the payoff has been great, less grief when phases are in degrees, but I need to compute a value at a point in time (for which I need the4 phase in radians).
Por favor traducir a español