@Mac Dude The 3D pie charts were introduced in Maple 16. 3D pie charts seem dishonest---they overemphasize sections in the foreground. Consider your example above: The Machinery is slightly more than 1/4 (27%), but it looks like slightly less than one quarter.

The arrow can be added with plottools:-arrow.

Just confirming what you said about slideshows, since you seemed unsure: There is no scrolling allowed. Each section becomes one slide. Sections that are longer than one screen get truncated.

@radzys I got the file this time.

@MuriloLobo The module S1 is supposed to be the output of a command in the Optimization package. But there is no such command in the beginning of your worksheet. There is a call later in the worksheet, S1:= NLPSolve(...). A call like this needs to occur before you access S1:-Results.

@Mac Dude Just confirming, since you were unsure: Sections and subsections do work in Classic.

@radzys I suspect that this is a bug in MaplePrimes; I've never seen it before. When I click on the file link in your most recent Reply, I get taken to a completely blank screen. Please try uploading again. Try giving the file a different name.

Debugging info for Bryon: The URL of the erroneous link is

www.mapleprimes.com/view.aspx?sf=206198_Answer/Wind.mw

when it should be (I think)

www.mapleprimes.com/view.aspx?sf=<some number>_Answer/Wind.mw

@MuriloLobo Something is missing. As Mac Dude said, S1 is not defined anywhere in there. You should be getting Error, `S1` does not evaluate to a module. You also need a semicolon at the end of each line. The comma at the end of the last seq needs to be a semicolon, as Mac Dude said.

Please upload your worksheet, don't just post it. Use the green uparrow that is the last icon of the second row of the toolbar of trhe MaplePrimes editor.

@Mac Dude Creating a sequence of equations or inequalities with seq is fine. Nearly every structure in Maple (everything that I can think of) is a first-class object, i.e., it can be assigned to a variable and manipulated like any basic variable.

@radzys Everything works in the worksheet that you posted: The solve solves the eight equations and you get the animation at the end. If you still have an issue that you'd like me to look at (your "most perfect scenario"), please post a worksheet where you attempt it and it doesn't work.

The period of the oscillations is about 0.0006. This is too small for you to see any significant detail on the scale x=0..1. Better is x=0..0.001.

@OV I am referring to calling s1[3](1) after running the loop as modified by Mehdi and getting the recursion error in "_dat".

There is nothing wrong with having an Array of procedures in Maple. (Technically, this is a table of procedures, but the distinction between table and Array is insiginificant here.) The problem is that s1[3], which is a procedure generated by dsolve, calls itself. I still don't know how that happened.

@Michael eval instead of evalf will produce exact results. But better still to use two-argument eval, as Acer did.

@Alejandro Jakubi The controller gets swapped out whenever it is in a waiting state, which is usually most of the time. This leaves all cpus available to run grid kernels.

Please post your worksheet.

@mehdi jafari The second recursion error is in what the OP calls s1[3], which is a procedure extracted from dsolve(..., numeric) output. It is in the second cycle of the for that this error occurs. It is confusing, and perhaps the source of the error, that s1[...] is defined at two places within the loop with different indices.

You can cause the error simply by calling s1[3](1) or at any numeric input.