Hi Matt,Matt Young wrote:With the correct procedures you should achieve a mean average of around 1 or 2mm for your overall registration result. You must use the cloud 2 cloud function after the traverse in order to achieve this type of accuracy, and you must adjust constraints within the registration after the cloud 2 cloud process.
I always prefer using coincident targets with scans - as Paul suggests using no targets is fast but not reportable in the same way as traverse or coincident targets.
If you have a project with thousands of scans then don't try and do it all in one registration, it will be slow going. Try to break the project up into manageable areas. Two or three hundred scans max per registration is usually my preference.
Was about to post a question about this.
I'm working on a registration using the C10 which will eventually have around 300-400 scans. At the minute I have around 200 scans in a registration, and it is slow going when registering/making adjustments.
I recall you being able to add multiple registrations into 1 registration, but I've never managed to successfully do it.
I've tried to freeze the registration and create a ScanWorld, then add this to a new registration (so I could eventually do this with multiple registrations), but it never finds the constraints when Auto-Adding.
I haven't received the control yet for for the project, so am keen to ensure my scan registration is kept together.
Do you have any tips?
I also have a second query... I know that by cleaning data in the ControlSpace and then selecting "Set default Clouds", this will save the edits, but if your ScanWorlds are already part of a registration will they be applied when creating a ModelSpace, or do you need to re-add them to a registration?
Actually, I have a third query haha. If you have a registration which includes some cloud to cloud constraints, when you remove the ScanWorlds and re-add them, they disappear. Is there a way to prevent this happening, other than creating vertices in the MS and pasting in to the CS?
In response to the OP. I use the traverse function all the time on a C10 and it's great. Much quicker for me and great results. You can always set up additional targets over known positions and scan them in, and/or scan in temporary targets too, then add them all in to the registration.