ACCEPTED SOLUTION
Accepted Solutions
Thats strange, I get the same error if I open my attachment but not if I open if from my HD. The problem is easily corrected by simply letting the sheet recalculate (Ctrl-F9).
For whatever its worth I resaved the file and attach it here,
In any case you should see something like this:
Thats strange, I get the same error if I open my attachment but not if I open if from my HD. The problem is easily corrected by simply letting the sheet recalculate (Ctrl-F9).
For whatever its worth I resaved the file and attach it here,
In any case you should see something like this:
no, it does not work on my system for some reason...I have the same windows xp Mathcad 15 M020 as well...and I am not able to post a screen shot for some reason. I attached it as a PDF...here you go!
Thats really strange - I have no clue. I guess retyping part of the last expression, the call of pdesolve will not solve the problem either.
The errormessage itself is odd, too. The only parameters which have to be integers are the last two. These parameters are optional, so you could try omitting them and see if the error still is thrown.
I have now tried a few times but I am not able to reproduce that error again, but i experienced it twice by opening my first attachment. I must confess that I didn't pay attention as to what the error message was, so I can't confirm it was the "integer" one. The first time I deleted the 0.33 and retyped it and all was OK. The second time I simply recalculated the sheet and the error was gone. Since then I was unable to reproduce that error by downloading my first file.
If nothing helps and if nobody else comes up with any good idea, I would suggest - silly as is it may sound because this suggestion usually indicates the advisor has no clue what to do (as is the case here, too) - to reinstall Mathcad. 
Is Pdesolve() the only command you encounter problems?
So, I have reinstalled it. This is strange! So when I open after resinstalling it, it works fine! The equation solves and I can see the graph. However, a reboot warning came and I hit restart. After restarting, it reverts back to the old where it does not solve. Its absolute rubbish! I am guessing some software compatability issues may be?
So I reinstalled it again, and this time did not reboot!
After restarting, it reverts back to the old where it does not solve.
Thats absolutely enigmatic and mysterious. I can't think of what piece of software could cause this behaviour!?
So I reinstalled it again, and this time did not reboot!
Hmmm, guess this can't be a permanent solution. So you have a fine puzzle to solve.
I don't clearly remember so I am not absolutely sure, but I think that the installation of MC15 did not require a reboot. So the reboot message you got could be because of an automatic OS update. After all we just had Microsoft patch day (every second tuesday of the month).
You could use the excel component or one of the various READxxx and WRITExxx commands (WRITEPRN, WRITEBIN, WRITEEXCEL).
See attached the file using READ/WRITEEXCEL as I thought it might bw useful for you to manipulate/graph the data in Excel, too.
The values for a selectable number of t-values (equally spaced from 0 to 500) are written to an Excel file and immedeatly read in again and plotted.
The idea is that if your solve block failed, the matrix which should be written is undefined and so no file is written. That way the file from the last successful run is read in and displayed. I attach the Excel sheet from my run, too. The file is setup so that it writes and reads the Excel file to/from the same directory as the Mathcadsheet is in. Thats the reason I deactivated automatic calculation so you can change the location the file is saved to first.
But working with that kind of tricks and reinstalling Mathcad after every reboot can't be a permanent solution, You may consider contacting PTC support (even though it looks to me that the problem is not Mathcad itself).
EDIT: corrected typo in file and added 3D. Thought it would be appropriate
Also enabled autocalc again but disabled the WRITEEXCEL command for the same reasons as explained above.
