Skip to main content
S
ssato15-Moonstone
15-Moonstone
April 25, 2018
Solved

PLOT ERROR

  • April 25, 2018
  • 2 replies
  • 5457 views

I have a quetion.

I attatched the file.

 

I do not understand the error on last plot of file.

I think "n" is no problem.

 

Best Rgs

Best answer by ssato

Everyone, I understood well.......

2 replies

W
Werner_E25-Diamond I
25-Diamond I
April 25, 2018

I do not understand the error on last plot of file.

I think "n" is no problem.


I agree and as I don't see any rational reason for this error I would call it a strange Prime bug.

Prime seems not to like the fact, that only every fourth value is non-zero? Not sure what exactly causes that bug.

But I can confirm that it should work and it also does work OK in Mathcad 15

B3.png

I found two possible workarounds to do it in Prime (not satisfactory but at least you get your plots):

1) change the factor 2 of the cosine to something close to 2

2) change the step width of your range n to 1,1.5 .. 50

B1.png

 

B2.png

F
Fred_Kohlhepp23-Emerald I
23-Emerald I
April 25, 2018

Interesting!  In Prime 3.0:

Capture.PNG

Going backwards?

W
Werner_E25-Diamond I
25-Diamond I
April 25, 2018

Fred, your function v differs from the original function. The 2 is only a factor of the cosine.

S
ssato15-MoonstoneAuthor
15-Moonstone
April 25, 2018

Thank you. everyone.

I will attach another file.
If "a" is an odd number in the last graph, an error will occur only with graph creation.
If "a" is an even number, no error occurs.

In the end, is this a bug in Prim 4.0?

If you are a bug, where should I contact?

W
Werner_E25-Diamond I
25-Diamond I
April 26, 2018

It sure IS a bug and obviously a new one as Fred head shown that in Prime 3.0 it works OK

 

PTC is not very interested in bug reports.

In fact you have to pay for the privilege(!) to send a bug report - only if you are under maintenance you may open a support ticket an report that bug.

 

L
LucMeekes23-Emerald IV
23-Emerald IV
April 26, 2018

And then it may take a while to get fixed...

 

Success!
Luc

Terms & ConditionsCookie settingsAccessibility statement