How to migrate a p:IGI+ v2 project to p:IGI+ v3.0

Existing p:IGI+ v2 projects must be migrated to p:IGI+ v3.0 to use the latest features and software improvements. Projects created in a p:IGI+ v2 can be opened directly in v3.0. When first opened, required updates, including changes to the property model, run automatically in the background.

Opening a project in v3.0 for the first time may take some time, depending on the project size and the version in which it was last saved. Once saved in the v3.0 format, the project will open normally.

Projects saved in v3.0 cannot be opened in earlier versions.

Due to property model updates that introduce sites and boreholes to replace wells and non-wells, you are advised to run the Site Merge, followed by the Data QC tool, after opening your V2 project.

This guide explains how to migrate an existing p:IGI+ v2 project to p:IGI+ v3.0.

Migrating a project to p:IGI+ v3.0

Step 1: Opening the project in v3.0

Open the v2 project by either:

- Drag the file into the grey workspace, or

- Select Project -> Open and navigate to the file. Note: your file might be in the Open recent list.

Step 2: Save the project in v3.0

Select Project -> Save as...

Assign a file name, then select Save

The project will be saved with a .pigi3 file extension. The original .pigi2 file will remain unchanged but will be closed. The .pigi3 file will automatically open after saving.

Note: Wells that existed in the v2 projects are converted to boreholes in v3 projects:

A Boreholes ‘user’ folder is created in the artefact manager, containing a dynamic sample set for each borehole.

The Sites and boreholes manager displays each borehole attached to an unnamed site.

Note: For any non-well samples, sites are created per sample, also with an empty site name.

Creating Sites

To utilise the new sites and boreholes concept, it is recommended that users run a Site Merge to create the relevant sites in the project prior to running the software’s Data QC tool, especially when there is a plan to load new data to the project.

Step 1: Open Site merge

Select Data -> Site merge…

Step 2: Select criteria for site merge

Choose properties to use for the site merge criteria (only site properties can be selected here) by either:

- Selecting properties from the Available Properties list, or

- Searching in Search for properties and adding them to the Included Properties list.

Note: Default site merge criteria are provided. Often, sites at this point won’t have names, so it is best to proceed with just Lat.Site and Long.Site. Remove Name & Country using

Optional step: Select Set as default to use these criteria for any future site merges.
Choose Merge within a sample set if required.

- Run Site merge on the entire project when first opening a v2 project.

Select Merge sites.

Step 3: Resolve conflicts for site merge

The Site merge stage 2 of 2 window displays a fully transparent summary of the existing sites, those that will merge, and any that could merge but have conflicts.

Proposed site groupings appear on the left.

Details for the proposed site groupings appear on the right (once selected).

Icons next to each site indicate the grouping status of that site's group. Hover over the summary icons for explanation tool tips.

Note: If many conflicts occur, consider refining the merge criteria.

Resolve conflicts using one or a combination of the following methods:

Option 1: Resolve conflicts manually

- Select a candidate site with conflicts
- Select Next conflict >>
- Choose a correct value using the tick boxes

Option 2: Auto-resolve conflicts

- Select Auto-resolve conflicts…
- Choose the required resolution
- Select Apply

Note: Auto-resolution applies to all conflicts, not just the selected item. Use Reset auto-resolved conflicts to undo these changes if needed.

2. After resolving all conflicts, select Confirm site merge.

Creating sites names

Sites were introduced in p:IGI+ v3.0. Projects created in earlier versions will have sites created during migration to v3.0. Site names are assigned using the Data QC tool.

This tool allows you to quickly define the different depth datums for sites & samples, which is important when using depth plots. The tool further allows bulk assignment of site names; where present, it assigns the common elements of Name.Borehole or Location.Site to Name.Site

Step 1: Assign site names using the Data QC tool

Select Data -> Data QC tool

If required, choose a sample set to apply the tool to.

- Run the Data QC tool on the entire project when first opening a v2 project in v3.0. Apply it to individual sample sets only when adding new data to an existing v3.0 project.

Select or deselect tick boxes to choose which rules to apply.

- A set of default parameters is selected. Nothing will happen when a ticked box has a “0” count.

QC actions include:

Defining required datums

Assigning site names from Name.Borehole or Location.Site

Assigning site or sample latitude/longitude where available

Flagging potential depth data issues

If any changes are made to the default rules that you wish to keep, select Set as defaults to retain these for future data QC within the project.
Select Apply.

Result: Site names are created and displayed in the Sites and boreholes manager.

Where borehole names exist, common elements of the Name.Borehole or Location.Site string are assigned as the site name.

Site names are written in the Name.Site property.

Where samples are not associated with a borehole, the site name is assigned from Location.Site string.

Note: Data stored in Location.Sample in v2 projects is migrated to Location.Site when opened in v3.0.