You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 83 Next »

Table of Contents


IMS graphic user interface for WRMSL and STMSL.


I. Introduction

The Whole-Round Multisensor Logger (WRMSL) and Special Task Multisensor Logger (STMSL) can simultaneously measure several parameters (e.g., density by gamma ray attenuation (GRA), magnetic susceptibility (MS), and P-wave velocity [PWL]) on whole round core sections. These loggers are nondestructive to sediment fabric. The data generated can be used as proxies for other data. The data is used to facilitate core-core, core-log, and core-log-seismic integration and to construct composite sections. Optimal measurements require a completely filled core liner with minimal drilling disturbance.

Logger sensors currently included on these logger systems:

  • Gamma ray attenuation (GRA) densitometer
  • Magnetic susceptibility loop (MS)
  • P-Wave velocity logger (PWL)

The WRMSL and STMSL are the only two systems, which allow continuous core section measurements, one after another.
Note: Both tracks function the same way; however, WRMSL measures density, magnetic susceptibility and P wave velocity, whereas STMSL only measures density and magnetic susceptibility.

II. Procedures

A. Preparing the Instrument

  1. Double-click the MUT icon on the desktop (Figure 1a) and login using ship credentials. For more information on data uploading see the "Uploading Data to LIMS" section below.
  2. Double-click the IMS icon (Figure 1b). IMS initializes the instrument. Once initialized, the logger is ready to measure the first section.


Figure 1. (a) MUT Icon. (b) IMS Icon.

At launch, IMS begins an initialization process:

  • Testing instrument communications
  • Reloading configuration values
  • Homing the pusher arm of the motion control system.

After successful initialization, the IMS Control and Instruments' windows appear (Figure 2).


Figure 2. IMS Control window (left) and Instrument' windows (right).

B. Instrument Calibration

To access an instrument's calibration procedure, click on the Instruments menu and select the instrument's calibration function. Good practice is to calibrate the instrument prior to receiving cores at each new site.


GRA: Standard Set Editor

The GRA standard is an aluminum bar inserted into a core liner, which is filled with DI water and sealed. The aluminum bar is machined into discrete steps that provide composite density values for creating a calibration curve of counts vs. density.

Before calibration, use the Standard Editor to enter offset and thickness of each step's center. Under the Instrument menu, select GRA: Edit Standards to view the GRA Standard Edit window (Figure 3).

NOTE: This only has to be done once, in order to add a new standard, as the values are retained in the configuration file. It is important to check the offset values against the standard because the standard can shift within the liner. 


Figure 3. GRA Standard Edits window.


Define two standard sets in the Standard Editor: Aluminum Steps (density) and Density Check (water).

  • Aluminum Steps : The offset (measured from liner top to center of step) and the thickness of each step are the values shown in the diagram above. Define the offsets in the order they are measured on the track.
  • Density Check: (1) Define an offset past the aluminum standard and (2) Enter water density (1 g/cm3) as the given value. The water measurement is used to validate the density calibration.


GRA Calibration Process

  1. In the Instruments menu, select GRA: Calibration.
  2. A window will pop-up asking to place the standard on the track (Figure 4).

Figure 4. First GRA Calibration window.


      3. Place the standard on the track with the Aluminum in the standard (Blue side) toward the GRA sensor. The bottom of the standard should be inserted into the slot of the arm plate. First loosen the plate to allow it to move. Click OK.

      4. The pusher moves the standard until it trips the top-of-section sensor, then moves the standard to all of the defined offsets, taking a measurement at each position. After measuring the last step, the pusher moves the standard to the offset for the water measurement.

      5. After the standard is measured, the calibration data displays in the graph along with the calibration line (Figure 5).

     6. Using the new calibration data, a density value for water is calculated and compared to the known value of 1 gm/cm3. The curve fit provides the coefficients used in the density calculations, ln I = B(μd) + C; where μ= Compton attenuation coefficient, d = sample diameter, I0 = gamma ray source intensity, and I = measured intensity of gamma rays passing through the sample. Allowing bulk density to calculated by using, ρ = 1/(μd) × ln (I0/I).

     7. Choose to apply the calibration to all future measurements by clicking Accept Calibration or click Cancel Calibration to restore the previous values.


Figure 5. GRA Calibration window.


     8. Last accepted calibration could be reviewed under Instruments > GRA: Setup (Figure 6).


Figure 6. GRA Setup window.


PWL Calibration process

  1. In the Instrument menu, select PWAVE: Calibrate-Utility and the PWAVE Calibration Utility window will open (Figure 7).
  2. Follow the steps on the right side of the PWAVE Calibration Utility window. Note: Liner Delay correction is excluded when using the Aluminum standard.

  3. Place the aluminum standard between the transducers. Close the transducers. Aluminum standard width is 76.25 mm. Select Laser Offset Correction. Confirm that the Distance matches the standard's width.

  4. Enter the Aluminum Standard velocity. 6295.00 m/s. Select Determine System Delay. Verify that the Velocity matches the Aluminum Standard's velocity.

  5. Open transducers. Remove Aluminum Standard.

  6. Position the Water Standard between transducers. Close transducers. Turn on Liner Delay. Enter the water's temperature (Water at room Temperature) under Temperature. Select Auto H2O Velocity Update. Liner Thickness is 2.58 mm. Click Determine Liner Velocity.

  7. Accept Changes.
  8. Open transducers and remove the water standard.

Figure 7. P-Wave Calibration Utility. 


        9. Last accepted calibration could be reviewed under Instruments > PWAVE: Setup (Figure 8).


Figure 8. Pwave Setup window.


Adjusting Measurement Parameters for the Waveform

Use the Stack slider in the PWAVE CalibrationUtility window to adjust the measurement parameters to obtain a better waveform (Figure 7). These parameters may need to be adjusted if the section material has changed.

Stack: Sets the number of waveforms to average to increase the signal-to-noise ratio. Note: Stack should not be any lower than 50.


Correction for acoustic velocity through water

In the calibration process, the PWL uses the P-wave speed through water for deriving the velocity through the CAB core liner. The acoustic velocity through distilled water is based on the equation of Marczak (1997);

Vp_water = 1402.385 + 5.038813T - 5.799136E-02T^2 + 3.287156E-04T^3 - 1.398845E-06T^4 + 2.787860E-09T^5

The National Physical Laboratory (NPL) gives a brief summary of this and other equations. Marczak's equation fits a 5th order polynomial through 3 published sound-wave-speed-in-water datasets. There are other equations with many more coefficients and some that also account for variations in pressure (or depth) and salinity. Given that we operate at 1 atm and use distilled water, there is no need for more complex equations. Variations from one equation to another and to fits of the observations tend to have quoted differences and standard errors less than 0.02 m/s.  Even given errors of about 0.2°C in temperature measurements, we should still be good to better than 1 m/s.

References

W. Marczak (1997), Water as a standard in the measurements of speed of sound in liquids. J. Acoust. Soc. Am. 102, 2776-2779.

National Physical Laboratory links with information, references, and online Vp calculators for water:
http://resource.npl.co.uk/acoustics/techguides/soundpurewater/content.html#BILANIUK
http://resource.npl.co.uk/acoustics/techguides/soundpurewater/marczak.html  <- Calculator for Marczak’s equation


C. Set Measurement Parameters

The five buttons on the  IMS Control window provide access to utilities/editors via drop-down menus (Figure 9).



Figure 9. Five buttons from IMS Control window. Menus within each button.


Click on the Instruments menu to select each instrument's Setup Editor (Figure 10, 11, and 12). In general, the values shown in the Setup Editor rarely need to be changed. Regardless, check these values at the beginning of every expedition.

Note: Do not change these values without reading the vendor's documentation.

GRA: Setup


General Information (Figure 10)

Instrument X Offset: Offset along the X-axis (push direction) from the home switch to the center of the gamma ray source collimator. Set at 191.64 cm.
Sensor Width: Width along the core axis that influences the measured value; used in calculating edge clearance (if enabled).
Analysis Name: Defined JR_LIMS analysis.
Instrument Group: Defined JR_LIMS instrument group component.
Model: Instrument model number/name of the sensing component.
S/N: Instrument serial number of the sensing component.
Manufactor's Name: Name of the manufacturer of the sensing component of the instrument.
Menu Name: Name used in the IMS menus
Full Name: Name used in IMS Reports and displays.


Instrument-Specific Information (digiBase Detector)

Detector Address: Instrument unique addressing ID set with the MAESTRO software provided by the vendor.
High Voltage: High voltage value applied to the photomultiplier tube.
Fine Gain: Used in conjunction with coarse gain (jumper setting in the digiBase) to amplify the signal. Affects the peak's position and width in the reported channels.
Peak Quality: Used to determine the quality of the Gaussian peak fit over the Cs peak (empirically determined).
Start Channel: Start channel of the ROI (region-of-interest).
ROI Channel Width: Number of channels for the ROI.
Display Width: Width of display about the peak center during acquisition.







Figure 10. WRMSL (up) and STMSL (down) GRA Setup Editor.



MS2: Setup


General Information (Figure 11)

Instrument X Offset: Offset along the X-axis (push direction) from the home switch to the center of the MS loop. Set at 221.64 cm.
Contact Width: Width along the core axis that influences the measured value; used when calculating edge clearance (if enabled).
Units: Set to SI; must match the physical MS meter setting.
Range: Set to 1.0; must match the physical MS meter setting.
Analysis Name: Defined JR_LIMS analysis.
Instrument Group: Defined JR_LIMS instrument group component.
Meter Model: Instrument model number/name of the sensing component.
Meter S/N: Instrument serial number of the sensing component.

Sensor Model: Sensor's model numberof the active component

Sensor S/N: Sensor's serial number of the active component
Manufactor's Name: Name of the manufacturer of the sensing component of the instrument.
Menu Name: Name used in the IMS menus.
Full Name: Name used in IMS Reports and displays.

Check Loop: If ON, check for the presence of an object within the loop before zeroing the meter.


Standard Information

Correction Factor: The vendor provides this value.

  • For standard-frequency loops (80 and 90 mm, 565 Hz), this value is 1.000.
  • For 10% high loops (80 mm only, 621 Hz), this value is 0.908.
  • For 10% low loops (80 mm only, 513 Hz), this value is 1.099.
  • For 20% low loops (90 mm only, 452 Hz), this value is 1.174.



Figure 11. STMSL (right) and WRMSL (left) MS Parameters Setup window.


PWAVE: Setup


General Information (Figure 8)

Instrument X Offset: Offset along the X-axis (push direction) from the home switch to the center of the PWL transducers. Set at 251.64 cm.
Contact Width: Width along the core axis that influences the measured value used when calculating edge clearance (if enabled).
Analysis Name: Defined LIMS analysis value.
Instrument Group: Defined LIMS instrument group component.
Model: Instrument model number/name of the sensing component.
S/N: Instrument serial number of the sensing component.
Manufactor's Name: Name of the manufacturer of the sensing component of the instrument
Menu Name: Name used in the IMS menus.
Full Name: Name used in IMS Reports and displays.


Liner Correction

Liner Thickness: Thickness of the core liner (2.58 mm).
Liner Velocity: Acoustic velocity of the core liner (butyrate). Should be 2100 ± 40 m/s.
Liner Delay: Calculated value equivalent to the liner thickness divided by the liner velocity.


Velocity Filter

The filter purpose is to remove extremely low or high velocities.
Velocity Filter: Enable or disable filtering.
Min Velocity Filter: Velocities below this value are not reported.
Max Velocity Filter: Velocities above this value are not reported.


Stacking

Waveform Stack: The number of waveforms stacked and averaged. Minimum 50.


D. Preparing Sections

Core sections measured on the WRMSL and STMSL can be run either immediately after "Core on Deck" or after they have reached temperature equilibrium. Pwave velocity if affected by temperature and should be run at a constant temperature for each section. We suggest room temperature (~ 19°C). Reach temperature equilibrium takes approximately 4 hours.

E. Making a Measurement


The WRMSL and STMSL are push tracks; each section pushes the previous section(s) through a set of instruments. Although it is possible to continuously process cores without a break, some of the instruments require a periodic background measurement to check and correct, if necessary, sensor drift.

By convention, we break the sequence of sections for background measurement between succeeding cores. Therefore, the functional definition of a sequence starts with the launch of IMS or with the first section measured after the "pusher" (piece of core liner filled with DI water long enough to push the end of the last section through the last sensor on the track) and ends the next time the "pusher" is used. Generally, this corresponds to the first and last section of a core.

  1. Place the whole-round section on the track between the top-of-section sensor and the pusher arm (Figure 12).

Figure 12. Blue end cap near the top-of-section sensor, clear end (bottom of section) touching the pusher.


2. Orient the section with the blue endcap towards the top-of-section sensor with working label (W) UP.

3. Click START to open the Section Information window. 

4. When the Section Information window opens (Figure 13), the cursor should be in the SCAN input box. If not, click in the box. NOTE: Not having the cursor in this box will prevent the label from been scanned.

Figure 13. Section Information scanning window.

5. Hold the scanner over the label and pull the trigger.

6. At the scanner beep, the Sample_ID and the LIMS_ID should correctly display on the screen. If not, re-scan.

7. If the top of the section is missing because a whole-round sample was removed, enter the length of the missing interval in the left hand area (Figure 13) so the sample position can be corrected. DO NOT place any type of spacer in front of the section to make up for the missing interval. Whole-rounds taken from the bottom of the section will not affect the measurement process.

8. Click Measure. The pusher arm moves forward and pushes the section until the blue endcap breaks the light beam of the sensor. The pusher then moves the section into the first measurement position and triggers the instruments to measure.

9. The move and measure process repeats until the pusher arm reaches its motion limits. The pusher retracts to the home position, ready to receive the next section. The Section Information window opens to repeat the process.

10. After the last section use the "water pusher". Click the PUSHER END SEQUENCE (Figure 14) button located in the Section Information window.

Figure 14. End of Sequence Pusher button.


11. Clicking Cancel button (and confirming) will cause loss of data for the sections which have not completed all of their measurements for a particular instrument. 

Note:  The label ID is used to query LIMS for the curated length. If not connected to the web servers, the length in the label bar code is used. Knowing the length is not critical, as the track will actually measure the length as part of its section handling process. 


F. Quality Assurance/Quality Control


Analytical Batch

The analytical batch is defined by the number of samples run between each sensor calibration. Calibrations and calibration timestamps are accessible through each sensor Instrument Interface screen.


Calibration

GRA

Calibration assumes a two-phase system model for sediments and rocks: minerals and interstitial water. Aluminum has an attenuation coefficient similar to common minerals and is used as the mineral phase standard. Pure water is used as the interstitial water phase standard. A piece of core liner containing a telescoping aluminum rod (5 varying thicknesses) and filled with distilled water is measured as a calibration standard. The largest diameter aluminum rod has a porosity of 0% and a bulk density of 2.7 g/cm3. Water has a porosity of 100% and density of 1.00 g/cm3. Intermediate elements verify the linearity of the log density relationship and the alignment of core and sensor. A linear least-squares fit through 3–5 calibration points yields the calibration coefficient. Total measured counts are divided by the counting time to normalize coefficients to counts per second.

MSL

Absolute susceptibility: Sample cubes are measured using the Kappabridge and results compared with corresponding readings from the Bartington instrument. Empirical correction factors have been calculated.

PWL

Pulse detection settings are checked by IODP technicians on a regular basis and do not require adjustments by the user. Pulse time is a constant which is included in the total time measured as a result of the threshold peak detection procedure used. This value changes depending on the wiring of the system. The user does not need to make adjustments to this factor. Transducer displacement and travel time delay calibrations are performed using an Aluminum standard of known velocity and thickness and distilled water at room temperature.


Accuracy

GRA

GRA accuracy is limited by the assumption that the measured material has the same attenuation coefficient as the calibration standards used. For general sediment-water mixtures, this should be the case and error should be <5%.

MSL

Accuracy of the susceptibility meter and sensor loop is 5% (according to Bartington).

PWL

PWL accuracy can be evaluated by measuring pure water at varying and exactly known temperatures. Past experience shows that for a properly calibrated system and good acoustic coupling, the disagreement with published sonic velocity values is less than ±20 m/s.


Precision

GRA

GRA precision is proportional to the square root of the counts measured, as gamma ray emission is subject to Poisson statistics. Measurements with the system have typical count rates of 10,000 (dense rock) to 20,000 (soft mud). If measured for 4 s, statistical error is <40,000 ± 200 cps, or 0.5%.

MSL

MSL precision is 2 x 10–6 SI. Susceptibility values in natural marine sediment samples over an interval of only a few meters (Milankovitch or millennial scale cyclicity) can range from a few tens to several thousands of 10–6 SI units. Typically, variations are 2–3 orders of magnitude greater than the precision, making magnetic susceptibility one of the most precise proxies for stratigraphic changes.

PWL

Measurements on standard materials such as water and calibration standards are repeatable within ±1 km/s.

III. Uploading Data to LIMS


A. Data Upload Procedure

To upload the images into the database (LIMS) MegaUploadaTron (MUT) program must be running in background.

If not already started do the following:

  1. On the desktop click the MUT icon on the bottom task bar (Figure 15) and login with ship credentials. The LIMS Uploader window will appear (Figure 16).
  2. Once activated, the list of files from the C:\DATA\IN directory is displayed. Files are marked ready for upload by a green check mark.


Figure 15. MUT icon



Figure 16. LIMS Uploader window


3. To manually upload files, check each file individually and clip upload. To automatically upload files, click on the Automatic Upload checkbox. The window can be minimized and MUT will be running in the background.

4. If files are marked by a purple question mark or red and white X icons, please contact a technician.
    Purple question mark: Cannot identify the file.

    Red and white X icons: Contains file errors.

5. Upon upload, data is moved to C:\DATA\Archive. If upload is unsuccessful, data is automatically moved to C:\DATA\Error. Please contact the PP technician is this occurs.


Data File Formats

The files generated by the whole round tracks (WRMSL and STMSL) include:

GRA Files

  • i_pi_gra.ini: A file containing the configuration information related to the GRA setup at the time of the measurement
  • .GRA: A data file containing all of the GRA raw measurements for a section of core.  Data include: offset, bulk density, total counts per second and a time stamp.

Magnetic Susceptibility Files

  • i_pi_ms.ini:  A file containing the configuration information related to the MS loop at the time of the measurement. 
  • .MS: A data file containing all of the magnetic susceptibility measurements for a section of core.  Data include offset, magnetic susceptibility, and a time stamp.  The file also includes the range and units and serial number of the magnetic susceptibility meter used.
  • *_MS.csv: A .csv file, saved in C:/Aux_Data, containing the mean magnetic susceptibility values for each measurement along a section as well as the range and units used at the time of measurement.

P-Wave Files

  • i_pi_pwave.ini: A file containing the configuration information related to the PWAVE instrument at the time of the given measurement
  • .PWAVE_L: A data file containing the pwave logger measurements for a section of core.  Data include: offset, distance in the caliper, travel time, and the velocity.
  • *_PWAVE-L.csv: A .csv file containing the raw waveform data for a section of core as well as the offset, velocity, travel time, distance between calipers, liner thickness, system delay, a time stamp, and laser distance.
    • System Delay is the sum of delays and includes: Travel time across the transducer caps, and electronic delays in the pulser and the digitizer.


B. View and Verify Data


Data Available in LIVE

The data measured on each instrument can be viewed in real time on the LIMS information viewer (LIVE).

Choose the appropriate template (Ex: PHYS_PROPS_Summary), Expedition, Site, Hole or the needed restrictions and click View Data. The requested data will be displayed. You can travel in them by clicking on each of each core or section, which will enlarge the image.


Data Available in LORE

Each data set from the Whole Round Logger tracks (WRMSL/STMSL) is written to a file by section.  The data for the GRA, MS Loop, and P-wave are each displayed under a different report in LORE.  These reports are found under the Physical Properties heading and include Gamma Ray Attenuation Bulk Density (GRA). Magnetic Susceptibility Pass-through (MS), and P-wave Velocity Logger System (PWL). The expanded reports include the linked original data files and more detailed information regarding the measurement.


GRA Standard Report

  • Exp: Expedition number
  • Site: Site number
  • Hole: Hole number
  • Core: Core number
  • Type: Type indicates the coring tool used to recover the core (typical types are F, H, R, X).
  • Sect: Section number
  • A/W: Archive (A) or working (W) section half.
  • Offset (cm): Position of the observation made, measured relative to the top of a section.
  • Depth CSF-A (m): Location of the observation expressed relative to the top of a hole.
  • Depth [other] (m): Location of the observation expressed relative to the top of a hole. The location is presented in a scale selected by the science party or the report user.
  • Bulk density (GRA) (g/cm3): Computed bulk density of sample.
  • Timestamp (UTC): Point in time at which an observation or set of observations was made on the logger.
  • Instrument: Abbreviation or mnemonic for the GRA sensing device used to make this observation (GRA1 or GRA2).
  • Instrument group: Abbreviation or mnemonic for the data collection device (logger) used to acquire this observation (WRMSL or STMSL).
  • Text ID: Automatically generated unique database identifier for a sample, visible on printed labels.
  • Test No: Unique number associated with the instrument measurement steps that produced these data.
  • Comments: Observer's notes about a measurement, the sample, or the measurement process.


Magnetic Susceptibility Standard Report

  • Exp: Expedition number
  • Site: Site number
  • Hole: Hole number
  • Core: Core number
  • Type: Type indicates the coring tool used to recover the core (typical types are F, H, R, X).
  • Sect: Section number
  • A/W: Archive (A) or working (W) section half.
  • Offset (cm): Position of the observation made, measured relative to the top of a section or section half.
  • Depth CSF-A (m): Location of the observation expressed relative to the top of a hole.
  • Depth [other] (m): Location of the observation expressed relative to the top of a hole. The location is presented in a scale selected by the science party or the report user.
  • Magnetic susceptibility (instr. units): Magnetic susceptibility of the sample, not volume corrected.
  • Timestamp (UTC): Point in time at which an observation or set of observations was made on the logger.
  • Instrument: An abbreviation or mnemonic for the MS sensing device used to make this observation (MSLP_477 or MSLP_476).
  • Instrument group: Abbreviation or mnemonic for the data collection device (logger) used to acquire this observation (WRMSL or STMSL).
  • Text ID: Automatically generated unique database identifier for a sample, visible on printed labels.
  • Test No: Unique number associated with the instrument measurement steps that produced these data.
  • Comments: Observer's notes about a measurement, the sample, or the measurement process.


P-Wave Standard Report

  • Exp: Expedition number
  • Site: Site number
  • Hole: Hole number
  • Core: Core number
  • Type: Type indicates the coring tool used to recover the core (typical types are F, H, R, X).
  • Sect: Section number
  • A/W: Archive (A) or working (W) section half.
  • Offset (cm): Position of the observation made, measured relative to the top of a section or section half.
  • Depth CSF-A (m): Location of the observation expressed relative to the top of a hole.
  • Depth [other] (m): Location of the observation expressed relative to the top of a hole. The location is presented in a scale selected by the science party or the report user.
  • P-wave velocity xy (m/s): Velocity of pressure wave through sample in the x-y plane (dependent on orientation of the material).
  • Caliper separation (mm): Displacement between the faces of the transducers in contact with the sample.
  • Sonic traveltime (µs): Traveltime of the sonic wave from transducer to transducer through the sample.
  • Timestamp (UTC): Point in time at which the observation or set of observations was made on the logger.
  • Instrument: An abbreviation or mnemonic for the P-wave sensing device used to make this observation (PWL).
  • Instrument group: Abbreviation or mnemonic for the data collection device (logger) used to acquire this observation (WRMSL).
  • Text ID: Automatically generated unique database identifier for a sample, visible on printed labels.
  • Test No: Unique number associated with the instrument measurement steps that produced these data.
  • Comments: Observer's notes about a measurement, the sample, or the measurement process.


C. Retrieve Data from LIMS

Expedition data can be downloaded from the database using the instrument Expanded Report on Download LIMS core data (LORE).


IV. Appendix


A.1 Health, Safety & Environment

Safety

  • Keep extraneous items and body parts away from the moving platform, belt, and motor.
  • The track system has a well-marked emergency stop button to halt the system if needed.
  • Don't insert your hand between the GRA source and the detector.
  • Do not look directly into the laser light source.
  • Do not attempt to work on the system while a measurement is in progress.
  • Do not lean over or onto the track.
  • Do not stack anything on the track.
  • This analytical system does not require personal protective equipment.


Pollution Prevention

This procedure does not generate heat or gases and requires no containment equipment.


A.2 Maintenance and Troubleshooting


Troubleshooting


  1. Pwave values are within the filter range, but values are being excluded/not saved.  This may even occur when the filter is turned off.
    • Check the amplitude of the wave forms.  If the first arrival signal is being clipped, then the software will 'filter' that data point.  Lower the stack value or adjust the gain down on the pulsar/receiver to reduce the amplitude of the wave forms.  Figure below illustrates a 'clipped signal' and the velocity out of bounds indicator is lit.  Second figure illustrates a waveform that is not clipped after the gain was adjusted.

A.3 Installation of GRA digiBASE

Unscrew the detector frame and take it out. Lift the detector structure carefully (due to the lead contained it is heavy), the digiBABSE and the photo multiplier are inside, only plugged by a USB cable. 



Unplugged the cable from the base and disconnect it from the detector.


Disconnect the base from the photo multiplier.



Proceed in reverse to install the new base.

In order for IMS to recognize the base it is necessary to open MCB Configuration program.

It will automatically look for new instruments and display them. Select the instrument and click Renumber New.



B.1 IMS Program Structure


a) IMS Program Structure

IMS is a modular program. Individual modules are as follows:

  • Config Files: Unique for each track. Used for initialize the track and set up default parameters.
  • Documents: Important Information related with configuration setup.
  • Error: IMS error file.
  • FRIENDS: Systems that use IMS but don't use DAQ Engine.
  • IMS Common: Programs that are used by different instruments.
  • PLUG-INS: Code for each of the instruments. 
  • Projects: Main IMS libraries.
  • Resources: Other information and programs needed to run IMS.
  • UI: User Interface
  • X-CONFIG: .ini files, specifics for each instrument.
  • MOTION plug-in: Codes for the motion control system.
  • DAQ Engine: Code that organizes INST and MOTION plug-ins into a track system.

The IMS Main User Interface (IMS-UI) calls these modules, instructs them to initialize, and provides a user interface to their functionality.

The WRMSL and STMSL systems are built with three INST modules (Gamma Ray Attenuation, P-wave, and Magnetic Susceptibility), one MOTION module, and one DAQ Engine module. Each module manages a configuration file that opens the IMS program at the same state it was when previously closed and provides utilities for user edit or modification of the configuration data and calibration routines.


b) Communication and Control Setup


Data communication and control is USB based and managed via National Instrument’s Measurement & Automation Explorer (NI-MAX). When you open NI-MAX and expand the Device and Interface section.  The correct communications setup can be found at IMS Hardware Communications Setup.

B.2 Motion Control Setup

The track's push system consists of a NSK linear actuator driven by Schneider Electric stepping motor: MDrive23. The MDrive 23 is a high torque 1.8º integrated motor-driver-controller that connects to the PC via USB-RS485 cable. An IODP-built interface board (Figure 17) provides power control, emergency, limit/home switches, specialty I/O connections, and status lights. With the exception of a built in "Home" function, the MDive's IMS motion software module provides direct control of the motor's functions. The motor can be installed directly out of the box without any special preparation.

At IMS launch, a series of commands are sent to place the motor into a known state and then to search for the home switch and zero the encoder's position out put.

It is assumed that the hardware has been installed correctly and powered up. On the very first launch, a set of default values will be loaded that should get the track safely running. BUT BE READY to kill the motion using the Emergency-Stop button. Generally, a run-off is caused by incorrect scaling factors for the gear ratio, screw pitch, and or encoder counts per revolution. Setting these up correctly usually correct the issue.

Note: If the motor fails to initialize or locate the home switch, then an error will be reported. At this point, access the motion control utilities for trouble shooting. The START button will not appear and measurements are prevented.



Figure 17. Interface board for motion control.


MDrive Setup

Select Setup from the Motion menu bar for MDrive Motion control window (Figure 18).




Figure 18. MDrive Motion Control window.

Track Options

Click Motor and Track Options to open the Track Motor Setup (Figure 19). Here is where the relationship between motor revolutions and linear motion of the track is defined.

Select Axis: In the case of the WRMSL and STMSL, it is always X.

Encoder Pulses/rev: Defined by the manufacturer of the MDrive as 2048.

Screw Pitch: Defined by the NSK actuator manufacturer as 2 cm/screw revolution.

Gear Ratio: In the current configuration, this is 4 to 1 but it can be changed.

Direction: The WRMSL is a right-hand track and a CCW rotation moves the pusher in a positive (from home to end of track) direction. The STMSL is a left-hand track so this value is set to CW. Now both are set as CCW.

Click Motion Utility to test these settings.
Click Accept to save the values or Cancel to return to the previous values.



Figure 19. Track Motor Setup window.


Fixed Positions

Click Fixed Positions to open the Track Configuration window (Figure 20). In this window, define fixed track locations (Figure 21) used by IMS and enable the top of section (TOS) switch and the runout switch (ROS).



Figure 20. Track Configuration window.


Select Axis: In the case of the WRMSL and STMSL it is always X.
Max Section Length: Maximum length of section that can be placed in the track and still expect the track to handle and measure correctly. This value is set to 160 cm.
Track length: Distance in cm between the limit switches. Use the motion Utility to determine this value. This value is set to 200 cm.
Load and Unload: Offset in cm where the track will stop when ready to load a new section of core. In the case of both the WRMSL and STMSL, this the same as the home switch.
Top-of-Section Switch: THIS MUST ALWAYS BE enabled! The IMS software uses this switch to determine the physical length of the section, which is critical to the calculations that move the cores through the sensor. Without a TOS switch, the track is not functional.
Top-of-Section Switch Offset: Distance in cm from the home switch to the TOS switch. There is a utility under the DAQ > Find Top-of-Section Switch menu that will determine this value based on the current DAQ Move motion parameters (discussed in this section). ANY change in the motion profile requires that this utility be run because the final position (where the pusher bar stops) changes.
Push Past: The offset from the TOS where the pusher should stop. This value set the maximum measurement interval but MUST be several centimeters less than the distance from the TOS to the limit switch.
Fast Past: Distance the pusher will move at a higher speed before slowing down to find the TOS switch. This value MUST be several centimeters less than the distance from the TOS to the maximum section length with the pusher arm in the home position.
Run Out Switch: Switch at the end of the track that when enabled pauses the motion, preventing the section from being pushed onto the floor.

Click Motion Utility to test these settings. Click Accept to save the values or Cancel to return to the previous values.



Figure 21. Schematic of fixed positions.


Limit and Home Switches

Click Limit and Home Switches to open Limit & Home Switches window (Figure 22).



Figure 22. Limit & Home Switches window.


Select Axis: In the case of the WRMSL and STMSL it is always X.

The MDrive can be used with either a dedicated Home switch or a limit switch as a home switch. These tracks use the dedicated Home switch. Select the appropriate setup for the track in use. Use the Utilities to execute the Home command and verify the correct setting. If the home switch position of detection edge changes, verify the instrument offsets and relocate the TOS switch are still correct. Setting the edge from CW to CCW will change the offset by a least 1 cm.


Click Motion Utility to test these settings.
Click Accept to save the values or Cancel to return to the previous values.


Motion Profiles

Click Motion Profiles to open Motion Profiles window (Figure 23).  The profiles are used to set the speed and acceleration profiles used by the track.

Setting the correct values for the motion profile takes a little experimentation to make the track run efficiently and safely.



Figure 23. Motion Profile window.


DAQ Move: This profile controls moves between measurement positions. Set this to a reasonable speed with gradual acceleration so the pusher does not bump the sections.
Limit Seek: This profile finds the limit switch locations. Do not exceed 5 cm/sec and use a large deceleration value or the core could overrun the limit switch and hit the mechanical stop.
Home Final: This profile finds the final location of the home switch. Do not exceed 1 cm/sec and use a large deceleration value.
Load/Unload: This profile moves the pusher back to the load position. Set this to a reasonable but high speed with gradual acceleration and deceleration values. Setting this too slow will waste time, but keep safety in mind.
Push-Slow: This profile allows the pusher to move the new section into contact with the previous section and to locate the top of section. Use a speed a little less than the DAQ Move speed with slightly lower acceleration and deceleration values.
Push-Fast: This profile allows the pusher to move quickly to the TOS switch. Typically, it is set the same as the Load/Unload values.
User Define: This profile is used for testing only in the Motion Utilities program.


Click Motion Utility to test these settings.
Click Accept to save the values or Cancel to return to the previous values.


The following table shows the motion profile settings for the WRMSL/STMSL:


Axis→

X-Axis

Profile↓

Speed

Accel.

Decel.

DAQ Move

10.0

5.0

5.0

Limit Seek

3.0

5.0

30.0

Home Final

3.0

5.0

30.0

Load/Unload

20.0

5.0

10.0

Push-Slow

3.0

2.0

30.0

Push-Fast

10.0

5.0

30.0

User Defined

5.0

5.0

5.0

Table: Motion Profile X-Axis for WRMSL/STMSL


C.1 P-wave: Waveform Acquisition and First Arrival Detection


Signal Processing

Figure 24 helps summarize the following signal processing discussion.


Acquisition and Ensemble Averaging

Figure 24. Shipboard P-wave signal.


In Figure 24 the received waveform is 60 µsec long and digitized at 10 nsec intervals. The first 10 µsec of the waveform is replaced with zeros to remove a large spike that occurs at the beginning of the outgoing pulse. We believe that this noise is generated by the electrical "cross-talk" within the pulser-receiver. 

A Butterworth Bandpass filter is applied to the waveform to reject frequencies less than 0.4 MHz and above 1.0 MHZ. The results of this filtering is stacked, summed, and averaged (ensemble averaging). The size of the stack is pre-set by the user to a value between 10 and 100. Even with this initial filtering and ensemble averaging, the resulting signal can still contain significant noise generated by the shipboard environment. Figure 24 is typical of the signal quality.


Picking the 1st Arrival

Attempts to use a cross-correlation method (popular in seismic analysis) have not been successfully applied to IODP data. Coefficients developed for one type of lithology, fail when the lithology changes. Therefore, we depend on a threshold-crossing process to determine first arrival time. The weakness of this method is that any high-amplitude noise can cause a false, early pick.

To increase the likelihood of a correct pick, the P-wave Logger software on the WRMSL and STMSL uses a series of mathematical and data manipulation techniques to suppress the noise relative to the peak of the first arrival. Another goal is to eliminate the constant adjustment of the threshold value as the amplitude of the waveform changes due to variation in signal attenuation along the core. As the P-wave Logger is an automated system, constant supervision and adjustment is not practical.


Signal-to-Noise Ratio (SNR) Enhancement

Methods employed are partly based on Dr. Tom O'Haver's 2006 publication: A Pragmatic Introduction to Signal Processing (http://terpconnect.umd.edu/~toh/spectrum/IntroToSignalProcessing.pdf). (Figure 25).


Figure 25. Signal to Noise Enhancement.


The ensemble averaging done at the acquisition stage is effective at eliminating nearly all of the random noise. Unfortunately, our signals contain a great deal of systematic environmental noise that shielding signal cables cannot fully eliminate. To suppress this noise, we need to exploit small differences between the noise and the acoustic pulse. The parameters used in the smoothing operators were developed empirically by measuring a variety of materials and by degrading the signal by attenuation at the pulser-receiver. Time was limited on Expedition 361 to select the best smoothing operators and their parameters. Further experimentation is needed to improve the process and validate that it will work for all possible lithologies recovered by IODP.


The SNR enhancement process consists of 3 steps: (1) smoothing, (2) 1st derivative, and (3) smoothing.

  1. The first smoothing step passes the waveform through a Savitzky-Golay filter that applies a polynomial least-square fit step-wise through the data (similar to a running average). Experimentation shows that using a 6th-order polynomial across a 126 data point window will reduce high-amplitude, high-frequency noise while retaining the shape of the acoustic pulse.
  2. After the first smoothing operation, we take the 1st derivative (central-difference) which suppresses the low-frequency noise. The downside to the differentiation is that the process adds back in high-frequency noise.
  3. A second smoothing step using FIR operator is then used to reject this noise. The FIR filter coefficients were calculated using LabVIEW tools.



Waveform as absolute values

Figure 26 shows the waveform (as absolute values) before and after the 3-step process and illustrates the significant noise suppression achieved. Attempting to find the first arrival on the unprocessed data would have failed because the amplitude of the noise is greater than the first arrival peak.

Figure 26. Waveform before and after 3-step process.


Normalization

At this point in the process, a copy of the waveform is normalized to scale between the values of –1 and 1. A copy of the processed waveform is converted to its absolute value and then normalized with the waveform scaled between values of 0 and 1. This normalization is critical to making the threshold picking process indifferent to either amplification or attenuation of the signal. Experience has shown that the threshold value needs little adjustment once chosen unless there is a significant lithology change.


1st Arrival Time

The threshold crossing is performed on the absolute copy of the waveform. The crossing time is then used as the starting point to find the first zero-crossing in the derivative waveform. From this time value, we subtract 1.5 µsec to account for ¼ wavelength phase shift caused by the 1st derivative operation and ½ wavelength correction back to the first arrival. See Figure 27.

Figure 27: The upper graph shows the threshold (Horizontal cursor) crossing the first peak of the acoustic pulse and the 1st zero-crossing (vertical cursor). After correcting the time, the lower graph shows the pick on the original stacked waveform.


Waveform Data

The process described above greatly distorts the original waveform. Artificially induced time shifts are eliminated by the P-wave calibration and rolled into the system time delay value. The waveform archived in the JR_LIMS database is taken after the original signal has been band-pass filtered and ensemble averaged. The data from further processing is discarded after the 1st arrival has been determined.


V. Credits

This manual is edited from various versions and has several authors including but not limited to David Houpt, Ty Cobb, Sandra Herrmann, Beth Novak, Sherry Frazier. 

This document originated from Word document WRMSL UG v.362P2.docx (see Archived Versions below for a pdf copy) that had contributions from multiple authors including David Houpt, Ty Cobb, Sandra Herrmann, Beth Novak, Sherry Frazier, and Bill Mills. Credits for subsequent changes to this document are given in the page history.

All improvements to the Quick Start Guides and User Guides are a communal effort, with honorable mention to the group of LOs, ALOs, and technicians who have helped.

VI. LIMS Component Tables

The following tables are the component tables for the data acquired by these two instruments. They include:

  • GRA - density estimation by gamma ray attenuation
  • MS - magnetic susceptibility
  • PWAVE_L - p-wave velocity
  • (excluded) XMAN, the prototype X-ray imager, does not have LIMS components and these data are saved offline (DATA1)
ANALYSISTABLENAMEABOUT TEXT
GRASAMPLEExpExp: expedition number
GRASAMPLESiteSite: site number
GRASAMPLEHoleHole: hole number
GRASAMPLECoreCore: core number
GRASAMPLETypeType: type indicates the coring tool used to recover the core (typical types are F, H, R, X).
GRASAMPLESectSect: section number
GRASAMPLEA/WA/W: archive (A) or working (W) section half.
GRASAMPLEtext_idText_ID: automatically generated database identifier for a sample, also carried on the printed labels. This identifier is guaranteed to be unique across all samples.
GRASAMPLEsample_numberSample Number: automatically generated database identifier for a sample. This is the primary key of the SAMPLE table.
GRASAMPLElabel_idLabel identifier: automatically generated, human readable name for a sample that is printed on labels. This name is not guaranteed unique across all samples.
GRASAMPLEsample_nameSample name: short name that may be specified for a sample. You can use an advanced filter to narrow your search by this parameter.
GRASAMPLEx_sample_stateSample state: Single-character identifier always set to "W" for samples; standards can vary.
GRASAMPLEx_projectProject: similar in scope to the expedition number, the difference being that the project is the current cruise, whereas expedition could refer to material/results obtained on previous cruises
GRASAMPLEx_capt_locCaptured location: "captured location," this field is usually null and is unnecessary because any sample captured on the JR has a sample_number ending in 1, and GCR ending in 2
GRASAMPLElocationLocation: location that sample was taken; this field is usually null and is unnecessary because any sample captured on the JR has a sample_number ending in 1, and GCR ending in 2
GRASAMPLEx_sampling_toolSampling tool: sampling tool used to take the sample (e.g., syringe, spatula)
GRASAMPLEchanged_byChanged by: username of account used to make a change to a sample record
GRASAMPLEchanged_onChanged on: date/time stamp for change made to a sample record
GRASAMPLEsample_typeSample type: type of sample from a predefined list (e.g., HOLE, CORE, LIQ)
GRASAMPLEx_offsetOffset (m): top offset of sample from top of parent sample, expressed in meters.
GRASAMPLEx_offset_cmOffset (cm): top offset of sample from top of parent sample, expressed in centimeters. This is a calculated field (offset, converted to cm)
GRASAMPLEx_bottom_offset_cmBottom offset (cm): bottom offset of sample from top of parent sample, expressed in centimeters. This is a calculated field (offset + length, converted to cm)
GRASAMPLEx_diameterDiameter (cm): diameter of sample, usually applied only to CORE, SECT, SHLF, and WRND samples; however this field is null on both Exp. 390 and 393, so it is no longer populated by Sample Master
GRASAMPLEx_orig_lenOriginal length (m): field for the original length of a sample; not always (or reliably) populated
GRASAMPLEx_lengthLength (m): field for the length of a sample [as entered upon creation]
GRASAMPLEx_length_cmLength (cm): field for the length of a sample. This is a calculated field (length, converted to cm).
GRASAMPLEstatusStatus: single-character code for the current status of a sample (e.g., active, canceled)
GRASAMPLEold_statusOld status: single-character code for the previous status of a sample; used by the LIME program to restore a canceled sample
GRASAMPLEoriginal_sampleOriginal sample: field tying a sample below the CORE level to its parent HOLE sample
GRASAMPLEparent_sampleParent sample: the sample from which this sample was taken (e.g., for PWDR samples, this might be a SHLF or possibly another PWDR)
GRASAMPLEstandardStandard: T/F field to differentiate between samples (standard=F) and QAQC standards (standard=T)
GRASAMPLElogin_byLogin by: username of account used to create the sample (can be the LIMS itself [e.g., SHLFs created when a SECT is created])
GRASAMPLElogin_dateLogin date: creation date of the sample
GRASAMPLElegacyLegacy flag: T/F indicator for when a sample is from a previous expedition and is locked/uneditable on this expedition
GRATESTtest changed_onTEST changed on: date/time stamp for a change to a test record.
GRATESTtest statusTEST status: single-character code for the current status of a test (e.g., active, in process, canceled)
GRATESTtest old_statusTEST old status: single-character code for the previous status of a test; used by the LIME program to restore a canceled test
GRATESTtest test_numberTEST test number: automatically generated database identifier for a test record. This is the primary key of the TEST table.
GRATESTtest date_receivedTEST date received: date/time stamp for the creation of the test record.
GRATESTtest instrumentTEST instrument [instrument group]: field that describes the instrument group (most often this applies to loggers with multiple sensors); often obscure (e.g., user_input)
GRATESTtest analysisTEST analysis: analysis code associated with this test (foreign key to the ANALYSIS table)
GRATESTtest x_projectTEST project: similar in scope to the expedition number, the difference being that the project is the current cruise, whereas expedition could refer to material/results obtained on previous cruises
GRATESTtest sample_numberTEST sample number: the sample_number of the sample to which this test record is attached; a foreign key to the SAMPLE table
GRACALCULATEDTop depth CSF-A (m)Top depth CSF-A (m): position of observation expressed relative to the top of the hole.
GRACALCULATEDBottom depth CSF-A (m)Bottom depth CSF-A (m): position of observation expressed relative to the top of the hole.
GRARESULTconfig_asman_idRESULT config file ASMAN_ID: serial number of the ASMAN link for the configuration file
GRARESULTconfig_filenameRESULT config filename: file name of the configuration file
GRARESULTdensity_bulk_gra (g/cm³)RESULT bulk density (g/cm^3): computed bulk density of the sample
GRARESULTinstrument_groupRESULT instrument group: which core logger the GRA result came from
GRARESULTobserved_length (cm)RESULT observed length (cm): length of the section as recorded by the core logger track
GRARESULToffset (cm)RESULT offset (cm): position of the measurement expressed in cm from top of section
GRARESULTrun_asman_idRESULT run ASMAN_ID: serial number of the ASMAN link for the run (.GRA) file
GRARESULTrun_filenameRESULT run filename: file name of the run (.GRA) file
GRARESULTtimestampRESULT timestamp: actual timestamp of the measurement (as opposed to the upload time recorded by MUT)
GRARESULTtotal_counts_sec (cps)RESULT total counts per second: C-137 gamma ray counts for the measurement (roughly inversely proportional to density)
GRASAMPLEsample descriptionSAMPLE comment: contents of the SAMPLE.description field, usually shown on reports as "Sample comments"
GRATESTtest test_commentTEST comment: contents of the TEST.comment field, usually shown on reports as "Test comments"
GRARESULTresult commentsRESULT comment: contents of a result parameter with name = "comment," usually shown on reports as "Result comments"
ANALYSISTABLENAMEABOUT TEXT
MSSAMPLEExpExp: expedition number
MSSAMPLESiteSite: site number
MSSAMPLEHoleHole: hole number
MSSAMPLECoreCore: core number
MSSAMPLETypeType: type indicates the coring tool used to recover the core (typical types are F, H, R, X).
MSSAMPLESectSect: section number
MSSAMPLEA/WA/W: archive (A) or working (W) section half.
MSSAMPLEtext_idText_ID: automatically generated database identifier for a sample, also carried on the printed labels. This identifier is guaranteed to be unique across all samples.
MSSAMPLEsample_numberSample Number: automatically generated database identifier for a sample. This is the primary key of the SAMPLE table.
MSSAMPLElabel_idLabel identifier: automatically generated, human readable name for a sample that is printed on labels. This name is not guaranteed unique across all samples.
MSSAMPLEsample_nameSample name: short name that may be specified for a sample. You can use an advanced filter to narrow your search by this parameter.
MSSAMPLEx_sample_stateSample state: Single-character identifier always set to "W" for samples; standards can vary.
MSSAMPLEx_projectProject: similar in scope to the expedition number, the difference being that the project is the current cruise, whereas expedition could refer to material/results obtained on previous cruises
MSSAMPLEx_capt_locCaptured location: "captured location," this field is usually null and is unnecessary because any sample captured on the JR has a sample_number ending in 1, and GCR ending in 2
MSSAMPLElocationLocation: location that sample was taken; this field is usually null and is unnecessary because any sample captured on the JR has a sample_number ending in 1, and GCR ending in 2
MSSAMPLEx_sampling_toolSampling tool: sampling tool used to take the sample (e.g., syringe, spatula)
MSSAMPLEchanged_byChanged by: username of account used to make a change to a sample record
MSSAMPLEchanged_onChanged on: date/time stamp for change made to a sample record
MSSAMPLEsample_typeSample type: type of sample from a predefined list (e.g., HOLE, CORE, LIQ)
MSSAMPLEx_offsetOffset (m): top offset of sample from top of parent sample, expressed in meters.
MSSAMPLEx_offset_cmOffset (cm): top offset of sample from top of parent sample, expressed in centimeters. This is a calculated field (offset, converted to cm)
MSSAMPLEx_bottom_offset_cmBottom offset (cm): bottom offset of sample from top of parent sample, expressed in centimeters. This is a calculated field (offset + length, converted to cm)
MSSAMPLEx_diameterDiameter (cm): diameter of sample, usually applied only to CORE, SECT, SHLF, and WRND samples; however this field is null on both Exp. 390 and 393, so it is no longer populated by Sample Master
MSSAMPLEx_orig_lenOriginal length (m): field for the original length of a sample; not always (or reliably) populated
MSSAMPLEx_lengthLength (m): field for the length of a sample [as entered upon creation]
MSSAMPLEx_length_cmLength (cm): field for the length of a sample. This is a calculated field (length, converted to cm).
MSSAMPLEstatusStatus: single-character code for the current status of a sample (e.g., active, canceled)
MSSAMPLEold_statusOld status: single-character code for the previous status of a sample; used by the LIME program to restore a canceled sample
MSSAMPLEoriginal_sampleOriginal sample: field tying a sample below the CORE level to its parent HOLE sample
MSSAMPLEparent_sampleParent sample: the sample from which this sample was taken (e.g., for PWDR samples, this might be a SHLF or possibly another PWDR)
MSSAMPLEstandardStandard: T/F field to differentiate between samples (standard=F) and QAQC standards (standard=T)
MSSAMPLElogin_byLogin by: username of account used to create the sample (can be the LIMS itself [e.g., SHLFs created when a SECT is created])
MSSAMPLElogin_dateLogin date: creation date of the sample
MSSAMPLElegacyLegacy flag: T/F indicator for when a sample is from a previous expedition and is locked/uneditable on this expedition
MSTESTtest changed_onTEST changed on: date/time stamp for a change to a test record.
MSTESTtest statusTEST status: single-character code for the current status of a test (e.g., active, in process, canceled)
MSTESTtest old_statusTEST old status: single-character code for the previous status of a test; used by the LIME program to restore a canceled test
MSTESTtest test_numberTEST test number: automatically generated database identifier for a test record. This is the primary key of the TEST table.
MSTESTtest date_receivedTEST date received: date/time stamp for the creation of the test record.
MSTESTtest instrumentTEST instrument [instrument group]: field that describes the instrument group (most often this applies to loggers with multiple sensors); often obscure (e.g., user_input)
MSTESTtest analysisTEST analysis: analysis code associated with this test (foreign key to the ANALYSIS table)
MSTESTtest x_projectTEST project: similar in scope to the expedition number, the difference being that the project is the current cruise, whereas expedition could refer to material/results obtained on previous cruises
MSTESTtest sample_numberTEST sample number: the sample_number of the sample to which this test record is attached; a foreign key to the SAMPLE table
MSCALCULATEDDepth CSF-A (m)Depth CSF-A (m): position of observation expressed relative to the top of the hole.
MSCALCULATEDDepth CSF-B (m)Depth [other] (m): position of observation expressed relative to the top of the hole. The location is presented in a scale selected by the science party or the report user.
MSRESULTaux_file_asman_idRESULT auxiliary file ASMAN_ID: serial number of the ASMAN link for the auxiliary data file
MSRESULTaux_file_filenameRESULT auxiliary filename: file name of the auxiliary data file
MSRESULTconfig_asman_idRESULT config file ASMAN_ID: serial number of the ASMAN link for the configuration file
MSRESULTconfig_filenameRESULT config filename: file name of the configuration file
MSRESULTms_rangeRESULT MS2 meter range (Hz): setting for the MS2 meter, either 0.1 or 1.0; does not apply to measurements made with MS3 meter
MSRESULTms_unitsRESULT MS units: setting for the magnetic suscepitibility units, either SI or cgs
MSRESULTms_correctionRESULT MS2C correction factor: MS2C correction factor for frequency-adjusted loops; this value is 1.000 for normal-frequency (565 Hz) loops and 1.174 for 20%-low-adjusted frequency (452 Hz) loops
MSRESULTmagnetic_susceptibilityRESULT magnetic susceptibility (instrument units): magnetic susceptibility of the sample, not volume corrected.
MSRESULTobserved_length (cm)RESULT observed length (cm): length of the section as determined by the core logger track; recorded only once per TEST
MSRESULToffset (cm)RESULT offset (cm): position of the observation made, measured relative to the top of a section or section half.
MSRESULTrun_asman_idRESULT run file ASMAN_ID: serial number of the ASMAN link for the run (.MS) file
MSRESULTrun_filenameRESULT run filename: file name for the run (.MS) file
MSRESULTtimestampRESULT timestamp: date/time stamp of each individual measurement
MSSAMPLEsample descriptionSAMPLE comment: contents of the SAMPLE.description field, usually shown on reports as "Sample comments"
MSTESTtest test_commentTEST comment: contents of the TEST.comment field, usually shown on reports as "Test comments"
MSRESULTresult commentsRESULT comment: contents of a result parameter with name = "comment," usually shown on reports as "Result comments"
ANALYSISTABLENAMEABOUT TEXT
PWAVE_LSAMPLEExpExp: expedition number
PWAVE_LSAMPLESiteSite: site number
PWAVE_LSAMPLEHoleHole: hole number
PWAVE_LSAMPLECoreCore: core number
PWAVE_LSAMPLETypeType: type indicates the coring tool used to recover the core (typical types are F, H, R, X).
PWAVE_LSAMPLESectSect: section number
PWAVE_LSAMPLEA/WA/W: archive (A) or working (W) section half.
PWAVE_LSAMPLEtext_idText_ID: automatically generated database identifier for a sample, also carried on the printed labels. This identifier is guaranteed to be unique across all samples.
PWAVE_LSAMPLEsample_numberSample Number: automatically generated database identifier for a sample. This is the primary key of the SAMPLE table.
PWAVE_LSAMPLElabel_idLabel identifier: automatically generated, human readable name for a sample that is printed on labels. This name is not guaranteed unique across all samples.
PWAVE_LSAMPLEsample_nameSample name: short name that may be specified for a sample. You can use an advanced filter to narrow your search by this parameter.
PWAVE_LSAMPLEx_sample_stateSample state: Single-character identifier always set to "W" for samples; standards can vary.
PWAVE_LSAMPLEx_projectProject: similar in scope to the expedition number, the difference being that the project is the current cruise, whereas expedition could refer to material/results obtained on previous cruises
PWAVE_LSAMPLEx_capt_locCaptured location: "captured location," this field is usually null and is unnecessary because any sample captured on the JR has a sample_number ending in 1, and GCR ending in 2
PWAVE_LSAMPLElocationLocation: location that sample was taken; this field is usually null and is unnecessary because any sample captured on the JR has a sample_number ending in 1, and GCR ending in 2
PWAVE_LSAMPLEx_sampling_toolSampling tool: sampling tool used to take the sample (e.g., syringe, spatula)
PWAVE_LSAMPLEchanged_byChanged by: username of account used to make a change to a sample record
PWAVE_LSAMPLEchanged_onChanged on: date/time stamp for change made to a sample record
PWAVE_LSAMPLEsample_typeSample type: type of sample from a predefined list (e.g., HOLE, CORE, LIQ)
PWAVE_LSAMPLEx_offsetOffset (m): top offset of sample from top of parent sample, expressed in meters.
PWAVE_LSAMPLEx_offset_cmOffset (cm): top offset of sample from top of parent sample, expressed in centimeters. This is a calculated field (offset, converted to cm)
PWAVE_LSAMPLEx_bottom_offset_cmBottom offset (cm): bottom offset of sample from top of parent sample, expressed in centimeters. This is a calculated field (offset + length, converted to cm)
PWAVE_LSAMPLEx_diameterDiameter (cm): diameter of sample, usually applied only to CORE, SECT, SHLF, and WRND samples; however this field is null on both Exp. 390 and 393, so it is no longer populated by Sample Master
PWAVE_LSAMPLEx_orig_lenOriginal length (m): field for the original length of a sample; not always (or reliably) populated
PWAVE_LSAMPLEx_lengthLength (m): field for the length of a sample [as entered upon creation]
PWAVE_LSAMPLEx_length_cmLength (cm): field for the length of a sample. This is a calculated field (length, converted to cm).
PWAVE_LSAMPLEstatusStatus: single-character code for the current status of a sample (e.g., active, canceled)
PWAVE_LSAMPLEold_statusOld status: single-character code for the previous status of a sample; used by the LIME program to restore a canceled sample
PWAVE_LSAMPLEoriginal_sampleOriginal sample: field tying a sample below the CORE level to its parent HOLE sample
PWAVE_LSAMPLEparent_sampleParent sample: the sample from which this sample was taken (e.g., for PWDR samples, this might be a SHLF or possibly another PWDR)
PWAVE_LSAMPLEstandardStandard: T/F field to differentiate between samples (standard=F) and QAQC standards (standard=T)
PWAVE_LSAMPLElogin_byLogin by: username of account used to create the sample (can be the LIMS itself [e.g., SHLFs created when a SECT is created])
PWAVE_LSAMPLElogin_dateLogin date: creation date of the sample
PWAVE_LSAMPLElegacyLegacy flag: T/F indicator for when a sample is from a previous expedition and is locked/uneditable on this expedition
PWAVE_LTESTtest changed_onTEST changed on: date/time stamp for a change to a test record.
PWAVE_LTESTtest statusTEST status: single-character code for the current status of a test (e.g., active, in process, canceled)
PWAVE_LTESTtest old_statusTEST old status: single-character code for the previous status of a test; used by the LIME program to restore a canceled test
PWAVE_LTESTtest test_numberTEST test number: automatically generated database identifier for a test record. This is the primary key of the TEST table.
PWAVE_LTESTtest date_receivedTEST date received: date/time stamp for the creation of the test record.
PWAVE_LTESTtest instrumentTEST instrument [instrument group]: field that describes the instrument group (most often this applies to loggers with multiple sensors); often obscure (e.g., user_input)
PWAVE_LTESTtest analysisTEST analysis: analysis code associated with this test (foreign key to the ANALYSIS table)
PWAVE_LTESTtest x_projectTEST project: similar in scope to the expedition number, the difference being that the project is the current cruise, whereas expedition could refer to material/results obtained on previous cruises
PWAVE_LTESTtest sample_numberTEST sample number: the sample_number of the sample to which this test record is attached; a foreign key to the SAMPLE table
PWAVE_LCALCULATEDDepth CSF-A (m)Depth CSF-A (m): position of observation expressed relative to the top of the hole.
PWAVE_LCALCULATEDDepth CSF-B (m)Depth [other] (m): position of observation expressed relative to the top of the hole. The location is presented in a scale selected by the science party or the report user.
PWAVE_LRESULTconfig_asman_idRESULT config file ASMAN_ID: serial number of the ASMAN link for the configuration file
PWAVE_LRESULTconfig_filenameRESULT config filename: file name of the configuration file
PWAVE_LRESULTdistance_in_caliper (mm)RESULT distance in caliper (mm): distance between transducers
PWAVE_LRESULTobserved_length (cm)RESULT observed length (cm): length of the section as recorded by the core logger track
PWAVE_LRESULToffset (cm)RESULT offset (cm): position of the observation made, measured relative to the top of a section half.
PWAVE_LRESULTrun_asman_idRESULT run file ASMAN_ID: serial number of the ASMAN link for the run (.PWAVE_L) file
PWAVE_LRESULTrun_filenameRESULT run filename: file name of the run (.PWAVE_L) file
PWAVE_LRESULTvelocity_wfm_asman_idRESULT velocity waveform signal file ASMAN_ID: serial number of the ASMAN link for the velocity waveform (.CSV) file
PWAVE_LRESULTvelocity_wfm_filenameRESULT velocity waveform signal filename: file name for the velocity waveform (.CSV) file
PWAVE_LRESULTtimestampRESULT timestamp: date/time stamp for the actual measurement time
PWAVE_LRESULTtravel_time (µs)RESULT travel time (us): traveltime of the sonic wave from transducer to transducer through the sample, associated with the velocity observation in the specified axis. (Calculated by software)
PWAVE_LRESULTvelocity_xy (m/s)RESULT sonic velocity XY-plane (m/s): velocity of pressure wave through sample through the XY plane, calculated by the software
PWAVE_LSAMPLEsample descriptionSAMPLE comment: contents of the SAMPLE.description field, usually shown on reports as "Sample comments"
PWAVE_LTESTtest test_commentTEST comment: contents of the TEST.comment field, usually shown on reports as "Test comments"
PWAVE_LRESULTresult commentsRESULT comment: contents of a result parameter with name = "comment," usually shown on reports as "Result comments"


VII. Archived Versions

  • No labels