Well, it has mostly to do with everything I witnessed and experience in my extensive time being an active user of reverse engineering tools and workflows over almost a period of 2 decades.
Basically it boils down to the fact that scanning technology doesn’t do a very good job seamlessly stitching together 4-dimensional-space-time.
Therefore, 3D-scans are of higher quality and are more accurate when they’re thought of as smaller constituents of the overall picture.
Meaning, rather than trying to capture any object via one single scan, it’s actually better to capture it in multiple pieces, and then align them later during post processing.
Hence:
So, the ‘alignment’ per say, and rather ‘automatic alignment’ should be done in a sequence later in the workflow during post processing.
The idea that ‘alignment’ / ‘automatic alignment’ should occur (during the scan process) is actually what causes an whole assortment of compounding errors over time.
It’s my strong belief that iRhino would be better off if it had the ability to incorporate ‘multiple scans’ that can be aligned later during post processing.
This would enable more accuracy and higher quality outcomes.
During post processing, of course, scans need to be cleaned up and noise needs to be reduced prior to the alignment and merging process of the multiple scans.
Hence: