Okay.  Good, good, and good.  :D

Maybe I've gotten myself confused.  In the shrink-wrapping script (the larger project, not the trimmed .pyd version), I generate the new vertex positions using initial worldspace locations.  I found that if I then generated the morph deltas using the same worldspace positions, any worldspace displacement could end up baked into the resulting morph.  To overcome that, I had to generate the deltas using the original base geometry vertex positions.  I may have muddled things while experimenting and ended up taking unnecessary steps?  This is more a problem of actor-level worldspace handling than of mesh-level (that is, world transforms versus shape changes via deformers or morphs).  Worldspace gives us the new surface shape for the mesh, but also the repositioning due to transforms.  I guess I'm having trouble sorting all of that out effectively, which is what prompted my question.  But, too, if I have morphs set before the comparisons, they get baked into the result if I don't use the base geometry positions to sort things out.  Did I explain that badly?  Probably.  Cage needs sleep.

I'm wondering about mapping polys/tris (verts?) between actors.  If we can virtually merge our geometries before running the comparisons, my tests seem to show that we'll run much faster than if we loop through multiple actors.  Would it make any sense to have the ability to merge the data internally for multiple geometries, then be able to separate it again at the end?  Did I explain that badly?  Probably.  Cage needs sleep.

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