Corelyzer by default visualizes core imagery by placing the image on a horizontal track. A track is just a way of grouping multiple section images. Before you can load an image in Corelyzer, you must first create a track. To create a track you must select the menu "File -> Create a Track", after which you will be prompted to enter a name for a track. Once you do this the Track listbox in the main menu will update.

Figure 5.1. Create a track

Tracks are a way of grouping. Since we have nothing in our grouping/track then nothing in our visualization window will change. Now we add images so that way we can see something and have something to interact with. First, let's remember that our track is a horizontally oriented track, with an increasing depth as we go from left to right. This means we will need images that are horizontally oriented in such a way that they are increasing in depth from left to right.

IODP images are vertical, with increasing depth as you go from top to bottom. Fortunately we have created a Corelyzer Plugin that makes use of CHRONOS webservices to access the JANUS database. The plugin is called the "Chronos-Janus Plugin" and will be discussed later. For now, we will assume that there are some images of core sections that are horizontally oriented, with an increasing depth from left to right.

If you know the images' orientation, you can also specify that individually in the image loading dialog shown below.

We also have to make sure that your images have the correct dots-per-inch (DPI). Why does the DPI of the image matter? This is discussed in detail in the appendix. It basically establish the correct mapping between the image dimension to the physical core dimensions.

How do you know what is the right DPI of your image? This all depends on the equipment in which the image was retrieved. Usually most line-scan cameras that are manufactured for the creations of high-resolution digital line scan images of core sections have this indicated in the advertisements of the scanner. Unfortunately, it seems that most of the scanners don't save off the correct DPI. There is a quick and dirty way of checking and making sure the DPI is correct in the section Making Sure the DPI of an Image is Correct. Or in the image loading dialog below, you can also specify the core section image's length, the DPI values will be calculated by Corelyzer.

5.1. Load Images from local files

So now we will assume that the images are:

• Horizontally oriented

• Have an increasing depth from left to right

• Have the correct dots-per-inch (DPI)

To bring up the file selection dialog to tell Corelyzer which images to load, we need to first select the grouping track in the track list, and then select the menu item "File -> Open Image Files...".

The “Load Images” dialog will pop up and allow you to load the section images with properties like, orientation (vertical or horizontal), length, DPI, and starting depth (in meters) of the section image etc. The upper-right of the dialog is an Excel-like table. Click on the "Select Image Files" button to fill the table with core section images. You can double-click each cell to make individual modifications. Press "Enter" when you finish editing a cell. Note that if you leave the DPI_X and DPI_Y value as 0, the length value will be used with image dimensions to calculate DPI values.

Also, you can enable the "Batch input" checkbox to fill the table parameters. You can select orientation, length, DPI, and start depth and depth increment. Click on "Apply" button will update and fill specified parameters into the table above.

Click “OK” button when you are satisfied with the table content. Corelyzer will start loading selected images with specified parameters.

Figure 5.2. Load Images dialog

Once completed the visualization window will display our imagery, and the Section listbox in the main iCores control window will update with the image filenames loaded on the Track. Notice in the image below that our image has a ruler in it, and that the ruler in the image closely matches the markers indicating depth at the bottom of the visualization window.

Figure 5.3. Visualization canvas with loaded core section images

A screen capture video of these actions can be found in this link online (size: 3.5MB).