@Muhammad Usman I just updated the Answer so that it also displays the symbolic summation in sigma notation.

@ianmccr I'm not sure if you're saying that you still don't fully understand the syntactic distinction between evaluating a procedure and executing it. If so, I think that the key distinction is that to execute a procedure, you must give it an argument sequence (which could be the NULL (or empty) sequence). This is usually done by putting a pair of parentheses containing the argument sequence next to any reference to the procedure, evaluated or not. So, if your procedure is in table T (exported from module M) at index P, it could be executed by

M:-T[P]();

@Annonymouse Could you give an example of what you mean by "setting up the options for plot3d"?

@raskr Could you post a Maple 2017 worksheet showing this? I don't have Maple 2017 to check. But certainly in both Maple 2016 and Maple 2018---both of which are open on my desktop at this very moment---and in several earlier editions, interface(displayprecision) sets the number of digits to be displayed after the decimal point (which is ridiculous, except perhaps in a financial context) and does not affect the number of significant digits displayed. So, I'd be surprised that Maple 2017 was the lone exception.

There is a size option to plot, for example,

plot(sin(x), x= -Pi..Pi, size= [1000,500]);

The numbers refer to the number of pixels.

@Adam Ledger Ah, yes, this new series of plots is much more interesting!

This is just a mathematical aside, unrelated to your font issue, which I don't know how to solve.

Are you talking about ordinary integer arithmetic here? Then x*y is necessarily divible by gcd(x,y), so floor is redundant. Furthermore, that quotient (when nonnegative) has a standard name: least common multiple, or lcm.

@MapleMathMatt A potential problem with your approach is that if a name u has multiple layers of indices, then op(0,u) only strips off the outer layer, returning a name that's still indexed. For example,

op(0, x[a][b]);

@Carl Love I tried to do the (7,7) case on its own. It's too big. After it used about 11G of memory, I killed it.

I got a "kernel connection lost" error, which could be a memory error, when trying to do the full 7x7 matrix. Would you please attempt to do the (7,7) case separately, not as part of a matrix?

curry is trivial. Here's a brief explanation. Suppose you have a procedure/function f(x,y) and a particular value of x, X. If g:= curry(f, X), then g(y) = f(X,y) for all y. The benefit is that the y has been moved to the first argument position.

:: is fundamental, but not so trivial. X::t (outside of a procedure header) is the same as type(X,t) used in a position where a boolean value is required. It returns a true/false value that answers Does object X have property t? (I'm using property in its generic English meaning rather than its special Maple meaning. Maple-speak refers to t as a type. Maple properties are related, but nowhere near as important as types.) There are several ways that X::t can be used inside a procedure header, but they all essentially mean Return an error if an attempt is made to replace X with something that is not type t.

@Muhammad Usman So, you don't believe that evalm was causing the problem? Try replacing &* with . and putting evalm back in.

@Annonymouse The final two lines of the code snippet that you quoted, when displayed the "normal" way, are

nops~(M)
plots:-matrixplot(nops~(M), heights= histogram);

The first line of that pair needs to end with a semicolon. Without it, the 2D Input interprets it as a scalar product of a matrix of integers and a plot. Amazingly, this is not an outright error! It actually produces and displays a matrix of plots.

@tomleslie I've directly downloaded your attached worksheet "mine.mw" into both Maple 2016.2 and Maple 2018.1 and used the menu command Edit -> Execute -> Entire Worksheet. In both cases, I got no errors. I also suspect that this is some 2D Input issue.

@Muhammad Usman I still see two usages of evalm in your worksheet. There's no good reason to ever use evalm. The only reason that it's still in the Maple library is so that some very old code will still run.

@rhcp Thank you. No problem; I'm happy to help you. Let me know if you need any further assistance.