@Andiguys Your new data lists don't have the same lengths as each other.

So it complains when you try to use them together as (column) Vectors; one is too tall or too short.

@Andiguys Did you delete one of your previously answered Questions?

(It would have been posted around Jan 30, on maximizing an objective containing a piecewise, then plotting wrt variable `e` and `delta`.)

The magenta error message in your last attachment clearly indicates the nature of your mistake.

@Andiguys A single underscore means nothing special to Maple.

But a double underscore in a name tells the GUI to pretty-print it (2D Output) with an subscript.

So, instead use  C__v with two underscores.

If you've assigned a name to that variable, then one way (of several) to prevent evaluation to the value would be to wrap with single right-quotes  'C__v'  or  ':-C__v'

You asked about subscripts in labels on January 20 (two weeks ago). See my Answer here.

ps. Did you delete one (or more) other question of yours, from the past month, including one from around Jan 30, relating to optimization with an objective containing a piecewise?

@Andiguys As I showed before, you can add,

   labeldirections=[horizontal, vertical]

to get the x-axis label horizontal and the y-axis label vertical.

Adding the option,

   axes=box

to a regular kind of plot makes a box, instead of just the two (vertrical and horizontal axes being open.

You can find explanations of these options for 2D plotting commands on the Help Page with topic plot,options

@Andiguys I use "\n" the new-line character to pad the axis labels, so that they don't crowd in too close to the axes. Adjust to taste.

You can also add your own choice(s) of view to either P1 or P2, separately, etc.

The easiest way to exclude some of the left data values is to just chop the block off, by simple indexing.

Andiguys_dual_ac4.mw

This revision has distinct legend entries, so that the curves of the same color can be distinguished properly. (The pointline style isn't properly supported by the GUI, for legend items. So I fake it here by duplicating with both line and point styles separately done).

I'm only content to use the same color for the curves as for the two vertical axes.Without that distinction there's little visual cue at all to show which axis relates to any given curve. (See later example below, where the axes labels provide a cue -- unsatisfactory, IMO.)
nb. The GUI always merges all the legend entries of a dualaxisplot, which is a shame. The Library code allows construction of a PLOT structure in which one axis's info specifies its curve's legend entries to have location=left, while the other axis's info specifies legend=right for its curves. But the GUI still renders them all at one spot. So a split pair of legend boxes cannot serve as the visual cue for which curves go with which vertical axis. A shame.

Adjust with your favour point symbols...

Download Andiguys_dual_acc.mw

And here is the idea of using labels on the two vertical axes, as a way to give a cue as to how the curves related to the scales. (I find this awkward; one's eye has to match by doing a triple-step: A curve to its color, then the color to a legend entry, and then the legend entry's name to one of the vertical axis labels. oof.)

Download Andiguys_dual_accc.mw

@Andiguys You could adjust the following to your taste (I just made it, before seeing your latest attachment...)

The first example runs from X=70000..95000, and the second  runs from the 3rd data point, ie. X=75000..95000. I wasn't sure what kind of vertical view you wanted.

I can adjust the colors/styles a little, so that the legends entries are distinct.

Your latest attachment did not follow my earlier instructions. I wrote to combine a pair or usual plots (each having two curves), into a single dualaxisplot. Instead, you created two dualaxisplots and have asked how to combine them. That's not the right way to get the effect you appear to be after.

Download Andiguys_dual_ac.mw

@Andiguys I showed you (three days ago) how the dualaxisplot command can be used to nicely show data from two different scales.

In my example from that link I used a color for the curves and two vertical axes, to make the correspondence more visually clear.

I'm not going to retype this data into Maple. You can upload it in a worksheet if you'd like me to show these four in an explicit example.

If you want two columns for each vertical axis then you can do it as follows:
 1) Make two usual plots, each with 2 of the curves in them (ie. pairs whose scales agree). Or put 3 curves in one usual plot, and 1 curve in the other. It depends on which columns share a scale.
  2) Use plots:-dualaxisplot to combine both those plots.

@Ali Guzel  Does your response mean that you are not going to provide any representative piece of code that illustrates the issues?

By the way, are you trying to simply paste 1D plaintext code from Heck's book into 2D Input areas (Execution Groups or Document Blocks) in later Maple versions? That's not always possible. You should instead set up a Worksheet with 1D Input, and paste into that, as by far the simplest way to handle other's 1D source. (Using Code-Edit-Regions is a possible alternative, but IMO may well be more work-intensive&problematic&buggy.)

Do you have an example?

What was the last version in which the code could run, can you say?

What version was it written for, can you say?

Was it written for a version older than Maple 6 (released, year 2000)?

@segfault 

I pass the (undocumented) option,

   -standalone

to the maple or xmaple script. That makes the GUI start in a separate JVM. I do that for much the same reason as you describe; I want a crash in one Maple GUI session to not freeze up all my other open Maple GUI sessions. This options allows separate GUI launches to be run independently far as OS and Java RT are concerned.

The above is about running separate Maple GUI instances. (I also happen to run all my worksheets with separate Maple kernels/mservers, all within any single GUI instance. But this is a different kind of thing.)

@segfault You haven't stated where you installed Maple, or how you're launching it. But the principal scripts that can launch it are,

  $(MAPLE)/bin/maple
  $(MAPLE)/bin/xmaple

if, say, MAPLE were a Linux environment variable whose value were the location of the installation.

On my Linux I have the installation location as,
   /usr/local/maple/maple2024
but my choice is mixed arbitrary/convention.

If you forget where you have installed Maple (but can still launch it from an icon, etc) then the following Maple command will return that location:
    kernelopts(mapledir);

You could hard-code extra options in a script file.

If you launch the Maple GUI by desktop icon then you could instead edit that icon's source file's script call. I personally avoid desktop icons in Linux because their format/locations can change by distro and desktop environment.

Or, if (like me) you launch Maple from a command-line xterm window then you could simply add a shell alias for the call with extra options. That's what I did. I simply added the alias to my .bashrc/.profile file and it's available in every new shell/login/etc.

@Andiguys You could add the option axes=box at the end of the plotting command.

Or, just get rid of Kitonum's choice of axes = normal

You could figure this out by reading the Help page for 3D plotting options, ie. see the section for axes.

@Rouben Rostamian  It's interesting. Your attachment was last saved by you in Maple 2024.2.

I cannot see the pretty-printed Vectors in its output if I open that in Maple 2023.2 or older. But I can using Maple 2024.1, say.

I left your attachment link alone, but replaced the (problematic) inlined content in your Answer.

The OP seems to use Maple 2022. That version runs your attachment fine.

Have you looked at this Question, from October 2024?

Its Answer involved substitution, in particular using simplify with side-relations involving bilinear derivatives, etc.