Skip to main content
S
SS_97819568-Gravel
8-Gravel
November 4, 2024
Solved

Unable to evaluate

  • November 4, 2024
  • 2 replies
  • 1316 views

I have run into similar problem again where I am not able to evaluate the value stating it cannot assign value greater than 10^307 what is missing in here? 

Best answer by Werner_E

Apart from my suggestion to use symbolic evaluation to get a numeric result I played around because I hoped that Prime would be able to simplify the symbolic expression so that it could be evaluated numerically as well.

 

What I found instead is what I would call a severe bug!

Using "simplify" changes the error message when trying to evaluate numerically (now "m" is said to be unknown/not defined) but also the numeric values in symbolic evaluations!!!

 

Without 'simplify'

Werner_E_2-1730749709647.png

 

now with 'simplify' added

Werner_E_3-1730749728035.png

EDIT: Further investigation showed that the bug has to do with the symbolics being forced to float mode by using floating point numbers.

When we change the definition of R.E from 0.01 to 1/100 and replace the two 0.2 in the definition Y.i(s) tp 1/5, the bug does not show when simplify is used (but numeric evaluation still would fail).

 

Nonetheless a severe bug. Someone should report it to R&D

 

2 replies

S
StuartBruff23-Emerald V
23-Emerald V
November 4, 2024

Your exponential terms ... they're of the form e-a*t+b, where a and b are large numbers.  The -a isn't so bad, but as ea+b = ea·eb, that eb is smashing it out of the 64-bit park.

 

Stuart

S
SS_97819568-GravelAuthor
8-Gravel
November 4, 2024

So there is no possible way I can evaluate those? 

W
Werner_E25-Diamond I
25-Diamond I
November 4, 2024

You could use symbolic evaluation

Werner_E_0-1730748032554.png

Werner_E_1-1730748638940.png

 

 

    W
    Werner_E25-Diamond IAnswer
    25-Diamond I
    November 4, 2024

    Apart from my suggestion to use symbolic evaluation to get a numeric result I played around because I hoped that Prime would be able to simplify the symbolic expression so that it could be evaluated numerically as well.

     

    What I found instead is what I would call a severe bug!

    Using "simplify" changes the error message when trying to evaluate numerically (now "m" is said to be unknown/not defined) but also the numeric values in symbolic evaluations!!!

     

    Without 'simplify'

    Werner_E_2-1730749709647.png

     

    now with 'simplify' added

    Werner_E_3-1730749728035.png

    EDIT: Further investigation showed that the bug has to do with the symbolics being forced to float mode by using floating point numbers.

    When we change the definition of R.E from 0.01 to 1/100 and replace the two 0.2 in the definition Y.i(s) tp 1/5, the bug does not show when simplify is used (but numeric evaluation still would fail).

     

    Nonetheless a severe bug. Someone should report it to R&D

     

      Terms & ConditionsAccessibility statement