Mathematica really slams Maple here

http://www.wolfram.com/mathematica/compare-mathematica/compare-mathematica-and-maple.html

Let the war begin !

Fair enough, I missed the uneval quotes. 

unassign should have separated the created data from the name and allowed gc() to clear it from memory. 

hmm.. setting the name to some smaller set of data doesn't release the memory either

temp:=Matrix(1)
gc();

kernelopts(bytesalloc)

           same large value

this would suggest maybe (I don't know I'm just speculating) that the problem lies somewhere with gc()

Fair enough, I missed the uneval quotes. 

unassign should have separated the created data from the name and allowed gc() to clear it from memory. 

hmm.. setting the name to some smaller set of data doesn't release the memory either

temp:=Matrix(1)
gc();

kernelopts(bytesalloc)

           same large value

this would suggest maybe (I don't know I'm just speculating) that the problem lies somewhere with gc()

Yes I had thought maybe it could have been unfinished code or even a bug.  But I have discovered that the problem is completely within mstring.dll

Wether it is unfinished or a bug I don't know.  If it was a simple fix it would be nice if maplesoft could simply modify the dll and make the new modified mstring.dll available.  Perhaps someone here is talented enough to fix it?  decompile the dll find the error, fix it, recompile it and make it available. 

**edit added**  I suppose I should mention how I confirmed the problem was with mstring.dll.  Transfering mstring.dll from a newer maple version into the old allows Create(ospd3) to work.  However I will not use it because there may be other unseen side effects which break other commands.

ospd3 has existed since at least M9.5 but cannot work until M15 when the mstring.dll file size jumped from 870 Kb to over 2000 Kb in size suggesting some major work was done on that dll.

Just bringing this up again as some nice applications for scrabble were added to the app center. 

Has anyone figured out why ospd3 does not work?  Is there a workaround??

Doesn't the condition n>=3 cause it to fail?

Changing n>=2 works fine.  The fact that you've set n>=3 and then using tablelook to find Zeta^n at n=2 will most certainly fail. 

zetatab := [conditional(Zeta^n::posint*x::anything+y::anything = Zeta^(n-3)*(Zeta-1)*x+y, n >= 2)]:
tab := compiletable(zetatab):
tablelook(Zeta^2+Zeta^6, tab);

tablelook(Zeta^3+Zeta^6, tab);

You don't need $1000 software to do math.  The personal Maple edition is only $249. 

Bugs in any software certainly increase frustration, but not knowing the language can also be the cause of frustration for any software.  I am certain Sage causes frustation with it's bugs, but because it is free the expectation that it will contain bugs is okay because they're expected to be there.  The fact is because you spend x$ for software one expects no bugs and when there is, it is a source of frustration for the topic you found it in.  It is unfair to say that many things do not work when in fact a more appropriate statement would be many things do work and some things have bugs.  Maple requires a higher learning curve than Sage but the question is - Is Maple perfect?  No, but neither is Sage.

I was frustrated at Sage because it couldn't factor(x^3+y^3) 
Then I found out that in Sage you you need to define y as a variable var('y') if you did not know this you would incorrectly conclude that nothing works.

Yes, there were a few commands in there that weren't completely financially related.  However , a logical choice it was to have them placed in the finance package. 

I haven't had a complete look at the Maple 16 finance package, as my native Maple platform is Maple12, but there are some fairly complex and interesting commands in there.  Even with the new statistics package there are still more commands that could be added.  It is not surprising that not all commands were included at the time.

The builtin packages are readonly.  You can change that by using LibraryTools[WriteMode] to modify the library package to writeable.  Then can change back to readonly later after modification. 

Although I would suggest not modifying the built-in libraries just in case it becomes broken and instead do as you have done already, by creating a new package MyFinance.  I meant to suggest Finance2 as a supplement name but that's easy enough to change. 

Maple12 has a meager 12 commands under the finance package.  In Maple15 it exploded to almost 12x's that number to 140! (! not to be confused with factorial) simply awesome!  It could be pointed out to Maple to add some more commands if there are some that are believed to be missing. 

I don't think Mathematica has it in their package either.  Even when the statistics package for Maple came out Karian and Tanis had written a maple statistics supplement since there were many missing functions that they believed should have been included.  Although today Maple is a much stronger platform than it was.

However, Maple is versatile and we could create those procedures you mention.  Maybe a collaboration on a finance supplement is in order? 

Yes okay, I see that now.  I was unawares of the bug.  It should be okay now.

I cleaned up the post (you had double posted the worksheet). 

It is missing some dialogue to show the reader what you are doing but it does look like a predator-prey type model, and in the beginning vector A somehow got created from A:=<,>  

A couple of thoughts came up while producing the tree.  We can turn all of the vertices labels off with labels=false but we can't turn some of them off.  It would be a nice display to blank out all of the parent node labels.  I thought about trying to blank out only numeric characters in the graph but couldn't think of a way.  Perhaps other options exist. 

For interest, visually the huffman tree from Huffman coding looks like this

with(GraphTheory):
t1 := Graph(undirected, {{1, 2}, {1, 3}, {2, 4}, {2, 5}, {3, 6}, {3, 7}, {4, a}, {4, e}, {5, 8}, {5, 9}, {6, 10}, {6, 11}, {7, 12}, {7, _}, {8, h}, {8, i}, {9, m}, {9, n}, {10, s}, {10, t}, {11, 13}, {11, 14}, {12, 15}, {12, f}, {13, l}, {13, o}, {14, p}, {14, r}, {15, u}, {15, x}}):
DrawGraph(t1,style=tree,root=1);  #I used numbers as just placeholders to build the tree

Windows has a built in magnifier under AllPrograms->Accesories->Accessibility

Windows has a built in magnifier under AllPrograms->Accesories->Accessibility