Well, you'll need to type them into Maple. The equations in the docx file are just bitmap images, so nobody will do the typing for you, I'm afraid. ;-) [Side note: does any OCR software help here?]

But you got the syntax right, as far as I can see, and the 2D Math features should help you.

I would, however, enter multiplication characters, just to avoid ambiguities, but that depends on input mode and personal preferences.

There are many ways and options to plot functions like this. Here's my suggestion:

a := exp(-2); # any constant
f := n -> piecewise(n=0, 1/6, n::posint, 1/6*(1-a)*a^(n-1));
plots:-pointplot([seq([n,f(n)], n=0..6)]);

and you will find this description.

For screencasts, it might be sufficient to use Slideshow mode. Just enter ?slideshow to bring up the help pages.

Currently, I have no Mac here, so did not try on that platform.

I'm not sure about that MATLAB syntax, but this is what I interpret, translated to Maple:

A:=Matrix([[0,3,2,13],[5,0,11,0],[0,0,7,0],[0,0,0,0]]);
map(isprime,A);
isprime~(A);  # alternatively, since Maple 13

The Simulate command creates essentially the same plots as you see in MapleSim, one per probe.

If you want to dsolve the DAE system (along with ICs), make sure you add the 'numeric' option. The resulting procedure can then be fed into plots[odeplot] to get a visual output. Please see the help pages of these three commands for a start. Run and modify their examples to get an idea what can be adjusted. For an introduction to the topic, check out ?examples,numeric_DAE worksheet.

Sorry, I don't understand why you are saying that CodeTools:-Usage does not give you information about CPU usage. It surely does. As I said, giving the percentage is (or should be) outside the scope of an application. Only the OS has the relevant data.

What other applications are you referring to?

Please see the ?CodeTools package, particularly its Usage command and related ones. They return absolute values, however.

Measuring percentages can/should only be done by the OS, not by an application, I'd say.

Note that things get more complicated on multi-core / SMP systems. To find out how many cores Maple sees (and potentially uses), enter kernelopts(numcpus). You can also set that number, which can be useful in profiling, benchmarking, etc..

I cannot reproduce that either. We're using Ubuntu 10.04 and Windows 7 here. Never tried Xubuntu, and 12.04 is fairly new, so we can't guarantee that Maple 15 will work on it.

Please upload your worksheet (mw file, with saved output), using the green arrow-up symbol.

Also, do you have any extra packages installed on Linux, or anything unusual in your ~/.mapleinit (if it exists)?

I cannot reproduce that problem either, but I don't have a Mac.

Unless you have already done so, install the 15.01 update from our website or via the "Check for Updates" menu. On the Mac, it's under Maple > Preferences, I think.

Student:-NumericalAnalysis was introduced in Maple 13, so if you can quickly upgrade, you're done.

If I interpret that description correctly, this should be what you want:

n:=7:
interface(rtablesize=2*n);    # optionally
J:=Vector([-1 $ n, 1 $ n]);   # Matrix([[...]]) would also work here
with(LinearAlgebra):
DiagonalMatrix(J);

Don't have much time to polish that, but the essential steps are

de1:=diff(x(t),t$2)+(a+2*q*cos(omega*t))*x(t)=0;
de2:=diff(y(t),t$2)-(a+2*q*cos(omega*t))*y(t)=0;
de3:=diff(z(t),t$2)=0;
sys:=[de1,de2,de3]:
sol:=dsolve(sys);
odetest(sol,sys); # optional check

The system is uncoupled, so you could also apply individual dsolve calls.

As you can see, Maple solves the first two in terms of MathieuC and MathieuS functions. Place the cursor on that, and hit F2 to see the docs.

... on supported platforms, including Ubuntu x86_64. You might check your Maple_15_InstallLog.log (and the same for the 15.01 update if you started with 15.00) for warnings and errors at installation time. But in case the problem is Fedora specific I recommend changing to another distribution. Fedora is bleeding edge, with all its pros and cons, and probably a bad idea for production systems.

I'd try ExportMatrix instead. Please take a look at the help page and decide which format fits your needs.

If you let T be a Matrix (even if it has no mathematical structure imposed), there should be no conversion necessary.