How many rows and columns of plots do you have in a Table?

Are they 2D or 3D plots?

Do you wish to avoid page-breaks between Table rows, in the printed export?

What's the smallest fraction of a page-width you'd want to see for any individual plot?

What version of Maple are you using?

Do you use plots:-display to show an Array of plots in a GUI Table?

Do you use the size option (for 2D plots)?

Do you use the legendstyle option to control the font size?

Please consider uploading an example, to give a better idea of the intended layout.

What (roughly) is the geometry of your Maple GUI window, in which you'd also like things to look reasonable? Can we suppose that obtaining nice layout in the printed export is the most important thing here?

acer

@Markiyan Hirnyk The problematic result that the OP showed may be reprodced with something like,

evalf( solve(convert(Eq1, rational, exact),diff(y1(t), t, t)) );

There is no fool-proof way to decide what is best, without complete knowledge of the particular floats present. Using convert(Eq1, rational) produces a solution to a slightly different problem, and is an approach that may or may not be better in general. It's important to note that it is solving a different problem, even if in this particular case it is clear (by manual observation of the floats in question) that it will deliver well.

For example, if the float .2916666667 in Eq1 had instead been 0.7071067812 then it might be more desirable to instead use convert(identify(Eq1), rational) which would recognize that as 1/sqrt(2). If that float had instead been 0.5432154321 then convert(Eq1,rational) works on a different problem with that float converted with an error of 1e-10, 1 ulp. Using isolate rather than solve works for the given problem without producing as many lengthy factors, but of course that approach may presuppose that the data is "accurate".

There is no perfect solution to such issues in general, which (by the way) is why symbolic dsolve offers several choices of float conversion mechanisms via options.

Perhaps another good suggestion for the OP would be to also try and introduce floats into symbolic equations as late as possible. This may not be possible in the case of measured data, of course.

@gordon the grey Before we try and figure out how best to make it happen for each such session, what effect did it have in a given session?

I mean, did it have any effect on the copy&pasted (Maple) results that showed up in Matlab, after it was done, in the same Matlab session?

@Ieva I'll see what I can accomplish in Maple 13, possibly this evening.

It seems useful and prudent to me to mention in advance that you're using software that is six major release versions out of date (2009), when asking for a technical solution.

I used Maple 18 when I ran the code I gave (2014).

@Alger Is this close to what you want?

Download polnew.mw

It works OK for me, without any workaround needed, in the 64bit verion of Maple 2015.0 on Windows 7 Pro.

It would be interesting to know whether it's specific to Win8.1, or 32bit Maple, or other.

acer

@Alger Please explain in more detail what you mean.

@Alger I don't see why what I gave does not do what you've asked.

Here below the colors red and blue are switched, as you have them.

You write cos(theta) but perhaps you intend cos(freq*theta), for some freq. You write you want the axis to be at radius R, but your image shows a curve entirely within the circle. That's obtained by just adjusting my code by 1, in the axial direction.

Please explain more, if it wasn't actually what you wanted.

Download algerplot.mw

@Christopher2222 Yes, that was the first of the three plots I showed by example.

@Kitonum I could be misunderstanding of course, but where the OP wrote ".mw" I interpreted it as meaning a query about behaviour in the Standard GUI (as opposed to .mws which I might interpret as a query about behaviour in the Classic GUI, or both).

Which style: detached, grouped, or stacked?

acer

@mapleatha it worked fine for me, using the Java GUI of Maple 13. Why don't you describe exactly what you're doing, and in which interface and input and output mode, instead of just wasting time?

Here's a screenshot of it working for me in 64bit Maple 13.02 on Windows 7. Earlier in the day it worked for me using 64bit Maple 13.01 for Linux.

@nm Using a DOS window under Windows 7: (This is one long command, of course. I split it across two lines of text here just so that it displays nicely in this post.)

c:\TEMP>"C:\Program Files\Maple 18\bin.X86_64_WINDOWS/cmaple.exe"
         -q -c "print(int(sin(x),x));" -c "quit"

                                    -cos(x)
c:\TEMP>

Using cygwin (and this one also worked using /cygdrive/c/ instead of c: in the fully qualified location of cmaple.exe): (Again, this is just a one-line command.)

$ "c:\Program Files\Maple 18\bin.X86_64_WINDOWS/cmaple.exe"
  -b "c:/Program Files/Maple 18/lib/" -q -c "print(int(sin(x),x));" -c "quit"

                                    -cos(x)

Those worked for me with Maple 2015 as well.

@mapleatha Why are you not updating to the 13.02 point-release?

There is an item "Startup Code" in the "Edit" dropmenu off the main menubar of my 64bit Maple 13.02 running on Windows 7.

What operating system and particular point-release Maple version are you using?

acer