@Christopher2222 Editing a post can in itself screw up contents between angle-brackets. It's a (very annoying) bug in the editor.

You can see an older version here. It had, at various lines,

A:=<<0|-4>,<-1|0>>;

beta:=<alpha|<0,0>>;

V1:=<-2,1>;

V2:=<2,1>;

(I've had to get into the habit of copying all of a post/comment/question to the clipboard before hitting the Edit button.)

I suppose that there are various ways for the student who does not immediately see the 7/9 part.

> restart:
           
> K:=7*10^i:         
> seq(K,i=0..2);     

                                  7, 70, 700

> P:=sum(K,i=0..j-1);

                                        j
                                    7 10
                               P := ----- - 7/9
                                      9

> seq(P,j=1..3);     

                                  7, 77, 777

> W:=sum(P,'j'=1..n);  

                                               (n + 1)
                                7 n   70   7 10
                         W := - --- - -- + -----------
                                 9    81       81

> seq(W,n=1..3);

                                  7, 84, 861

> u:=unapply(W,n):

> u(3);
                                      861

acer

I suppose that there are various ways for the student who does not immediately see the 7/9 part.

> restart:
           
> K:=7*10^i:         
> seq(K,i=0..2);     

                                  7, 70, 700

> P:=sum(K,i=0..j-1);

                                        j
                                    7 10
                               P := ----- - 7/9
                                      9

> seq(P,j=1..3);     

                                  7, 77, 777

> W:=sum(P,'j'=1..n);  

                                               (n + 1)
                                7 n   70   7 10
                         W := - --- - -- + -----------
                                 9    81       81

> seq(W,n=1..3);

                                  7, 84, 861

> u:=unapply(W,n):

> u(3);
                                      861

acer

Did you really intend e^(-34.32*10^4/t) and others like it, or were those intended as exp(-34.32*10^4/t) instead?

acer

@kail85 It's likely going to boil down to which you prefer to use: `freeze` and `thaw`, or `subs`, or maybe even frontend.

restart:

f:= a*exp(x) + b*exp(2*x) = 2*exp(x) + 5*exp(2*x):

frontend(solve, [identity(f,exp(x)), [a,b]],
         [{`+`,`*`,`=`},{[a,b],identity}]);

                                    [[a = 2, b = 5]]

I find that I often start off with `frontend`, and if the example gets involved I'll switch over and try with `freeze` and patmatch or typematch.

@kail85 It's likely going to boil down to which you prefer to use: `freeze` and `thaw`, or `subs`, or maybe even frontend.

restart:

f:= a*exp(x) + b*exp(2*x) = 2*exp(x) + 5*exp(2*x):

frontend(solve, [identity(f,exp(x)), [a,b]],
         [{`+`,`*`,`=`},{[a,b],identity}]);

                                    [[a = 2, b = 5]]

I find that I often start off with `frontend`, and if the example gets involved I'll switch over and try with `freeze` and patmatch or typematch.

@AliKhan The Matlab result for A3(3) is wrong, The evalhf result for A3(3) is wrong. But if you really want to use evalhf then try it with `add` instead of `Sum` or `sum`.

I find that people really don't like hearing it, but one thing you might reconsider is the methodology of assigning float values to your parameters at the start of your worksheet. Such values are useful for numeric evaluation, but often make it awkward to get the best symbolic benefits before doing numeric evaluations. Maple can often be a lot more easily powerful if you don't make such assignments at the start.

@AliKhan The Matlab result for A3(3) is wrong, The evalhf result for A3(3) is wrong. But if you really want to use evalhf then try it with `add` instead of `Sum` or `sum`.

I find that people really don't like hearing it, but one thing you might reconsider is the methodology of assigning float values to your parameters at the start of your worksheet. Such values are useful for numeric evaluation, but often make it awkward to get the best symbolic benefits before doing numeric evaluations. Maple can often be a lot more easily powerful if you don't make such assignments at the start.

T:=convert(expand(simplify(convert(A3(n),rational))),tan);

                             /1     \
                          tan|- Pi n|
                             \2     /

acer

T:=convert(expand(simplify(convert(A3(n),rational))),tan);

                             /1     \
                          tan|- Pi n|
                             \2     /

acer

@nerdpole Try it as,

alpha := unapply(piecewise(
    x1 < 0 or x2 < 0 or x3 < 0 or h < x1 or h < x2 or h < x3, 0,
    0.5*h  ..... )),x1,x2,x3);  

with inserting the (x1,x2,x3) -> yourself.

@nerdpole Try it as,

alpha := unapply(piecewise(
    x1 < 0 or x2 < 0 or x3 < 0 or h < x1 or h < x2 or h < x3, 0,
    0.5*h  ..... )),x1,x2,x3);  

with inserting the (x1,x2,x3) -> yourself.

@Doug Meade You could try Chapter 16 of the Maple 16 Programming Guide.

@Doug Meade You could try Chapter 16 of the Maple 16 Programming Guide.

Sorry to the audience, if it is obvious, but there is also the possibility to use a combination of `read` and .mla library archives.

The documented source code -- including comments, and structured with $include or related directives -- could be kept in a plaintext file. A simple shell script, or even a very short worksheet, could then be used to `read` the source and save it to library archive. But such a "rebuild" would only need to happen whenever the shared source code got changed. All other occasions that need to use the shared materials could simply pick it up at run time from the .mla library archive.

This is actually how I work with Maple most, by launching the commandline interface to rebuild my .mla, and launching the GUI from a terminal shell. For both of those I use the `-b` option to specify augmentation of libname (although I have several common actions and common libname amendments aliased in the shell, or in simple scripts).

I sometimes prototype procedures in the GUI. But if they become long or if I want to re-use them then I put them into plaintext files, which has yet another benefit of being very safe from corruption. And then I edit them with `vi`, which has Maple source syntax highlighting.

acer