@alshehri 

Yes, just subtract one expression from the other. The y(x) terms cancel, as well as the terms having h^2.

@alshehri 

The h=0 is the expansion point, i.e., it's the Taylor series at or about h=0. The 3 is because I wanted terms upto O(h^3).

@alshehri 

y(x+h):  % = series(%, h=0, 3);

y(x-h):  % = series(%, h=0, 3);

@alshehri 

y(x+h)-y(x-h):  % = series(%, h=0, 3);

Your file did not attach. This is an intermittent bug in MaplePrimes. Please try again.

@landivar Have you tried a simple restart; ?

If that doesn't work, try plotsetup(inline); , then retry the plot3d.

If that doesn't work, try adding the option thickness= 2 to the plot3d. This thickens the gridlines.

If that doesn't work, try adding options style= wireframe, color= black to the plot3d. This should show only the gridlines.

Do you remember which examples you ran?

Or < v > + m, which produces Matrix output.

Another option is v + m[..,1], which produces Vector output.

@Kitonum Yes, your solutions are the same two solutions as produced by my program. My program does not directly prove that these are the only solutions, although it can be easily used to generate such a proof.

Your techniques for the direct solution of such problems are very impressive. Your technique is to step through the entire solution space finding the points that satisfy all the constraints. My technique is to make logical deductions from the constraints and narrow the solution space. As a trivial example, from A = B and B = C, I deduce A = C (where `=` means membership in the same equivalence class rather than simple identity).

My program does this problem in about 0.1 seconds. Your technique takes about 2.9 seconds.

@sunil-maple What format do you want the table? There are 27 matrices in the ring. A 27x27 array with each entry a 2x2 matrix seems to large to put onscreen. So, what format did you have in mind?

Do you mean 2x2 matrices?

@Markiyan Hirnyk Stephen Forrest is saying to select "Factor" from the context menu. This is equivalent to using factor (lowercase f).

@Markiyan Hirnyk The information about continuity is not displayed if you include the phrase assuming n::posint.

@Christopher2222 wrote:

One could instead create a proc that would circumvent the issue when StandardDeviation command is called, yes?

Yes, Statistics:-StandardDeviation could be overloaded so that when weights are passed in, it is diverted to separate user-supplied code; and when weights are not passed in, it uses the current code. Like this:

restart:
sav_std_dev:= eval(Statistics:-StandardDeviation):
unprotect(Statistics:-StandardDeviation):
Statistics:-StandardDeviation:= overload([
     proc(A::{rtable,list})
          option overload;
          local p, weights, sd;
          if not membertype(identical(':-weights')={Vector,list}, [args], p) then
               error "invalid input:"  # Kicks to next proc in overload
          end if;
          weights:= rhs([args][p]);
          print('weights' = weights);
          sd:= Statistics:-StandardDeviation(A);
          # Do whatever you want here to compute with the weights.
     end proc,

     sav_std_dev
]):
    
protect(Statistics:-StandardDeviation):

Please explicitly show in a worksheet the code that works and the code that doesn't work. Please state explicitly why you say that it hasn't worked.