Woo!  This is fast.  Even without octree, the .pyd is running in twelve seconds the same correlations which were taking between one and seven minutes for me previously (longer for multiple actor looping).

I'm going to perseverate on multiple actors for a moment, because that's my next test.  It looks like the way to do it right now is to get the full set of correlations for each source actor in a group to the target actor.  Then sort through those to find the best matches, based on the lowest distances.  This will surely be faster (thanks to the .pyd) than what I was doing before, but I'm wondering if there will be any RAM overhead issues.  There will end up being multiple complete data sets for the hit points, corresponding to each source actor, which amounts to a lot of data coming in up front which will just be discarded (but when have I ever complained about that before, eh?)  So that's what I'm going to try.

I have the different shrink types worked in, but there script is currently a bit of a mess because I haven't ported over all the core to the new form.  So I hope to have a version to post tomorrow, which you can decide whether or not to make the one that gets passed in the zipfile....  :unsure:

===========================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.