Quote - Robert (IPP guy) came up with a neat way to handle the spherical zone weighting, so I might be able to dig that up at some point... but your other suggestion sounds interesting as well.  If I could create (for example) an Ear morph and then tell the correlation script to ignore (exclude) any verts listed in that morph, that would work.

That's exactly how the morph subtraction features of the Morph Trimmer script work.  It's more versatile than using an AABB or sphere, it can restrict vertices more readily (try isolating eyelashes using a bounding box :lol:) and it could be used with morphs made using magnets or the morph brush.  The old AABB setup also created complications between running the Tkinter GUI and allowing the user to work in the 3D space.  All methods I've seen or tried which do that end up introducing potential Poser instability.

Once the .vmf Trimmer is together, you'll have a wide range of available screening methods which can create data files for merging.  I sort of think the editor should be kept simple.  I think some ideas you've mentioned may not belong in the editor, but in the Trimmer.  Among other things, the editor can be run outside of Poser if desired, so it can't necessarily access Poser data.  A screening tool which operates within Poser will cover many situations, reducing any need to complicate the comparison or editor scripts with excess options.

Quote - Ok, so the other options I mentioned - making some decision on what to do with duplicate vert info - would decide what to do with those indices in File #2, where there was already data for them in File #1.  Currently, (my understanding is that) your script just replaces the info, without doing any other tests on it.  File #2 data currently takes priority over FIle #1 data.  I'm suggesting that some sort(s) of tests could be done to determine which data to use.  Again, no redundant info in the resulting output/merged file.

I misunderstood.  You're talking about rules of precedence, right?.  Right now this can be handled by loading the files into the editor in the desired order.  If your second file is better, don't merge it into the first file, merge the first file into the second.  This could become complicated when there are more than two files, so I can see your point.  Some way to set merging precedence would be useful.  :thumbupboth:

Quote - So, I'm not (necessarily) suggesting moving back to the .vwt format, but since you mentioned it, I'm still unclear on your reluctance to list that additional data.   You seem all for options that may or may not be of any value, but you seem opposed to additional data that might be useful to have handy

I was glad to get rid of them, actually, and I still don't see any indisputable value for carrying the locations in the data file.  Those who are dissatisfied can create their own edits of the script, even post and share them.  I'm not ready to introduce a broad change if I'm not convinced of its utility.  That includes additions and removals, at this point.  I hesitate to move too fast, in most cases.  Make a good enough case for something, give me time to come around, and my opinion may change.

I like the idea of more refined dot checks.  :thumbupboth:

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