I don't know enough about the math involved to really be able to develop this without using PoserPython for testing and visualization, unfortunately.  And I'm not altogether sure switching to a standalone Python 2.5 script would rescue the process from the current problems.  Basically, I don't know enough about programming.  Maybe I'll make more progress on this some time in the future.  Hopefully someone else will run with the idea before that.  The math really isn't so bad, although I don't understand why any of it is appropriate at any given point.  The problem is what seems to have been poor planning with Python's design, in the early days.  Certain memory handling was implemented to speed things up, presumably when computers were slower and less powerful.  I've read some serious rants about this memory leaking, online, coming from professional programmers.  If the pros can't beat this problem, I'm not going to keep banging my head against the wall over it....

Bummer, huh?

===========================sigline======================================================

Cage can be an opinionated jerk who posts without thinking.  He apologizes for this.  He's honestly not trying to be a turkeyhead.

Cage had some freebies, compatible with Poser 11 and below.  His Python scripts were saved at archive.org, along with the rest of the Morphography site, where they were hosted.