I've been doing my Scene registrations mainly using the common practice of spheres and auto register which generates a ScanMangager with the target tensions listed for the entire cluster.
I was shown a different method which was to mark all of your spheres and checkerboards, then drag in the scans one by one using "place scan" individually. This seems to work well but doesn't create a ScanManager. All the tensions are listed under each scans "Scanfit". The idea was that it's easier to spot a misaligned scan when doing it manaually than with the autoregister.
My question is whether anyone knows any downsides to this method other than taking a bit longer? For example, do the target errors still get distributed with a closed loop.
Using "place scans" vs ScanManager
- MarkL
- V.I.P Member
- Posts: 129
- Joined: Thu Sep 29, 2011 7:57 am
- 12
- Full Name: Mark Lupton
- Company Details: Wolverton
- Company Position Title: LASER Scanning
- Country: USA
- Skype Name: [email protected]
- Linkedin Profile: Yes
- Has thanked: 1 time
- Oliver Buerkler
- Global Moderator
- Posts: 1446
- Joined: Mon Oct 06, 2008 9:44 am
- 15
- Full Name: Oliver Buerkler
- Company Details: FARO Europe GmbH
- Company Position Title: Director of Laser Scanning
- Country: Germany
- Skype Name: oliver_buerkler
- Linkedin Profile: Yes
- Has thanked: 38 times
- Been thanked: 12 times
- Contact:
Re: Using "place scans" vs ScanManager
Hi Mark.
Placing single scans does not do a global adjustment.
For this, you need to run "Plans Scan_s_" on a cluster or the whole project.
Best regards,
Oliver Bürkler
Placing single scans does not do a global adjustment.
For this, you need to run "Plans Scan_s_" on a cluster or the whole project.
Best regards,
Oliver Bürkler
Oliver Bürkler
Director of Laser Scanning
FARO Europe GmbH
[email protected]
[email protected]
Twitter: FARO_LS_PM
Director of Laser Scanning
FARO Europe GmbH
[email protected]
[email protected]
Twitter: FARO_LS_PM