@RezaZanjirani Your last Reply has no attachment.

@RezaZanjirani In my code I made it take the first solution from solve.

Your situation might be better handled as an optimization problem, ie. maximize this new (as yet unstated) objective function, with the original equalities/inequalities as constraints. And, for speed, it might be formulated as a floating-point numeric problem.

Prior to this, you've created several separate Question threads on this (or very close) topic. Please don't spawn any more wholly separate new Question threads on this. Duplicate Question threads get flagged as such and may be deleted.

You could add your followup queries and details to this or an earlier relevant Question. I suggest providing as complete and detailed a description as you can of your eventual goal and motivating example as you can, even if you don't yet have prototype Maple code to solve it. That'd be much more useful than, say, slowly approaching your actual goal by a set of partial reveals of details & code attempts.

@RezaZanjirani You could construct the legend entries programmatically, as some function of the delta values. For example, HmaxProc_ac2.mw

Or you could simply construct them separately, by hand.

I don't know whether your "TEXT" has to vary with the delta values, and if so, how.

IIRC the X11_defaults/Maple file was used by the Classic GUI, which isn't really available any more for Linux.

There is a resources file used by the Java GUI, named like (version specific),
    ~/.maple/2023/maplerc
but I don't think that allows for much color configuration aside from the line like,
HelpBGColor=255 255 255
which I think specifies the background color for the main window portion of the Help viewer.

I have deleted yet another duplicate Question thread on this doCalc procedure.

If the OP has further followup queries or details on this then they can be added here, instead of in wholly separate new Question threads.

@minhthien2016 

Download inert_exa.mw

@minhthien2016 

Download inert_ex7.mw

(or, in steps as before, inert_ex6.mw)

@minhthien2016 Once you have a process that works on a single data list, you can make it into a reusable procedure to work easily on multiple data lists.

Download inert_ex5.mw

@minhthien2016 Like this?

Download inert_ex4.mw

Please put your close followup examples here, instead of spawning wholly separate new Question threads on the same topic.

An example:

Download inert_ex3.mw

@tim_finks It was unclear, because your Question here had it as the opposite:

   solve(f=ma,a)

with neither a space nor a multiplication symbol.

Did you enter it as a multiplication, ie. either explicitly as m*a, or implicitly as m space a?

If you entered it as just ma then that's a two-letter name, not a product of two names.

@minhthien2016 You can show the first such equation by,

   Display(temp[1], inert=false) =~ value(temp[1]);

and similarly for the 2nd and 3rd.

You can get all three such equations more directly, in a list, by,

   Display~(temp, inert=false) =~ value(temp);

nb. I made a slight ajustment to the original, to utilize Display~ in that elementwise manner, so that its result is still a list.

@Carl Love That multithreaded variant acts in-place on separate portions of the input Array E, which I believe is why there's little-to-no addtional memory usage overhead.

I added option threadsafe to EasterC_Mpl, so that its compiled result EasterC could run in parallel tasks, ie. so its external call was non-blocking. (See ?Compiler) That'd be needed for other kinds of Threads approaches.

I like splitting the tasks with my own routine, so that I can try and tweak the split. Sometimes using numcpus itself seems not quite optimal. Maybe there are also cache effects...

I only mentioned the bookkeeping because I made a slight adjustment to EasterC_Mpl's loop (k from BEGIN to END), and I'd had just the one coffee. That seemed simpler than fiddling with the Array indexing. It seemed reasonably straightforward because EasterC_Mpl already had the useful BEGIN & END parameters.

Your code assigns a procedure to F, so your attempt like invlaplace(F, p, t) doesn't make too much sense.

Did you perhaps intend invlaplace(F(X, Y, p), p, t) instead?

(I mean, after fixing the weird 2D Input issues with the arguments. Try it in 1D Input.)