@Carl Love I wish I'd thought of it earlier.

@Christopher2222 I submitted a bug report related to this a few years ago.

@tomleslie Yes, and now you've obtained a method that is essentially the same as what dharr showed earlier (as in the examples,Explore help page).

[I'm not suggesting that you haven't come up with this all by yourself. I think it's the natural way to approach it efficiently. I'm pretty sure I've seen Preben do the same thing. I've long wanted something like DEplot to offer the same flexibility+efficiency.]

Please post your followups to this thread here, instead of entirely new Question threads.

To get the visual effect of subscripted text (but not as output) you might have to toggle into non-executing 2D Math input mode and manually flip off italics from the menubar.

@Christopher2222 It looks as if his question is about how to enter it as input, while your answer is only about how to produce output.

Moreover he seems to want a subscripted/superscripted bit of "text", which I interpret as meaning something formatted in upright roman font. So mi is not the right typesetting markup for that.

I don't see how your answer relates properly to this question at all.

@dharr Vote up, because this shows dsolve being called only the one time.

The help page referred to is available in the Help system under the topic examples,Explore

@ebrahimina I much prefer to have multiplication show explicitly, even in 2D Input. Relying on a space to denote multiplication implicitly often leads to confusion and mistakes. But in this case the * appeared when I copied and pasted, I suspect. [edit] I have revised my Answer to use the unitless range 0..100 since the calls to tau and Q already contain argument x*Unit(mm). [/edit]

Did you have a second followup question?

On the topic of style, I also dislike using the syntax Q(x):=...  to denote assignment of an operator, but I forgot to change it when replying. That syntax is ambiguous and can also be used to denote assignment to the remember table of Q. And ambiguous syntax is error prone. I much prefer the syntax Q:=x->... 

By the way, I used Maple 2017.2 in my Answer, since the OP's original attachment was last saved in Maple 2017. I also tried to write the answer so that the OP could use his original definitions of Q and tau, as is, and call plot without having to strip or cancel out the units.

Start by giving us proper details.

Stop spamming this site with your homework questions.

Put all your homework assignment questions into a single Question thread, if you really can't be bothered to learn basic Maple syntax or work out even the simplest problems yourself.

@mmcdara Using Maple 2016.2 so as to get Statistics:-HeatMap, here is some overlaid colored mixes of plaintext and 2D Math.

It uses a procedure that colorizes or enboldens typeset representation of math expressions or strings.

Download color_math_HeatMap.mw

I've written such a procedure several times over the years. I agree with you that it can be useful. Let me know if it requires tweaking. I think I wrote this particular one so as to get mixed colored captions on plots.

On the help page for DocumentTools:-Tabulate the first sentence in the paragraph where it describes the color option says, "The foreground color for text."

I interpret "text" as meaning entries which are strings and not expressions. Which means that the behavior is just as documented. Not a bug.

It would be nice to also have control over typeset 2D Math, as a functionality enhancement. One possible scenario would involve the existing color option also affect typeset math, with an additional option (say, typesetcolor) which could override that.

@DisabledWhale That 2D Input syntax for operator assignment that you are trying to use is highly ill-advised.

I have suggested several alternatives which work properly and make sense in the Maple programming language. Those alternatives work in both 1D and 2D input mode. They do not use ambiguous syntax. They do not rely on settings in the GUI or worksheet, and as such will work the same if re-run later by you or others.

The 2D Input syntax for operator assignment that you are trying to use, has several significant problems. It is ambiguous and clashes with remember table assignment, and in 2D mode you or anyone else cannot immediately discern which meaning is there. That 2D syntax is not universally the same in all recent versions of Maple. You or others may well have problems figuring out at a later date what you intended. The syntax that you are trying to use has a history of causing problems, is difficult to figure out, has been implemented suboptimally, and is implemented inconsistently across versions.

But you want to use that particular 2D Input syntax for operator assignment anyway. It's not that I don't want to help you with that, but rather that I am unable to properly help you with that. Nobody can properly help you with that because it is generally unworkable, so even if you figure out this particular question it will give you problems later.

@jmalik7 That agrees with what I wrote before.

Your approach has at least one mistake, since you define W using symbol w before you place assumptions on w[i,j], and more importantly because you have no assumptions of, say, realness of the y[i,j].

But if set up more suitably then I suspect that you may receive a result of FAIL from is, which doesn't help. Even this happens, it seems:

is((y22 - y12)^2>=0) assuming real;
                         true

is((y22 - y12)^2+b>=0) assuming b>=0, real;
                         FAIL

is((y22 - y12)^2  + (y21 - y11)^2>=0) assuming real;
                         FAIL

So even if you simplify as follows it may be that is has issues dealing with it.

K := simplify(Trace(simplify(Transpose(Y) . (d-W) . Y))):

collect(K,[w[1, 2],w[1, 3],w[2, 3]],Student:-Precalculus:-CompleteSquare);