Registration Tightening

[jared.white]

Hello, 

I am working through a registration issue now, that is very large (over 2000 scans).  It appears that recap will only allow you to merge / constrain a single scan to one other single scan.  What we notice is that there is a lot of stack up error from one side of the project to the other.  Cyclone has a feature that is ran once scans are linked one by one that is called 'auto add cloud constraints'.  What this does is look at all overlap between the registered scans, and creates a constraint between anything that overlaps.  This tightens up the error dramatically with large projects.  It would be great if Recap would do the same thing.  

JW

[ryan.frenz]

This isn't quite correct - ReCap will use a single scan to seed the registration, but all overlapping scans to finalize/adjust it.  This happens all the time and is not a separate action or option.

This usually works great, unless you somehow got a biased drift between sides of a large loop or levels of a building.  If the drift is too large, ReCap may not consider all of the scans to be overlapping, and hence not fix the problem with the full adjustment.

This case is usually corrected by identifying the scan or area that triggers the drift, and correcting it, or rebuilding the group to minimize the effect.  If the ends of the loop are close enough, you'll see the adjusted result you expect.

HTH

-Ryan