@vv I started from noticing,

   sum(sum(1/i,i=1..n)/n/(n+1), n=1..infinity);
   expand(%);

rather than with your observation.

I will submit a report against the weakness.

I often delete several spam posting at night, but I've skipped the past few nights.

I've noticed that this site's spam-filter seems to miss more AI generated spam postings, and those seem to have become in vogue.

@Christopher2222 The `size` option is now handled by all the 3D plotting commands in exactly the way that other old (2019) Post addressed (for plots:-display and plot3d).

It offered no other functionality in regards to your current query; it merely allowed the window `size` functionlity before it was officially incorporated.

That Post's code is completely irrelevant to modern Maple versions. Indeed, since that Post's code does a hot-rewrite clobber of Library routines you shouldn't use it in any modern version.

On a somewhat related note, I recall that I once wrote this, to mimic independent aspect ratios for axes of a particular flavor (implicitplot3d) of 3D plot.

That's not the same as the zooming thing for 3D plots, but the two topic intertwine, in practice.

I don't actually believe that a pure Library-size solution is possible, despite having written that old Post. What I suspect might be best would be wholly new elements of the PLOT3D structure, which would denote to the (GUI) plot-renderer what axes-aspect-ratios and scaling/zoom factor to use. Those substructure elements would, naturally, be constructed via new options to the relevent Library plotting commands.

@C_R There is a form for it, here.

Whether it goes through the form, or though tech support, it ends up in the same bug tracking database system (and for which triage assessment gets items assigned to the appropriate developer or group).

In your example, this expression (as well as the values substituted into it) does not depend on x,

    rhs(isolate(de5, diff(p(x), x)))

And that's what's used for the vertical (second) component in your plotted points.

It doesn't depend on x, and it doesn't vary with x.

@salim-barzani Please put your followup example for this here, not in a wholly separate and new Question thread. A separate Question thread on this will be deleted.

So, was this the effect you were after, in the sense of avoiding unwanted fractions?

nb. Some more cosmetic improvement could be had by rearranging terms in sums, so that fewer leading terms have a minus sign. I have several variants of code that do this, and can handle this example. (This example is useful because some coefficients in the collect call have opposing needs for sort re-ordering. So no single sort call applied to the whole expression might serve. I have a prototype of a routine that runs through the sub-term sums individually, figuring out a "nice" term re-ordering, in a coefficient-by-coefficient way. Maybe I will make a Post about it. Let me know if you just want a one-off to further beautify this example sooner/now.)

Which fractions do you object to?

Which expressions are you wanting to export?

@vv I thought you might enjoy this (forced) variant, done in Maple 2024.2,

Download nm_simp_exB.mw

@vv That's nice, short, and easily understandable. (vote up, naturally)

In Maple 2025.0, without the factor@expand,

> kernelopts(version);
   Maple 2025.0, X86 64 LINUX, Mar 24 2025, Build ID 1909157

> A := -x*(x - 4*exp(x/2) + 2):
> B := x*sqrt((-8*x - 16)*exp(x/2) + x^2 + 4*x + 16*exp(x) + 4):

> simplify(eval(A-B,x=2*t)) assuming t::real;

                0

In Maple 2024.2 it doesn't need the substitution,

Download nm_simp_ex.mw

@nm Why not consider it a sympy weakness?

What does that O(..) term represent there? Is it so useful, that its presence/absence might not be used for some addititional programmatic leverage?

Please put your queries in a "Question", rather than a "Post", in future.

I've changed this one to a "Question", for you.

ps. Yesterday you submitted two Posts for it, concurrently, with the exact same content, before any moderator touched either. There's no need for that.

@zenterix You had several flavours of plot call. If you run into issues for any of them then you can come back to this, and force it with these options.

@segfault When my Java GUI locks up, and it won't close down using its window's corner icons, then I kill the parent java process in my OS.

That usually also kills its child mserver processes, but if not then I kill those afterwards

ps. Since I sometimes run multiple worksheets (some of which I really don't want to die if any other worksheet freezes the GUI) I use an option to allow wholly separate Java virtual engines. I do this by adding    -standalone   after the executable call string in the Properties of the desktop icon that can launch the Maple GUI.