@C_R It fails for me if I don't use the not-evaluate quotes. 

@mmcdara Thank you for writing out a customized version of the H-type error bars. The penultimate example is perfect. (The final example is beautiful.) 

Sadly, your answer reinforces my belief that ErrorPlot cannot generate the traditional error bar in science through an option. Very few folks have the skill and experience that you possess, nor the time, to write code using CURVES, POINT and PLOT. Maybe a simple procedure could be added to the Maple Applications Center. (Maybe a summer intern can add it to either ScatterPlot.)

@nmacsai Another option is the plot option, "axes = frame".

@acer 

Thank you for the explanation of what is going on in the background. I believe I understand why Export failed, but plotsetup succeeded. 

And doing another eyeball test, I'm in agreement: PNG > GIF >> JPEG. This question generated a greater positive outcome than I expected. 

@mmcdara 

1) The key appears to be using plotsetup vs. Export. Appreciated.

2) Thank you for the suggestion of GIF over JPEG. I agree; if I zoom in quite a bit, the JPEG does show more fuzz than the GIF. 

Sadly, both formats change the tickmark font. 

@janhardo 

I very much appreciate all your work on this task. It has been sorely missed in Maple, IMO. And your work is well beyond my knowledge and capabilities. However, I do have a comment about the user experience. 

The goal of this process is for Maple to perform calculations and return the simplest expression based on some metric. 99% of the time, I will not ask Maple to return the best method selected. I will never add or remove methods. All I care about is for Maple to return a simple expression.

Hence, to that end, it is my opinion there should be only one procedure called 'Simplify.'  (Sorry, FullSimplify is too wordy.)   With the procedure, there should be options, not additional procedure names. For example:  "showmethodused", "usemethod = ", "sizemetric = {leafcount, size}" and "size" (or "expressionsize").  

Learning one procedure name and considering options within a procedure is easier than learning multiple procedure names. Consequently, the philosophy of the Maple language should be a procedure is like a directory, and each option is a subdirectory or file within the directory. Many procedures, such as "plot", work this way.

Again, I encourage you to continue your work but consider the simplified philosophy. 

(If you are completely wedded to the methods approach, and I can see some value for it, an alternative is to call the module Simplify and the main method Simplify.)

@mdenney Much appreciated! 

@ider I wish I knew. This interface problem involving 2D input and a couple of others are so annoying for me that I have not transitioned to 2024.  Fortunately, the problem has been reported to and reproduced by Maplesoft. We hope that with 2024.1, the problem will be resolved. Now, if you come up with a creative solution - please let us know.

However, I cannot tell if we are using the same 2024.0 build. Mine is 1767880. No change in matrix scrolling. 

To @janhard, @mmcdara and @acer - thank you for your contributions to this important topic.

While even I recognize "simplify" has improved during the past two iterations of Maple, this post pushes the project forward. A robust "simplify" procedure has significant pedagogical value.

@Ronan, I believe they are one and the same. See the help page.

@dharr Upvote for using ifelse and not the often mistyped `if` phrase.

Just an FYI, for efficiency considerations, the for loop can be reduced to a seq procedure:

A := [ seq( Matrix(n,(i,j) -> f(i,j)), n = 1..4) ]

where f(i, j) is the function defining each element.  Your mileage may vary. 

@MapleIsHard And that is what one generates late at night on minimal sleep. My hope was to get you started. Clearly, you now have a multitude of Maple solutions. I hope you found them mathematically and conceptually educational. 

As a like-minded educator, I thought you might be interested in an alternative approach to this problem. It simplifies some of your work and provides the code to create a "What If" app through the Explore procedure. IMO, the Explore procedure is the most pedagogically valuable Maple procedure for complex problems like yours. 

SIR_simple_vaccination_example_suggestions.mw

Upload your worksheet for assistance.