cyclone 7.1 new features overview whitepaper

Cyclone 7.1\TruView

Phoenix\Xena Integration Testing Specification of 24 V1.1

Leica Geosystems HDS

Cyclone 7.1 and TruView New features and enhancements

****There is a new location for the hostID.txt file- see section 2.19 below for details****

Contents

1 Summary of features ...................................................................................... 2

1.1 Registration\Target acquisition.................................................................... 2

1.2 ModelSpace ............................................................................................. 3

1.3 Cyclone Publisher\ TruView\TruSpace........................................................... 3

1.4 Navigator\General Cyclone ......................................................................... 4

2 Feature detail ................................................................................................ 4

2.1 Automated target matching ........................................................................ 4

2.2 Highlight Entire Row in Registration Editor .................................................... 7

2.3 Proper sorting of columns in the Registration Window ..................................... 8

2.4 Accepting Acquired Targets- New Acquire Target Dialog .................................. 8

2.5 Vertex added to scanner location during traverse ........................................... 9

2.6 Auto-registration with C10 data................................................................... 9

2.7 ScanWorld Centric Viewing ........................................................................10

2.8 Objects / Object Handles Visibility in Limit Box .............................................14

2.9 Export CloudWorx-VR data ........................................................................15

2.10 Add Modeled Objects to ScanWorld for TruSpace and TruView ......................15

2.11 Modeled Objects Show in TruView............................................................17

Please also see the section- Add Modeled Objects to ScanWorld for TruSpace and TruView..........................................................................................................17

Example with a large registration.....................................................................18

2.12 Persistent Render Settings-TruSpace........................................................20

2.13 Control Grip Handle Size.........................................................................20

2.14 Publisher Control Default Units ................................................................21

Publish Scanner Location Meta Data...............................................................21

2.15 ..............................................................................................................21

2.16 Two ways to import C10 data..................................................................21

2.17 Create Special Folders............................................................................22

2.18 Export RGB and Intensity via ASCII Export................................................22

2.19 New location for the HostID.txt file for licensing .........................................22

How to unhide the AppData Folder for Windows7\Vista and the Application Data folder

for XP..........................................................................................................23

Cyclone 7.1\TruView



1 Summary of features

1.1 Registration\Target acquisition

• Automated Target Matching New Command in Registration window-Advances Auto-Add Constraints A new constraint creating routine in registration that prioritizes target position

over target ID; Faster\better results can be achieved especially if there are at least 3 target constraints between each ScanWorld.

• Accepting Acquired Targets- New Acquire Target Dialog Cyclone now asks whether or not you accept the target extraction before the

target is written to the ControlSpace

• Highlight Entire Row in Registration Editor In the Constraint tab of the registration window, when highlighting a single constraint row, the entire row is highlighted making it easier to discern all of the

constraint information in that row.

• Proper sorting of columns in the registration window When the columns are sorted in either tab of the registration window the columns are now properly sorted in either ascending or descending order.

• Traverse enhancements-Traverse editor

Travers information is now saved from the traverse editor to the control spaces and will overwrite existing information (target heights, IDs); as a result, a

traverse that is not complete can be reopened later and all changes make previously will re-appear. The Traverse needs to be verified or applied for the

information to be saved.

• Vertex added to scanner location during traverse

If the user imports a C10 project or fills in the ID and scanner height fields in ScanControl, then a vertex will be created in the ControlSpace at the scanner 0,0,0 location and a scanner height and ID annotation will be added. The

creation of this vertex is preference driven, and the default is set to Automatic.

• Auto-registration with C10 data Data from a C10 project will be imported into Cyclone “already registered” if a field setup was performed while scanning.

Cyclone 7.1\TruView



1.2 ModelSpace

• ScanWorld Centric Viewing Command under: Edit\Modes\Seek Local Mode

A new tool in the ModelSpace which automatically limits the number of ScanWorlds viewed by using a “seek” like tool. The user clicks on a point cloud or object and only the ScanWorlds within the specified radius of the

pick are shown.

• Add Modeled Objects to ScanWorld for TruSpace and TruView Command under ModelSpace Menu and Keyplan. Command- File\Copy Geometric Objects to ScanWorld

• Objects / Object Handles Visibility in Limit Box

Command under: View\Limit Box Clip Geometrics This tool allows the user to clip geometry as well as point clouds when using a limit box.

• Export CloudWorx-VR data

Command under: File\Export CloudWorx VR • Control Grip Handle Size

Command under Preferences: ModelSpace tab –Grip handle size. Controls the graphical size of the handles from 1-10 pixels.

1.3 Cyclone Publisher\ TruView\TruSpace

• Persistent Render Settings-TruSpace

After setting, the settings carry over to other TruSpaces.

• Modeled Objects Show in TruView

Publishes a TruView with objects from a ModelSpace.

• Publisher Control Default Units Publishes a TruView with the default units set from within Cyclone.

• Publish Scanner Location Meta Data Open a registration and go to File\Show diagnostics. Scroll down to find

the Scanner locations, and highlight and copy paste into a text file. Alternatively TruViews can be created, and in the TruView folder there is a file called SWlocation.xml with all the scanner locations in it.

Cyclone 7.1\TruView



1.4 Navigator\General Cyclone • Two ways to import C10 data

There are now two commands from the menu to import a C10 project import. One selects the whole project file and the other allows selection of a project

within the Scanner-Projects Folder. • Apply Multi-Image via Batch

• Create Special Folders

If any special folder is missing under a ScanWorld, you can select the ScanWorld in the navigator and go to the top menu: Create\Repopulate Sub-Folders. This will create any missing folders. Typically it is the image

folder that is missing.

• Export RGB and Intensity via ASCII Export If *.txt format is selected the user will be able to add a column for each of: intensity, red, green, and blue

• New location for the HostID.txt file for licensing

XP C:\Documents and Settings\<username>\Local Settings\Application Data \Leica Geosystems\

Vista / Win7

C:\Users\<username>\AppData\Local\Leica Geosystems\

The Application folder is hidden by default, so if it is not visible go

to Folder options and click the “show hidden files, folders and

drives” option.

2 Feature detail

2.1 Automated target matching

The new Advanced Auto Add Constraint option uses a new algorithm designed to prioritize the position of the targets over the target ID. In many registrations users either do not enter the correct IDs for some targets or do not enter IDs at all. With the old

Cyclone 7.1\TruView



(Classic) Auto Add Constraint routine target IDs are given priority over position. This led to constraints being added that could be bad because of bad target ID’s. In a large

registration with many SWs the result is that many bad constraints are added. The user would then have to manually find the bad constraints and edit them. With the new routine

(Advanced Auto Add constraints) the targets are matched by their position, and then as a final verification the IDs can be used to resolve any conflicts (i.e. SW’s that have very similar target geometry). The result is fewer bad constraints and usually better

registration errors. Both the Classic and new way of adding constraints are available in Cyclone 7.1.

The new command is under the classic one in the registration window and is

called Advanced Auto Add Constraints.

When you invoke the new command, a dialog comes up with 3 main options of how to add constraints. Clicking the information button in the dialog brings up a full explanation of all

options:

Classic Registration

New Registration

Cyclone 7.1\TruView



T1 T2 T3

T1 T2

T3

Using the 3 constraint option SW1 will not get added because it only has 2 matching constraints between SW3 and SW2. SW2 however will work with SW3 because there are 3 matching constraints between them.

T5

1. Add only three or more constraints:

This option searches for target constraints between ScanWorlds with at least three sets of matching targets. An example of this is if T1,

T2 and T3 are present in both ScanWorld 1 and ScanWorld 2.

This option first matches geometry (by

location), then if the Use Target IDs check box is checked, it first compares candidates by

the number of matched IDs, then compares errors to set constraints.

If any ScanWorld has fewer than three targets matching those in another single ScanWorld, then that ScanWorld would not have any constraints added. If this is

the case, then you can always add the constraints manually. This is done by opening each ScanWorld in the viewers in the registration window, picking the

target manually and using the Add Constraint command. Alternatively, if there are many ScanWorlds that have fewer than three constraints, then you can try the "two constraints" option. The 2 constraint option may produce a number of bad

constraints that need to be deleted.

The advantage of the 3 constraint option is that it produces the most valid candidate constraints, and it fixes most mislabeled targets. It does this by

prioritizing the matching of target location patterns over the Target ID, even if you choose the “Target ID" check box.

Example of a registration where a ScanWorld does not have 3 constraints between

itself and one other:

SW3

T1

T2

T6

T6

T2

SW2

T2

T4 T4

T1

T5

SW1

Cyclone 7.1\TruView



2. Only Add 2 or more constraints:

Use this option if the “3 constraint” option does not work or if there are too many ScanWorlds that are not added by the use of the 3 constraint option. This option

searches for constraints between ScanWorlds with at least two sets of matching targets.

You can expect to delete many bad constraints with this option on large registrations with many targets.

3. Add all constraints

This option adds one or more constraints and should only be used if the first two options (1 and 2) do not work. It is recommended to use this option if there are no

targets IDs.

This option searches for constraints between ScanWorlds with at least one set of matching targets.

2.2 Highlight Entire Row in Registration Editor

In the Constraint tab of the registration window, when highlighting a single constraint row the entire row is highlighted making it easier to discern all of the

constraint information in that row.

Cyclone 7.1\TruView



2.3 Proper sorting of columns in the Registration Window When the columns are sorted in either tab of the registration window the columns

are now properly sorted in either ascending or descending order.

2.4 Accepting Acquired Targets- New Acquire Target Dialog

In ScanControl there is an added feature in the Acquire targets dialog under Scanner Control\Acquire Targets:

Added features in the Acquire Targets dialog:

1. You now can now accept the target after inspection using the Accept Target icon button on the top menu:

Clicking this button will add the target to the Control Space.

2. If the target extraction was bad you can re-pick the target area using the icon button without having to pick and re-add the target to the dialog.

3. The box under Added will be checked after you accept a target.

Cyclone 7.1\TruView



2.5 Vertex added to scanner location during traverse If the user imports a C10 project or fills in the ID and scanner height fields in

ScanControl, then a vertex will be created in the ControlSpace at the scanner 0,0,0 location and a scanner height and ID annotation will be added. This vertex is

valuable in the creation of a Traverse using the Traverse editor. Historically a vertex was only created after a Traverse was assembled. Now a user can more easily edit and find errors in a traverse before a registration is created. The creation of this

vertex is preference driven, and the default is set to Automatic.

The preference that controls the creation of the vertex is under the Scan tab:

• No-a vertex will not be created upon project import • Yes- a vertex will always be created upon project import.

• Automatic- a vertex will only be created if Cyclone detects that a field set up was performed while scanning with the MMI on the C10.

2.6 Auto-registration with C10 data Data from a C10 project will be imported into Cyclone “already registered” if a field setup was performed while scanning.

The MMI will assign a global coordinate system, using Known Coordinates, to each

ScanWorld if Setup in the MMI was used while scanning. When the project folder is imported into Cyclone the ScanWorlds come into Cyclone in a global coordinate system. Then Cyclone creates a registration and registers the ScanWorlds (no

constraints are created because the ScanWorlds are already in the global coordinate system), then the registration is frozen and a registration ScanWorld and

ModelSpace is created.

Please be aware that if you use this registration method that no constraint error report or traverse report is generated.

If you want a constraint error report then you need to unfreeze the registration and use Auto-Add constraints to re-register the ScanWorlds

using Cyclone registration.

Cyclone 7.1\TruView



If you want a traverse report to need to unfreeze the registration and re-register using the traverse editor.

This is a preference driven option under the Scan Tab:

• No- the data come in without global coordinates assigned to the ScanWorlds (normal import of the data)

• Yes- the data will always come in with global coordinate assigned to the ScanWorlds and the ScanWorlds will be Auto-registered whether or not field

setup was used on the MMI while scanning. • Automatic- the data will only come in with global coordinate assigned to the

ScanWorlds and be Auto-registered only if a field setup was used on the MMI

while scanning.

2.7 ScanWorld Centric Viewing This tool automatically limits the number of ScanWorld viewed by using a “seek” like

mode. The user clicks on a point cloud or object and only the ScanWorlds within the specified radius of the pick are shown.

Command under: Edit\Modes\Show Local Mode and Edit\Modes\Local Seek or use

the icons on the Modes tool bar:

1. To start Show Local Mode click the Show Local Mode Icon

2. Then Select the icon to start the Local Seek function. Click on a cloud or object while in this mode.

3. Only the ScanWorlds within the default radius of 10m will show after you click on

a cloud or object.

4. You can also use the regular seek mode to click on visible clouds to re-center your view.

5. To show all clouds again just exit Local mode by clicking on the Show Local

Mode Icon again to exit local mode.

Cyclone 7.1\TruView



Options

• Holding down in the CTRL key while picking keeps the mode active for the next pick.

Otherwise you have to re-pick on the icon then pick on the cloud or object. • Google Street view style viewing

• Turn on the ScanWorld locations under View\TruSpace\Show ScanWorlds.

Then double click the ScanWorld icons in view mode. You will be put

into panoramic mode . Just click on the next ScanWorld icon to jump to the

next ScanWorld location.

• You can also click on the icon and then click on a ScanWorld icon in the ModelSpace to center the view on that ScanWorld and apply the local seek radius.

Click here in

mode to jump to the next ScanWorld

location

Cyclone 7.1\TruView



Shown below is an example of a set of ScanWorlds before and after a Local Seek mode

pick. The radius of the Local seek is a preference under the ModelSpace tab called Viewer: Local ScanWorld Radius. The default is 10 meters.

Before pick: All ScanWorlds are shown

Cyclone 7.1\TruView



After Pick: Only ScanWorlds with 10M of the pick are shown

Cyclone 7.1\TruView



2.8 Objects / Object Handles Visibility in Limit Box Command under: View\Limit Box Clip Geometrics This tool allows the user to clip geometry as well as point clouds when using a

limit box.

Here is an example of the new limit box functionality:

Before Limit box placement

After limit box placement and activating the option:

Cyclone 7.1\TruView



2.9 Export CloudWorx-VR data Command under: File\Export CloudWorx VR

This command exports points only to an *.alp file required for the CloudWorx-VR application running inside of 3D MAX or Maya. There is an option when

exporting, either to export one cloud, or separate clouds. It is recommended to export one cloud. However if you export multiple clouds the separate clouds

retain the ScanWorld naming convention in Cyclone.

2.10 Add Modeled Objects to ScanWorld for TruSpace and TruView Command is under the ModelSpace Menu and TruView publisher dialog. Command- Copy Geometric Objects to ScanWorld

This tool copies geometry that exists in a ModelSpace to ScanWorld(s). Then the ScanWorld’s associated TruSpace can be opened showing these objects and a TruView can

be created using these objects.

Concept: A TruView is published from the contents of a TruSpace. A TruSpace is directly connected

to its ScanWorld. To view objects in a TruSpace and or to view them in a TruView the objects must first be copied to the TruSpace. When a user models objects in a

Registration ModelSpace there can be many associated ScanWorlds, so a dialog comes up and asks you which associated ScanWorlds do you wish the objects copied to. Since there can be 100’s of ScanWorlds in a registration, the user is given the choice of selecting

which ScanWorlds to copy the objects to.

There are a few ways to get objects into a ScanWorld: From the TruView settings dialog:

Use this option to automatically create a TruView(s) by copying the objects from a ModelSpace to ALL

ScanWorlds in the registration

Cyclone 7.1\TruView



From a ModelSpace Use this option to choose which ScanWorlds you want the objects copied into.

Open a ModelSpace and go to the top menu-File\Copy Geometric Objects to

ScanWorld. A Dialog will come up and ask which associated ScanWorlds do you want the objects copied into.

If you have opened up a ModelSpace from inside a registration then the available ScanWorlds to copy to will be from that registration. In the above image the user has a

choice of copying to all or just selected ScanWorlds. The available ScanWorlds are from the registration as shown in the image below:

Objects modeled in this ModelSpace can only be copied

to these ScanWorlds

because these are the ScanWorlds that are inside of

the registration

Cyclone 7.1\TruView



2.11 Modeled Objects Show in TruView

Please also see the section- Add Modeled Objects to ScanWorld for TruSpace and TruView Concept: TruViews are published from the contents a TruSpace. In order to publish a

TruView with modeled objects the objects must first be copied to the TruSpace. This is straight forward when working in an unregistered ScanWorld. You simply copy objects

from the ModelSpace to the TruSpace then publish. However users work and model in a Registration ModelSpace where there can be many ScanWorlds in a registration. From this ModelSpace you can still publish TruViews with modeled objects, but you need to be

aware of which ScanWorlds you want to copy the modeled objects into.

Workflow example: From the ModelSpace got to File-Publish TruView. There is a new check box in TruView

settings dialog called Copy Geometric Objects to ScanWorlds. This will copy objects from the current ModelSpace you are viewing to ALL the associated ScanWorlds

TruSpace(s). Then the TruView(s) will be created with these objects.

Please note: if you want control over

which ScanWorlds get objects, you need to use the command File-Copy

Geometric Objects to ScanWorlds. Then you will get a list of ScanWorlds available to copy the objects to. Please

see the section- Add Modeled Objects to ScanWorld for TruSpace and

TruView. Please also see example below.

There is another option called Hide Points Near Geometry. This is a setting that controls whether or not objects will get covered by PointCloud data. The default is usually sufficient to make sure that the objects show on top of any point cloud points.

New Check box location for Copy Geometric Objects to ScanWorlds

Choose this option to publish a

TruView w/o publishing the objects that currently exist in the

TruSpace(s)

Cyclone 7.1\TruView



Example with a large registration :

• A user is modeling in a Registration ModelSpace. This

registration contains 30+ScanWorlds. • The user wants to publish a TruView from this ModelSpace.

• The user wants the modeled objects to only show up in TruViews from ScanWorlds 10,11,13,15 and 16.

• From the registration ModelSpace the user goes to File-

Publish site map. If the user uses this

method for publishing the TruViews, then ALL of the ScanWorlds in

the registration 30+, will get the data copied

into them.

New Check box

Cyclone 7.1\TruView



• But if the user goes to File-Copy Objects to

ScanWorlds first then a dialog comes up and asks which ScanWorlds (TruSpaces) you want

the modeled objects copied into. This way the user has control over which ScanWorlds the objects get copied into. In the case the user has

selected ScanWorlds 10,11,13,14,15 and 16.

• The result of this example is a TruView with all of the ScanWorlds published and ScanWorlds

10,11,13,14,15 and 16 have modeled objects

added to them.

• There is also a check box that will clear the

TruSpaces of existing objects before adding

more objects.

Options and add-ons:

• The check box for Copy Geometric Objects to ScanWorlds will be grayed out and

not usable when publishing a TruView from a Key Plan. To publish from a Key Plan with geometry, first open the registration ModelSpace and use the command File-

Copy geometric object to ScanWorlds first. Then Re-open the Key Plan and publish as normal. The objects are already copied to the ScanWorlds (TruSpaces), so you will see them in the TruViews.

Cyclone 7.1\TruView



2.12 Persistent Render Settings-TruSpace

Once render setting are set in a TruSpace and the user navigates to anther TruSpace from within a TruSpace the render settings persist. The persistence settings are all the settings in the Global Color map dialog and the RGB, Hue or

grayscale setting icons and the point size:

2.13 Control Grip Handle Size Command under Preferences: ModelSpace tab at the bottom –Grip handle size Controls the graphical size of the handles from 1-10-default is 10

This control the size of the grip handles on varies object in the ModelSpace.

Default control grip handle size -10 Grip size set to- 2

Cyclone 7.1\TruView



2.14 Publisher Control Default Units Cyclone now publishes TruView with the default units set from within Cyclone.

When a user opens up a TruView in a Browser the defaults units shown on the left side dialog are now what the user set as default units in Cyclone.

2.15 Publish Scanner Location Meta Data This tool allows the user to export the x,y,z scanner location coordinates in either an XML format for it can be copied from the registration diagnostics dialog.

Open a registration and go to File\Show diagnostics. Scroll down to find the Scanner locations and highlight and copy paste into a text file or a TruView can

be created and in the TruView folder there is a file called SWlocation.xml with all the scanner location in it. Below is an example of the output to an SWlocations.xml file:

2.16 Two ways to import C10 data

There is a workflow change with the addition of these tools. You

no longer can select the top level Scanner_Projects Folder. Now you can directly select the project you want to import.

There are now two commands from the menu to import a C10 project import. One selects the whole project file and the other allows selection of a project within the Scanner-Projects Folder. Users can now browse directly to the project

and either import it fully or import partially.

1. Import ScanStation Project fully imports a selected project folder

2. Import ScanStation C10 Partial Project allows the import of any object in the

project (i.e. Image, bin file, target scan etc)

Cyclone 7.1\TruView



2.17 Create Special Folders If any special folder is missing under a ScanWorld you can select the ScanWorld

in the navigator and go to the top menu: Create\Repopulate Sub-Folders. This will create any missing folders. Typically the image folder is missing when certain file formats get imported. ZFS is one of these types, but there are

others.

2.18 Export RGB and Intensity via ASCII Export If *.txt format is selected the user will be able to add a column for each: intensity, red, green, and blue.

2.19 New location for the HostID.txt file for licensing After installing 7.1 the HostID.txt will be written to the following location:

XP C:\Documents and Settings\<username>\Local Settings\Application Data\Leica Geosystems\ Vista / Win7 C:\Users\<username>\AppData\Local\Leica Geosystems\

Cyclone 7.1\TruView



The Application folder is hidden by default, so if it is not visible go to Folder options and click the “show hidden files,

folders and drives” option.

Please note that the HostID.txt will not be written to Program Files\Leica

Geosystems\Cyclone

You will need administrator privileges to unhide these folders..

How to unhide the AppData Folder for Windows7\Vista and the Application Data folder for XP :

For Windows 7\Vista:

1. Right click Start to open Windows Explorer :

2. Click the Organize button on the top left and click Folder and search options

3. Click the radio button Show

hidden fies, folders and drives

Cyclone 7.1\TruView



For XP:

1. Right click Start to open Windows Explorer :

2. Click the Tools option from the top menu and choose Folder Options…

3. Click the radio button Show hidden files and folders .