Compare what you have done, with these choices for the tickmarks option:

tickmarks = [tickList, tickList, default]

tickmarks = [tickList, tickList, [0=0,1=1]]

tickmarks = [tickList, tickList, [op(map(rhs=rhs,rtable_elems(B))), 0=0]]

(The last two of those should give the same effect, for your B. I mentioned the last once only in case you later start putting in other values within B and want it to pick them up automatically.)

restart;

fseqn := (Se, f) -> Se^(f+1):

Vector(5, j->fseqn(2.1, j));

                      [  4.41   ]
                      [         ]
                      [  9.261  ]
                      [         ]
                      [ 19.4481 ]
                      [         ]
                      [40.84101 ]
                      [         ]
                      [85.766121]

Please try working with methods suggested for your earlier, very similar Questions, before asking even more on this theme.

Download another.mw

It's interesting that this works:

int(diff(f(x,y),x)*g(x)+f(x,y)*diff(g(x),x), x);

                          f(x, y) g(x)

For your goal, could you get dsolve to do it for you?

de := diff(K(x,y),x) = diff(f(x,y),x)*g(x,y)+f(x,y)*diff(g(x,y),x):

raw := dsolve({de}):

raw[1];

           {K(x, y) = _F1(y), f(x, y) = 0, g(x, y) = g(x, y)}

raw[2];

   /                                                K(x, y) + _F1(y) \
  { K(x, y) = K(x, y), f(x, y) = f(x, y), g(x, y) = ----------------  }
   \                                                    f(x, y)      /

solve(raw[2], K(x,y));

                  {K(x, y) = g(x, y) f(x, y) - _F1(y)}

The command LibraryTools:-Save is for storing in a .mla Maple Library Archive file. (And you'd first use LibraryTools:-Create once, to create the .mla file.) There is no corresponding "read" action necessary or relevant. But this does not seems to be what you're attempting.

If you want to save as plaintext in an .mpl file then you should use the command save instead and supply a filename which has the ".mpl" extension. In that case it doesn't have to be inside any special folder. You get it in future sessions using the read command.

The purpose of putting .mla archives within special folders under cat(kernelopts(homedir), "/maple/toolbox") is that those get automagically added to libname upon restart. The kernel finds things in archives in libname automatically, without any need for "read".

Placing your .mpl files directly within a toolbox lib subdirectory seems confusing to me, especially since there is no special benefit for doing so. It might be more logical to use a subdirectory named src instead.

Make sure your target directory exists.

You do not need to assign to the varuable names v1,v2,etc which would have the drawback that you'd need to unassign them in order to re-use then conveniently as names. You can accomplish the same effects using a list of equations or a table, either of which can be used to associate the names with the values.

This is a common and important usage scenario in Maple.

Download funcsubs.mw

The leading term is determined lexicographically (here, alphabetically, but where lower/uppercase matters).

And so what matters for -v1+a is the coefficient of a , while what matters for -V1+a is the coefficient of V1.  The capital letters are taken first.

Maple needs to use some convention in your usage case where no variable list is supplied as additonal argument. It might make sense (albeit tiresomely) to complain about the particular convention used, but it would make no sense to complain that it has to have some convention.

[edit] I should point out that for important efficiency concerns Maple stores only one instance of a polynomial in memory, regardless of whether it is entered as -v1+a or later as a-v1 . Moreover a polynomial can have its subterms sorted inplace in memory, but that structural change should not affect the result from sign which is mathematical. Therefore its leading term cannot be determined by the order in which you later re-type it or the order in which the subterms are stored in memory. So a convention that considers the leading term lexicographically lets things work.

restart;
p := -V1 + a;
                          p := -V1 + a

sign(p);
                               -1

sort(p,order=plex(V1,a),ascending);
                             a - V1

p;
                             a - V1

sign(p);
                               -1

sort(p,order=plex(V1,a),descending);
                            -V1 + a

p;
                            -V1 + a

sign(p);
                               -1

Since Maple 15 it is even easier to set the default unit for a particular dimension with the UseUnit command. I mean easier than having to use the commands AddSystem and UseSystem as you did above.

This allows other scales of power to be simplified to your desired kWh/day.

You can utilize it with or without loading Units:-Standard, depending on whether you want arithmetic with units to resolve/combine automatically. Or in recent versions you can utilize it alongside Units:-Simple, which does that automatic combining of units while also allow mixed arithmetic of quantities with units attached and unknown quantities (eg. names) without units specified.

Download useunit.mw

There are also facilities for right-click units re-formatting in the Maple 2018 GUI. You can also use that (or convert(...,units,W) ) to force display in Watts alone.

@primogen Have you tried,

Physics:-diff~(SimplifiedMassMatrixDot, theta[2](t));

a_ac.mw

I toggled this Question to be marked as "Maple 2017", since that's the release in which your attachment was last saved. (You had it as "Maple 17" which is four major releases earlier.)

I don't know of any easy way to handle 2D Input of units (ie. typeset via command-completion, or from the Units palette).

The following affects 2D Output. (I doubt it will work alongside right-click unit-formatting.)

Download unitcolorbold.mw

Download inertanother.mw

Download inertsurd.mw

The multiple assignment functionality was added in Maple V R5 which was released in 1997.

Have you tried,

display(Array([ display(A,B), C ]));

More importantly, Shouldn't you call it like,

Explore( P(a), parameters=[a=-1.0..1.0] );

so that it explores a function call to P?

Yes, you should be to accomplish this using Embedded Components, as long as the data exists before the plotting begins.

If you're hoping for an asynchronous process that sits there waiting for newly computed data points to be added to the file then the task is much more complicated (if possible at all).

Do you have a sample of data? What kind of plot do you want?