@JamesK I find your error message very strange. What command did you give? It looks like you might have given that command ModuleApply(...) rather than FunctionToTree(...). Can you post a worksheet where you get the error?

If you've downloaded the worksheet I attached, then you need to "Execute Cute" in the Code Edit Region. Put your mouse in the box that contains the code, right click, and select Execute Code.

@JamesK I find your error message very strange. What command did you give? It looks like you might have given that command ModuleApply(...) rather than FunctionToTree(...). Can you post a worksheet where you get the error?

If you've downloaded the worksheet I attached, then you need to "Execute Cute" in the Code Edit Region. Put your mouse in the box that contains the code, right click, and select Execute Code.

@JamesK I just posted a module with the required functionality in your followup thread.

@JamesK I just posted a module with the required functionality in your followup thread.

@PatrickT The smoothness of the Postscript export does make the source of the problem seem to be something more akin to pixelation than to, say, numerical instability. I noticed that the problem was still there upon export to JPEG, which usually has a smoothing and blurring effect. Would someone who has a printer please print the original "jagged and nasty" plot?

@PatrickT The smoothness of the Postscript export does make the source of the problem seem to be something more akin to pixelation than to, say, numerical instability. I noticed that the problem was still there upon export to JPEG, which usually has a smoothing and blurring effect. Would someone who has a printer please print the original "jagged and nasty" plot?

Isn't that just the derivative with respect to x?

Download diffdiff.mw

Would someone who works for Maplesoft please comment on this?

• Is Maple IDE an officially sanctioned Maplesoft product?
• If it isn't, why are you letting them get away with abusing your trademarks?

@spradlig I use Classic to open very old .mws worksheets. All I do is open them and resave them, and then I can open them in Standard. That's all that I use Classic for. However, I can think of two other reasons why someone might want Classic. The first is that the spacing of the characters in the math output of Standard is often too wide or misaligned vertically. Thus it is harder to read. The second reason is that moderately long output that Classic can display virtually instantaneously can take inordinately long to display in Standard, and very long output very often causes the GUI to crash completely.

@spradlig I use Classic to open very old .mws worksheets. All I do is open them and resave them, and then I can open them in Standard. That's all that I use Classic for. However, I can think of two other reasons why someone might want Classic. The first is that the spacing of the characters in the math output of Standard is often too wide or misaligned vertically. Thus it is harder to read. The second reason is that moderately long output that Classic can display virtually instantaneously can take inordinately long to display in Standard, and very long output very often causes the GUI to crash completely.

Several times I have had a complete loss of kernel soon after receiving this error. So, I don't think it can be so safely ignored.

Several times I have had a complete loss of kernel soon after receiving this error. So, I don't think it can be so safely ignored.

And remember to click Apply Globally at the end.

And remember to click Apply Globally at the end.

@sakhan To get all the nonlinear terms at once, first get the linear terms and the constant terms and subtract from the original. What's left is the nonlinear terms.