Skip to main content
C
CuzImInside1-Visitor
1-Visitor
April 22, 2019
Solved

BUG REPORT

  • April 22, 2019
  • 3 replies
  • 7604 views

Hello everyone,

 

a few days ago I experienced a really annoying bug.

 

You will find a mathcad file attached, where my problem is described.

I will also attach a pdf file for those people who can't open the mathcad file.

 

MathCAD Version: Prime 5.0.0.0

 

 

I would be glad if anyone could solve my problem or if any staff could forward this report to the responsible department.

 

 

 

Thanks for helping!

 

Lukas

Best answer by Werner_E

Funny effect and I agree thats it a bug. But it won't help reporting it to PTC as they are not interested, they don't care about us Mathcad/Prime users.

In playing around with your sheet I noticed two things:

1) The bug only occurs if the function name of the derivative consists of more than one character

2) Omitting the "=0" also persuades Prime to return the correct solution:

B.png

The bug shows in Prime 4 and in Prime 5, but the bug is not present in Mathcad 15:

B2.png

 

Good thing is that there are two easy solutions:

1) If you are lazy, not only omit stating which variable you want Prime to solve for but also omit the " = 0 "

or

2) Always state which variable Prime should solve for - its good habit to do so anyway.

 

3 replies

W
Werner_E25-Diamond IAnswer
25-Diamond I
April 22, 2019

Funny effect and I agree thats it a bug. But it won't help reporting it to PTC as they are not interested, they don't care about us Mathcad/Prime users.

In playing around with your sheet I noticed two things:

1) The bug only occurs if the function name of the derivative consists of more than one character

2) Omitting the "=0" also persuades Prime to return the correct solution:

B.png

The bug shows in Prime 4 and in Prime 5, but the bug is not present in Mathcad 15:

B2.png

 

Good thing is that there are two easy solutions:

1) If you are lazy, not only omit stating which variable you want Prime to solve for but also omit the " = 0 "

or

2) Always state which variable Prime should solve for - its good habit to do so anyway.

 

C
CuzImInside1-VisitorAuthor
1-Visitor
April 22, 2019

Thanks for your detailed answer!

 

I think I will accustom to always write the variable I want to solve for.

 

I just do not like such little unpredictable bugs, they could be really bad at an exam.

 

 

ttokoro
ttokoro21-Topaz I
21-Topaz I
April 24, 2019

test1.png

t.t.
L
LucMeekes23-Emerald IV
23-Emerald IV
April 22, 2019

What strikes me most is the fact that the symbolic processor returns 0.69314718055994530942 as an answer, instead of just:

ln(2)

 

Luc

W
Werner_E25-Diamond I
25-Diamond I
April 22, 2019
@LucMeekes wrote:

What strikes me most is the fact that the symbolic processor returns 0.69314718055994530942 as an answer, instead of just:

ln(2)

 

Luc

Yes, thats disappointing. Guess Maple in your MC11 does a better job here.

In Mathcad or Prime we have to help MuPad a little bit so that it will come up with the exact result:

B.png

V
VladimirN24-Ruby III
24-Ruby III
August 21, 2019

Please send your issue by using "Mathcad Support Center": 

http://www.ptc.com/support/mathcad_supportCenter.htm

https://support.ptc.com/support/mathcad_supportCenterEnterprise.htm

C
CuzImInside1-VisitorAuthor
1-Visitor
August 22, 2019

No chance, they don't want to (look at the screenshot) ...

 

L
LucMeekes23-Emerald IV
23-Emerald IV
August 22, 2019

That is very much in line with common experience on this forum.

Any decent software (developing and selling) company should be happy (and generally is) to learn from anyone if there is a bug in their software.

PTC is not interested in improving their product, and certainly does not want to learn from those users that don't  pay maintenance fees. I can only imagine that they are happy to take customer money for their product, but feel distraught whenever a comment on that software is raised (because it takes time=money to pay attention to it); more so when the comment comes from a non-paying customer.

 

Luc

Terms & ConditionsAccessibility statement