Please try attaching that worksheet again.

@acer You're right: "Separately summing" was a poor choice of words. But I still think that the title "Separation of even and odd terms suffices" applies. Note that your accelerator procedure F only works when the chunksize is even.

@acer Aha! That gives me an idea of something even easier. Since the even and odd terms both form decreasing sequences, since each is asymptotic to a convergent p-series, and since the numeric summer only looks at the numeric values of the terms, separately summing the even and odd terms should do it.

Using the general series term F(n) from my previous Answer,

evalf(Sum(F(2*n)+F(2*n-1), n= 1..infinity));

     0.785852250894067

Voila. This also confirms the accuracy of the asymptotic series approach, although it was a much bigger hammer than was necessary for the job.

It's tricky. You essentially have to do it one procedure at a time. I have posted code here in the past which will cycle through all the procedures in a module and print them. However, the search tools on MaplePrimes are atrocious, and I can't find that post. Perhaps someone else can. (*)

Some modules have a "module body"---a small section of directly executable code. There is no way to see this code as it's not even saved with the module. This code is usually irrelevant and I think that it's unlikely to be used in a saved package anyway.

((*) Let me take this opportunity to request again from the MaplePrimes administrators: Please, please make this entire site searchable by Google, with the pointers pointing to the threads rather than to the users' Answers and Replies sections!! When a user has over 5000 Answers and Replies (as I do), a pointer into those sections is worthless!! What's stopping you from making this change? Wouldn't it require only a trivial amount of effort? There's a vast storehouse of Maple knowledge here that's essentially going to waste. ) 

@acer However, the infinite sum, although correctly entered, can't be evaluated under evalf. I'm working on an approximation based on asymptotic expansion. There are a few snags.

@YasH Without the parse, the cat(L[]) produces a variable name that looks like a number. You will notice that the result shows in italics in the GUI. With the parse, you actually get a number, which shows in an upright font.

(This may have changed in a recent version of Maple. I'm stuck with Maple 16 today.)

@JessyOw I think that you need to enter the string with quotes: `Hello! Bob` rather than Hello! Bob.

On the other hand, I do have sympathy for the other position: that the condition number is a precisely defined mathematical entity and that ConditionNumber should respect that. So perhaps the other number should be relegated to a command ConditionNumberEstimate or some such. And since this estimate is so crude, perhaps only its ilog10 should be reported.

@moses Look closely at the beginning of the first for loop in procedure `α__ν`. You have

for i from 1 to `n__pile ` do

It should be

for i from 1 to `n__pile` do

In other words, you have an extra space at the end of `n__pile`.

Note that there's no need to use name quotes on n__pile. If you had simply used n__pile, this error would've been advoided.

@moses If I understand you correctly, you want to evaluate the matrix that you currently have entered as alpha, with each value of S coming from the corresponding entry in the matrix S__p. Is that correct?

@pchin I figured that something like this was going on since there is no error message when trying to use colorscheme with densityplot. Can it be fixed (in the future) so that option scaletorange respects option zrange?

@Kitonum How do you get Maple's array plots (side-by-side plots) to display on MaplePrimes? It never works for me. What browser are you using and which Maple GUI?

@Kitonum The usual case is that numpoints alone isn't enough get an exact number of points. The default setting is adaptive= true, which attempts to fill in the sharp turns of a curve after fulfilling the numpoints requirement. You can read about it at ?plot,options. If you count the points in your own posted example, you'll see that there are 25, which is why I brought up this issue.

@acer I stumbled upon this technique myself when looking for a way to get more control over the size of 3d plots projected into the xy-plane. It's great that you've found a single command to do it.

What's the purpose of each pair of unevaluation quotes in the following line of code:

P2d:=':-PLOT'(remove(type,[op(P3d)],
     ':-specfunc(anything,{:-AXESLABELS,:-LIGHTMODEL,:-ORIENTATION})')[]):

@Bendesarts Yes, your guess as to the reason for the limited usability of the style of module that I proposed is entirely correct.