Post Reply 
Determinant example in help fails in CAS
07-30-2020, 12:02 AM
Post: #1
Determinant example in help fails in CAS
The third example in the Help File for determinants, DET()
fails to parse correctly in the CAS window.
It works fine in the House window.

The other two examples load and solve in CAS


HELP>TREE>THE TOOLBOX MENUS>MATH MENU>MATRIX >DET, example tab > 3
Find all posts by this user
Quote this message in a reply
07-30-2020, 07:14 AM
Post: #2
RE: Determinant example in help fails in CAS
For list processing inside the CAS with det, you can run apply(det,list of matrices).
Find all posts by this user
Quote this message in a reply
07-30-2020, 07:30 AM
Post: #3
RE: Determinant example in help fails in CAS
Good morning, "Parisse", how do I proceed with the "trn ()" or "transpose" functions?
Find all posts by this user
Quote this message in a reply
07-30-2020, 02:25 PM
Post: #4
RE: Determinant example in help fails in CAS
Excellent suggestion: with "mat2list(apply('trn', {mtrix1, matrix2, ...})) the result is right!

Sincerely, Roberto.
Find all posts by this user
Quote this message in a reply
07-31-2020, 05:55 PM
Post: #5
RE: Determinant example in help fails in CAS
EDIT NOTE :
The bug I originally reported is ONLY with the software version of HP Prime not the physical unit.

In Windows version, examples 1 and 2 parse correctly but not 3

"DET({/[[1,2,],[5,6]],[[3,4],[-6,-2]]/}) Error:Bad Argument Value"

In Android HP Prime Lite version, none of them work in CAS mode: the examples do not parse correctly, resulting in a SYNTAX ERROR popup. It looks like the brackets and commas are not converted to tabs or whatever is done internally.
Find all posts by this user
Quote this message in a reply
08-01-2020, 05:41 AM
Post: #6
RE: Determinant example in help fails in CAS
Are you sure that the "physical" calculator behaves differently from the emulators? And anyway, I wouldn't speak of a bug, but of a different processing behavior between "HOME" and "CAS" (see Parisse's answer). Sincerely, Roberto.
Find all posts by this user
Quote this message in a reply
08-01-2020, 06:47 AM
Post: #7
RE: Determinant example in help fails in CAS
(08-01-2020 05:41 AM)robmio Wrote:  Are you sure that the "physical" calculator behaves differently from the emulators?

I wouldn't be so sure of that. They're both built from the same codebase.

There are only 10 types of people in this world. Those who understand binary and those who don't.
Find all posts by this user
Quote this message in a reply
08-01-2020, 07:14 AM
Post: #8
RE: Determinant example in help fails in CAS
Hi, grsbanks. In fact they are both built by the same codebase (at least I suppose that's the case). However, why can't the HP PRIME G2 calculator ("physical" version with firmware 20200121) calculate the following operation (see post: "Error with exp function and imaginary numbers")?

cos(1e49) -> 0.70354916584 (virtual calculator)

cos(-1e49) -> -Inf (HP PRIME G2 "hardware", firmware 20200121).

I cordially greet you, Roberto.
Find all posts by this user
Quote this message in a reply
08-01-2020, 03:15 PM
Post: #9
RE: Determinant example in help fails in CAS
(08-01-2020 07:14 AM)robmio Wrote:  Hi, grsbanks. In fact they are both built by the same codebase (at least I suppose that's the case). However, why can't the HP PRIME G2 calculator ("physical" version with firmware 20200121) calculate the following operation (see post: "Error with exp function and imaginary numbers")?

cos(1e49) -> 0.70354916584 (virtual calculator)

cos(-1e49) -> -Inf (HP PRIME G2 "hardware", firmware 20200121).

I cordially greet you, Roberto.

What angular units are you using? Here's what I get on physical calc:

Home
Deg: COS(1e49) = 0.173648177667
Rad: COS(1e49) = 0.814097070848
Grd: COS(1e49) = 1

CAS
Deg: cos(1e49) = +Inf
Rad: cos(1e49) = +Inf
Grd: cos(1e49) = +Inf

Tom L
Cui bono?
Find all posts by this user
Quote this message in a reply
08-01-2020, 03:38 PM
Post: #10
RE: Determinant example in help fails in CAS
Hi, I used radians. However, since the cosine of an angle can vary only from -1 to +1, regardless of the angular units, the operation: cos(10e49) cannot give a result = + inf.
The error appears only in the HP PRIME G2 (hardware version, last firmware: January 21, 2020, CAS view).
Hopefully HP will fix it quickly, along with other bugs. This error, in fact, prevents the numerical calculation of some integrals not only in CAS view, but also in HOME view:

romberg(exp(-(z)*sinh(t)-n*t),t,0,∞)

with "z" as complex number.
Find all posts by this user
Quote this message in a reply
07-26-2024, 12:10 AM
Post: #11
RE: Determinant example in help fails in CAS
(08-01-2020 03:38 PM)robmio Wrote:  The error appears only in the HP PRIME G2 (hardware version, last firmware: January 21, 2020, CAS view).
Hopefully HP will fix it quickly, along with other bugs. This error, in fact, prevents the numerical calculation of some integrals not only in CAS view, but also in HOME view:

romberg(exp(-(z)*sinh(t)-n*t),t,0,∞)

with "z" as complex number.

It seems that the trouble computing this integral may not be due to the G2 cos(1e50)=-Inf bug, but rather that CAS on the HP Prime has limited precision.

In Xcas, 12 digits:
romberg(exp(-(2*i)*sinh(t)-4*t),t,0,∞) -> undef

Xcas, 15 digits:
romberg(exp(-(2*i)*sinh(t)-4*t),t,0,∞) -> -0.985997062230590e-1*i

At least that's something, though Wolfram alpha gives a different approximation with a real component. Even at 100 digits Xcas has no real component, who is right?

integral(exp(-(2*i)*sinh(t)-4*t),t,0,∞)

- neek
Find all posts by this user
Quote this message in a reply
Post Reply 




User(s) browsing this thread: 2 Guest(s)