Frozen merge naming

[drserajames]

Frozen merge naming

[skepner]

I have never heard about this feature and it was not implemented in acmacs. Frozen merge (requested by other people) is different: two maps are oriented to each other using procrustes and resulting coordinates (in the merge) are copied from the oriented sources, coordinates for common points are means of coordinates in the oriented sources.

I will add implementation of what you described into my todo list. You may suggest the name, it cannot be "frozen merge" because that name is busy with feature described above.

I understand that people may be confused by naming. Some time ago we had discussion with Derek about names for overlay and frozen megres (implemented in acmacs) and current names are result of that discussion. I am not going to change the names. People have to get used to the "new" names.

[drserajames]

I spoke to Derek about it and he also thinks it's best to be consistent with the lispmds names (that was what he expected you'd done), as many people using acmacs.r will have started with lispmds.
your name -> lispmds name
frozen -> overlay
overlay -> overlay relax
[new functionality] -> frozen

[skepner]

To break the infinite loop of renaming I decided to rename functions in the following way. I assign numbers to different merge types, i.e. functions will be called acmacs.merge.1, acmacs.merge.2, etc. And I will update documentation (?acmacs.merge) accordingly. Then you may create your own function called say merge_frozen which just calls whatever acmacs.merge.N function you think it corresponds to. Or you ask Sam to create that kind of function in Racmacs, if you wish. Other people who may have their own opinion on what frozen merge is will be able to create and name their own functions whatever they like.

[drserajames]

👍

[skepner]

implemented in v4.0