Skip to main content
B
bsimpkins1-Visitor
1-Visitor
May 3, 2018
Solved

Prime 4.0 crashes with eigenvecs function

  • May 3, 2018
  • 10 replies
  • 3167 views

hi all, 

i'm running a recent install of Prime 4.0 on Win 10. i'm doing a bit of matrix math. Using eignenval is fine but eigenvecs is problematic. It might solve once or twice but when i go back up to change a parameter value, the sheet tries to recalculate eigenvecs, stalls for ~10 seconds, then shuts itself off!

sheet is attached.

 

cheers,

blake

Best answer by bsimpkins

SOLVED

 

Enabling the "multi-threading" option under calculation is causing the crashes. Disabling multi-threading stabilizes the computation.

Incidentally, this is the 2nd problem with multithreading i've found. in Prime 2.0, enabling multithreading caused sheet calculations to be carried out out of order, so some would fail because earlier calc weren't completed.

10 replies

W
Werner_E25-Diamond I
25-Diamond I
May 3, 2018

I changed the values of V1 and V2 a few times and ran into no error whatsoever. Prime 4.0, Win10 64bit

-
-MFra-21-Topaz II
21-Topaz II
May 3, 2018

Everything is fine with me too. Maybe he needs a good antivirus (excluding free ones)

B
bsimpkins1-VisitorAuthor
1-Visitor
May 3, 2018

UPDATE

 

rewrote the sheet in Prime 2.0 on Win 7 machine and it runs fine (and considerably faster).

W
Werner_E25-Diamond I
25-Diamond I
May 3, 2018

You should have stated which values you changed in which way before you ran into the error you described.

Do you still experience the same error when using your new Prime 2.0 sheet with your Prime4 installation?

B
bsimpkins1-VisitorAuthorAnswer
1-Visitor
May 3, 2018

SOLVED

 

Enabling the "multi-threading" option under calculation is causing the crashes. Disabling multi-threading stabilizes the computation.

Incidentally, this is the 2nd problem with multithreading i've found. in Prime 2.0, enabling multithreading caused sheet calculations to be carried out out of order, so some would fail because earlier calc weren't completed.

    W
    Werner_E25-Diamond I
    25-Diamond I
    May 3, 2018

    I see!

    I can confirm that enabling multithreading produces the very same effect you described for me, too.

    Bad bug, indeed!

    D
    DJF16-Pearl
    16-Pearl
    May 3, 2018

    This is interesting.  I had to turn off multi-threading in 3.0/3.1 or it always crashed.  4.0 I've had no issues until now - but I do confirm this bug.  (win 7, 64)

     

    speaking of bugs - does 4.0 close for anyone else if you double click the round (M) button in upper left?

    Terms & ConditionsAccessibility statement