After you have executed a Document Block, select all of it, both input and output. (You can use the mouse pointer to left-click & drag, or Ctl-Alt-Shift-D, or right-click in the border if your have the Markers visible.)

Then use the menubar item,
   Edit -> Document Blocks -> Toggle Input/Output display

That allows you to hide the input of a particular Document Block (as opposed to, say, all input in the sheet).

It's a little awkward to undo the effect, though you should be able to use the "Show Command" item from the same submenu.

That works for me in Maple 2019 without having to encapsulate in a Table (which has its own mechanism for this kind of thing). 

[edit: presumably you have some other examples to cover, with some general action, or else you could just square both sides, trivially...]

How do you feel about using the isolate command here?

restart;

eq:=sqrt(y)=tanh(x):

isolate(eq,y);

                           2
                y = tanh(x) 

Or perhaps you might be able to get by with temporarily substituting or freezing the trigh terms (but be more careful if you need to preserve the explicit dependence on name x, for subsequent or intermediate differentiation, say).

thaw(solve(subsindets(eq,trigh,u->freeze(u)),y));

There is quite often a balance between terse syntax and higher performance. By this I mean the contrast of short syntax against rewriting such operations in just one or two (evalhf'able or Compile'able) procedures that are verbose but very efficient in memory and computation time.

But here are some ideas. (I used Maple 2015, on Linux.)

I found it interesting that the original elementwise action of pi0 and pi1 on float[8] Vector Q would not produce a float[8] result. So I forced that -- saving some time and memory -- by using map[evalhf] instead, for which I had to reverse the order of their parameters. (Sometimes such a result does attain, with a builtin action, say. But not this pi0 & pi1.)

I have stopped well short of rewriting everything (except the Sample calls) in one  big evalhf'able/Compile'able procedure. There can be diminishing returns in such effort.

Download MakeItFaster_ac.mw

If you have to repeat the whole computation several times, then the "memory used" number can have more effect (because it alludes to how much memory management is going on). Lower is better, even if the wall-clock timing is otherwise the same for a run. I used some in-place operations, to reduce production of collectible garbage within the procedure. There are several choices in how to go about that. But I didn't do a variant where Q is reused as the third argument to Sample, etc. Refactoring the code to use the fewest number of separate Vectors is another diminishing return, and can forsake readability.

There are several mistakes.

The syntax mistakes mostly relate to plot, assignment, etc, rather than to the Explore command.

You forgot the colon in the assignment syntax, for P, and so didn't actually assign to anything.

The syntax for the plotting command is strangely wrong. (Is this a cut&paste of something else?!)

It's difficult to guess what you mean by the data values for plotting. Which are the independent values? What is ()...() supposed to mean?

You forgot to assign any numeric values to M_0, M_1, k_0, and k_1.

You appear to have shown us something like an invalid plaintext version of some 2D Input. That's no good. Upload your actual worksheet, instead of doing that.

I can guess what sort of thing you intended for the data. I made a short guess. The following works, and you should be able to fill in the missing data. (If not, then upload your worksheet.)

explore_plot.mw

With a call to Table (from DocumentTools:-Layout) you can pass calls to Column (same package) and specify the `weight` option.

It takes as many Column calls as there are columns (counting span). The weights are relative to each other.

Let us know if that's not your context.

You can get the comparison using Units:-Simple instead of Units:-Standard, although zero meters is still just zero.

Download UnitsStandardCompare_ac.mw

[edited] I've deleted my answer using the CenterOfMass command, as I overlooked the coordinate system and made an unfortunate choice for the integration bounds (related to the square).

Tom's done it in his own Answer, now.

Let me know if this is close to what you are after (or if it needs adjustment).

Download mat_polycoeff.mw

Perhaps this will help. (I'm not sure whether it is good for your purposes...)

Download HasChild_ac.mw

Here is one way,

Download PMSM_eq_ac.mw

[edit] The following is shorter (only because it avoids having to dispel the constant of integration), but it seems slightly odd (to me) to ignore the dsolve command entirely.

IntegrationTools:-Combine(solve(value(map(int,PMSM_v_eq,t)),
                                {lambda__alphabeta(t)})[]);

It's not clear from your question how you want to treat multiple (or nested) solutions coming out of solve, as your only example is simple. I could guess...

Download solve_removal.mw

@coopersj The default behaviour of the 2D Input  ||V||  should match the current context's behaviour of Norm(V) , in the case where neither explicitly specifies a particular norm.

Of course, each should always be available -- if provided explicitly -- so as to clarify the situation if the nature of the worksheet's material and content make the context non-obvious. And so they are. I used command-completion on the word "Norm" whilst in 2D Input mode, to select a specified norm from the popup menu.

Download norm_LAVC.mw

One way to get the results without the x is to change how you call fsolve, ie.,

f := x^2-x+0.25:

fsolve({f=0}, x=0..1);

     {x = 0.5000000000}, {x = 0.5000000000}

[fsolve(f=0, x=0..1)];                          

         [0.5000000000, 0.5000000000]

Your first question about "storing" the results is unclear. If you assign the last result about to S then you can access each root by indexing, eg,

S := [fsolve(f=0, x=0..1)];

          S := [0.5000000000, 0.5000000000]

S[1];

                  0.5000000000

S[2];

                  0.5000000000

Under the location of my Linux installation of Maple 2020.1 there is a file (relative path):
   bin/Maple2020.png

That is a 1-layer 48x48 pixel RGB color space PNG image, at 72x72 ppi and a print size of 16.93x16.93 mm.

You could try scaling that up in size (after making a copy of the original file).

Of course, the final behavior is up to your twm window manager.

The simplest way to switch the orientation roles is to use the parametric calling sequence of the plot command.

plot([y^2, y, y = -3 .. 3],
     color=blue, thickness=3, title="T1.1 x=y^2 [ECE]",
     view=[-5..5, -5..5]);

I don't care so much for the three choices Tom mentioned. The rotate example involves more typing, a little extra computing, generates a temporary plot as collectible garbage, but is otherwise ok. Solving/inverting the expression analytically for all branches is problematic in general. And implicitplot is inefficient (compared to a direct plot).