PP-LWT MEETING MINUTES 21 NOVEMBER 2000 Attending: Blum, Fackler, Freeman, Ledwon, Mills, Prince AGENDA 1. Reports * Legs 189-192 Cruise Evaluations * Legs 190-192 Tech Reports 2. Major Issues * Voltage setting for NGR system * NGR data transfer * P-wave velocity upgrades and tasks * New PWS calibration procedure * Bar codes * Direct Upload and Systems-DB Links 3. Action Overview * Tasks completed * Old tasks not completed * New tasks Appendix I: PP application task list, 21 November 2000 1. REPORTS 1.1. LEGS 189-192 CRUISE EVALUATIONS (FROM SCIENTISTS) During Leg 190, the problem of having the ovens under the auxiliary sampling table was noted again. Unfortunately we have no other suitable space in the vicinity of the MAD station for the ovens. The general space problem (for core handling) was also commented on. The slow performance of the MST in the early part of the leg caused frustrations and is further addressed below. The generally slow operation of the pycnometer was noted - a situation we have to put up with because no alternative equipment exists on the market. Having multiple pycnometers operational simultaneously would present serious space and maintenance challenges and would require some software development. During Leg 191, Rick Carlson (Texas A&M university), was very happy with the lab. He experimented with alternative P-wave velocity calibrations and presented the results to the group after the cruise. His suggestions are being implemented along with our hardware upgrades to both the PWL and PWS3 systems (see items below). Carlson also suggested that a permeameter would be very useful on the ship. We concur, however, the grim budget situation and the crammed lab space prevent us from launching such an initiative at the end of this phase of the program. On Leg 192, the PWS computer seemed to have frozen up repeatedly. Scientists were affected by PWS data upload problems that resulted from new equipment installed on Leg 191 (see below). 1.2. LEGS 190-192 TECH REPORTS The MST became sluggish at times and had to be rebooted. The belt snapped several times during 192, close enough to the boat so that it could be re-attached by slackening the belt. If this continues, a new belt may be needed. At one time, repeated error messages were tracked back to the malfunction in the emergency stop button switch, which wasn't obvious from the button itself. The most serious problem with the MST during this period was that the coreboat would periodically off-center and the home position had to be re-zeroed. Some cores were measured with the offset and the core length/position data had to be edited in the database. A time stamp problem also had to be fixed in the database because it caused errors with calibration data links. This seems to be the result of Labview data formatting in the MST program, which is regularly upset by local time changes into the past. At the beginning of Leg 190 NGR data acquisition was extremely slow. Extensive analysis of the power supply and gain settings (see 2.1.) revealed that the power had been set too high. On Leg 191, new PCI boards were installed to accelerate NGR data transfer (see task below). Some problems were not resolved, however, and the desired effect was not yet achieved (see 2.2). Editing capabilities for NGR data seem to be broken as a result of the latest upgrades in NGR data handling. Needs to be fixed otherwise the shore personnel has to be tasked with clean up (see new task). Problems were experienced on 190 with the PWL calibration (shaky hardware) and with the PWS3 separation measurements. Both problems were addressed on Leg 191, when the PWL and PWS transducer separation measurement devices were upgraded (see 2.3 and new task). The new equipment resulted in some data upload problems on 191 and 192, though, because the calibration data (and procedures) are affected by this upgrade (see 2.4). The new pycnometer arrived on the ship during Leg 190. Fackler had to make adjustments to the MAD program for the fact that the keypad and communications differed from the older models. A new data field now identifies which pycnometer is being used. It was discovered on Leg 191 that running individual cells causes errors with the new pycnometer. Otherwise, the new pycnometer seemed to work extremely well. MAD data upload seemed to work better with the integrated upload utility in the new MAD program version brought on Leg 192 than with the Generic Uploader. A procedure was implemented to format TC data in a spreadsheet and upload them into the database (final values only). A database editing capability (similar to MST and PWS) is now needed to manage TC data after the upload (see new task). The Generic Uploader was received very well by the ODP staff. 2. MAJOR ISSUES 2.1. VOLTAGE SETTING FOR NGR SYSTEM During Leg 190, ODP technical staff under the coordination of Matt O'Regan analyzed the issues determining the optimal voltage setting for the NGR. This problem had been unresolved for years and the latest, concerted effort brought closure to the question. Matt completed a report, which will be posted on the WWW once we receive an electronic copy. The report concludes that the NGR should be run with 0.62 kV applied to the scintillation detectors (actually, it should read 0.65 kV) and 10 mV set for the Low Level Detect (LLD) on the multi-channel buffer. 2.2. NGR DATA TRANSFER Mills installed the new PCI boards that should dramatically accelerate NGR data transfer and eliminate the significant lost time during MST logging. This has been a high-priority upgrade for a long time. Unfortunately, something does not seem to work yet and Mills is to consult with ORTEC in November. Hopefully this can be fixed at the beginning of Leg 194. 2.3. P-WAVE VELOCITY UPGRADES AND TASKS The PWL transducer separation measurement LVDT device was upgraded on Leg 191 to a more robust system. This eliminated the calibration problems due to shaky hardware. The new LVDT returns a voltage to be calibrated to distance, and not the 1-255 integer value the old system returned. At the same time, the transducer separation scale on the PWS3 was replaced with a LVDT system. The hardware upgrades require a number of adjustments to the calibration data handling at all levels. They also provide an opportunity to make P-wave data formats uniform and compatible for all four systems (PWL, PWS1,2,3). The PWL and PWS3 files, formats, and data models should be identical after these adjustments. (See new task 'P-Wave Fixes'.) The new PWS3 device is still measuring the absolute distance between the upper transducer and the fixed frame, which is prone to errors because the lower transducer is not perfectly fixed. The LVDT device needs to be mounted such that it measures the relative displacement between the transducers, analogous to the PWL system. This should happen on Leg 194. It was also decided that a future pressure transducer for the PWS3, used to monitor constant pressure on the samples, should be mounted on top of the top transducer (not at the bottom, as in the past configuration). The tasks 'PWL CALIBRATION DATA' was completed from the reporting side but not from the MST file format side (number of reported digits). The task is superceded by 'P-Wave Fixes' and eliminated from the list. 2.4. NEW PWS CALIBRATION PROCEDURE In the past, transducer separation and time (electronic/transducer delay) were calibrated in one step, using solid (lucite) standards. Based on suggestions from Rick Carlson, the calibration is now being performed with water bags instead of solid displacement standards. Anastasia and Bill confirmed the practicality of this procedure. This means that the LVDT must be calibrated first, and the time delay must be calibrated subsequently and separately using the calibrated LVDT data. The additional work should be offset by better accuracy. Up to now, the liner correction was applied based on a constant liner thickness and a constant sound velocity in the core liner determined once in the past. The accuracy of that correction was not quite satisfactory because of the difficulties of measuring the transit time through a thin, bent plastic layer, and because of the potential variability in the liner properties. The new procedure will allow the determination of transit time through the liner more accurately, using regression of multiple measurements of water bags placed in the liner, and the PWS3 calibration performed without liner. The velocity in water determined with the PWS3 can be used directly for the calibration of PWS1 and PWS2. In the past, the velocity in water was looked up in tables based on temperature measurements. In the future, the calibrated water from PWS3 calibration can be poured into the tray for PWS1/2 calibration, and the velocity value typed in for the program to use. 2.5. BAR CODES No major progress has been made with the implementation of bar codes for the MST, which is partly due to higher priority projects in both the Science and Information Services departments. Technical problems also play a role: Fackler performed tests on the ship and found problems with muddy labels and wrinkled tapes that have yet to be overcome. More discussion and tests are likely to take place during Leg 194 (both Fackler and Mills sail). 2.6. DIRECT UPLOAD AND SYSTEMS-DB LINKS The status of the 'Direct Upload', which one day should replace the need to invoke data upload manually for each measurement system, was discussed. All attendees agreed that this is still the favorite concept but that it is not of top priority/urgency for the following reasons. 1. ODP staff is very satisfied with the 'Generic Uploader" presently used to invoke data upload. 2. The Generic Uploader is also very useful for data migration because it can be adjusted easily for different data formats and structures. 3. With direct uplaod comes also the need for good database editing utilities for all data. A prerequisite for direct upload, and a much more urgent issue in terms of data integrity, is to ensure that measurement systems can retrieve calibration and standard data directly from the database. Measurement systems and database had been set up to do this from the beginning, but the actual links were never established. This results in a number of problems, including the need to re-create calibration and background data files when in fact the relevant data already reside in the database, and occasional date stamp confusions. The group has been talking about this for quite some time and we therefore define the new task 'System-DB links'. The task 'Replace JANUS.MST with Direct Upload' is eliminated from the list, first because JANUS.MST was replaced with the much improved 'Generic Uploader', and second because we define the scaled-back task 'System-DB links'. 3. ACTION OVERVIEW 3.1. TASKS COMPLETED Application development tasks € Upgrade PWS - superceded by 'P-Wave Fixes' € Upgrade "Strength" - runs on PC now € Converted PWS and AVS to the PC platform Other tasks € Upgraded PWL displacement measurement. € Upgraded PWS displacement measurement. € Upgraded PWL signal source. € Purchased and installed a new (third) pycnometer. € Purchased spare MST core boats. € Purchased PCI Maestro boards for NGR (and GRA) data transfer. € Clarified with SCIMP that AVS is NOT coming off the track. 3.2. OLD TASKS NOT COMPLETED Application development tasks € NGR (and GRA) data transfer (partly done) [Mills]. € MAD control measurements [ISD/Blum]. € TC user interface [Becker/Blum]. € TC data model [Mithal/Blum]. € Implement bar codes [ISD/Mills]. € WCMST threshold warnings [ISD/Mills]. € MSL drift correction (partly addressed) [Mills/Blum]. € WCMST control data [ISD/Mills/Blum]. € Implement PWS4 system [Mills/Ledwon/ISD]. € Simultaneous MSP (MSCL or AMST) [Mills]. Other tasks € DB group to present their color calculations for comparison with CM2002 calculations for Leg 189 [Clark/Blum] € Fix MAD report [ISD/Blum]. € Investigate MST core boat positioning problem and belt failures [Mills] 3.3. NEW TASKS (see descriptions in Appendix I) Application development tasks € TC database editor [ISD]. € NGR database editor [ISD]. € P-wave fixes [Mills, ISD]. € System-DB links [Mills/ISD]. € MSL background correction [Mills/Blum/ISD]. APPENDIX I: PP APPLICATION TASK LIST, 21 NOVEMBER, 2000 REFERENCE: NGR DATA TRANSFER CONTACT: PP-LWT DATE: 9/21/99; modified 11/20/00 DATA SYSTEM: WCMST-NGR OBJECTIVE: Increase speed (and therefore quality) of natural gamma ray data acquisition. RATIONALE: NGR data acquisition slows down core logging substantially (~200% overhead time) because writing the data to the local disk takes more time than measuring it and writing it to the multi-channel buffer. TASK(S): At least double present rate (or sampling resolution) of NGR (and overall WCMST) data acquisition by upgrading NGR data transfer to present technology. This can be accomplished with the recent change of the WCMST control software to the PC platform (drydock), and the new PCI board installed on Leg 191. A persisting problem should be resolved on Leg 194. RESOURCES: Estimated 8 hr of software configuration. REFERENCE: FIX MAD REPORT CONTACT: PP-LWT DATE: 4/18/00 DATA SYSTEM: MAD OBJECTIVE: Provide accurate and user-friendly data report. RATIONALE: A recent review and discussion with the database group revealed that several format/labeling problems exist in the present MAD report. While accomplishing the minor changes to fix this, some additional modification could be done to enhance the logic and user's grasp of the different methods A, B, and C. TASK(S): Prepare a report according to the example (Excel table) provided by Blum. Re-arrange/eliminate some columns. Use one decimal precision for all % values (water content, porosity) and three decimals for all mass (g), density (g/cm^3), and void ratio values. Fix column headers according to example. RESOURCES: Estimated 10 hr of query writing. REFERENCE: MAD CONTROL MEASUREMENTS CONTACT: PP-LWT DATE: 9/21/99; modified 12/3/99 DATA SYSTEM: MAD OBJECTIVE: Save and make available MAD control (precision) data. RATIONALE: Volume control measurements (using calibration sphere) are routinely acquired with the pycnometer to check on the instrument's performance. These measurements have been used for a quick, real-time verification that the value did not deviate more than a certain empirical amount from the true value. A few years ago, the major pieces (new control program, data model) were put in place to keep a record of these control measurements that would not only allow a quantitative evaluation of the analytical error, but also correction or elimination of data affected by a malfunctioning cell. Today, these data are still not loaded and no web report exists. TASK(S): Load MAD control measurements into database and make them accessible through a web report. RESOURCES: Estimated 24 hr of programming. REFERENCE: WCMST THRESHOLD WARNINGS CONTACT: PP-LWT DATE: 9/21/99; modified 12/3/99 DATA SYSTEM: WCMST-ALL SENSORS OBJECTIVE: Avoid collection of bad data, or loss of data, through real-time warnings. RATIONALE: Instrument problems (electronic failures, calibration problems, etc.) occur on almost every leg. Because WCMST data acquisition is automated and rapid, associated bad data collection is often discovered only days later and entire holes' worth of data may be lost. The original specifications for the new MST software in 1996 included a warning system based on control measurements taken with every section (partly implemented) but the project was never completed. In addition, threshold warnings should also be possible based on the core measurement values. TASK(S): Implement threshold warnings for the WCMST. Add an interface where the operator can enter high and low threshold values for each sensor, for the routine control measurement (default values) as well as for the core measurements (core- specific values), and make alarms go off if the acceptable values are not met. This would drastically reduce the risk of collection bad data by allowing the operators to discover instrument problems immediately. RESOURCES: Estimated 80 hr of Labview programming REFERENCE: MSL DRIFT CORRECTION CONTACT: PP-LWT DATE: 9/21/99; modified 12/3/99 DATA SYSTEM: WCMST-MSL OBJECTIVE: Improve accuracy of magnetic susceptibility drift correction. RATIONALE: The present implementation of the magnetic susceptibility drift correction is rather ineffective because of slack in timing and positioning of the reference measurement. TASK(S): The reference measurement for drift calculation should be taken as soon as possible after the core measurements, i.e., at the end of the last MS measurement rather than at the end of the section run (last NGR measurement) as presently implemented. Furthermore, the reference measurement should be taken at the same position as the zeroing took place. The MST run should therefore be interrupted at the end of the MS run, the boat moved into the zeroing position, and the reference measurement taken, before the section run is resumed. Ideally, zeroing and reference measurements are taken at the center of a 50-cm long "Control 2" standard, a liner filled with pure water and mounted at the top of the core boat. RESOURCES: Estimated 40 hr of Labview programming; fix to hardware configuration REFERENCE: WCMST CONTROL DATA CONTACT: PP-LWT DATE: 9/21/99; modified 12/3/99 DATA SYSTEM: WCMST-ALL SENSORS OBJECTIVE: Make MST control (precision) data consistently available. RATIONALE: Control measurements are used to evaluate and monitor instrument performance, calibrate or correct core measurements, or take test measurement independent of the core sample identification requirement. Control-1 measurements are performed on standards that are run like a core, in a separate run; they may be part of the ODP set of standards or any type of material or standard provided by the user. Control-2 measurements are routinely performed at the beginning of each section run, on a water standard that is mounted at the top of the core boat. Control-3 measurements are routinely performed "through air", at the end of a section run. Implementation of control measurements is at various stages, most problems appear to be related to the web reports and should be easy to fix. TASK(S): Complete implementation of the following control measurements, uploads, and web reports: GRA: Ctrl-1, Ctrl-2, Ctrl-3 MSL: Ctrl-1, (hold), Ctrl-3 NGR: Ctrl-1, (hold), Ctrl-3 PWS: Ctrl-1, Ctrl-2, N/A Specific tasks: 1. Check all Control web report header names and units, there are mistakes". 2. Change names of web reports from "Control" to "Control-1. 3. Create headers on the web report selection page ("Control-1", "Control-2", "Control-3") that are linked to a brief explanatory text about control measurements. 4. When NGR background measurements are taken on the long water core, write the data to the control-1 tables as well so they are available to the user. 5. The Control-2 water standard is too short for the NGR and MSL sensors; don't acquire these data until modifications to the WCMST allow implementation of a longer (50 cm) water standard on the core boat. 6. Control-3 values for GRA appear to be hard-coded or copied for each section rather than measured; the web report does not return any values. 7. For PWL, the Control-3 web report lists values although control-3 measurements are actually not possible with this sensor. RESOURCES: Estimated 200 hr of programming. REFERENCE: IMPLEMENT PWS4 CONTACT: PP-LWT DATE: 9/21/99; modified 12/3/99 DATA SYSTEM: "PWS" OBJECTIVE: Separate instrument for P-wave velocity measurements on cylinders/cubes for better data. RATIONALE: At present, the P-wave velocity sensor 3 (PWS3) is used for measurement on both half-cores and discrete rock cubes or cylinders. The requirement of sensor spring loading for the former has resulted in a lot of bad data for the latter type of measurement because measurement conditions were different from calibration conditions. TASK(S): For this and other operational reasons, implement a separate PWS4 system. It would mostly be a stand-alone copy of the present PWS3 system. Once the hardware and controlling software (Labview) are completed, database model, upload, and data report can be completed almost identical to the PWS3 system. RESOURCES: Estimated 120 hr of Labview programming and testing. REFERENCE: TC USER INTERFACE CONTACT: PP-LWT DATE: 9/21/99; modified 12/3/99 DATA SYSTEM: TC OBJECTIVE: Ensure consistent thermal conductivity data collection. RATIONALE: The present TC program (instrument control) is the generic version written by the manufacturer (Teka, Berlin). It works very well, but it does not include an ODP sample identification interface or data upload protocol. The instrument output files are not consistently returned to ODP from the ship. Instead, spreadsheets prepared by scientists ad-hoc are the product of this system. This is one of the last standard data acquisition systems not integrated at all into the ODP routine and database. TASK(S): Write an ODP-specific user interface with consistent sample identification protocol (use of bar codes is preferred). Add data upload and backup on "Save", and database-editing functions (delete bad run, rename section and interval. Detailed specifications are available from P. Blum. RESOURCES: Estimated 24 hr of ODP programming; $4k for software; $7k for programming. REFERENCE: TC DATA MODEL CONTACT: PP-LWT DATE: 9/21/99; modified 12/3/99 DATA SYSTEM: TC OBJECTIVE: Ensure consistent thermal conductivity data archiving and access. RATIONALE: The present database model only accommodates the final, interpreted TC values. The values are uploaded on shore from inconsistent spreadsheet files prepared by scientists ad-hoc. This implementation is a quick fix and not compatible with the more rigorous data archiving and quality standards for other physical properties measurement systems. TASK(S): Develop new database model that accommodates all measurement parameters and raw data (time-temperature series) that are output by the Teka instrument. Draft specifications are available from P. Blum. RESOURCES: Estimated 40 hr of programming REFERENCE: SIMULTANEOUS MSP CONTACT: PP-LWT DATE: 9/21/99; modified 12/3/99 DATA SYSTEM: AMST-MSP OBJECTIVE: Allow simultaneous acquisition of color reflectance and point-sensor magnetic susceptibility. RATIONALE: At present, the magnetic susceptibility point sensor (MSP) measurements are not feasible on a high recovery leg. The first problem is related to the instruments integration time and is out of our control. The second problem is that MSP measurements require a dedicated run on the AMST. TASK(S): Implement MSP measurements such that they can be taken simultaneously with the color reflectance measurements, slowing the latter down slightly but allowing to take both measurements on moderate-high recovery legs (hardware component!) Integrate data upload and edit functions similarly as for the CR data and as part of the AMST upload and edit component. RESOURCES: Estimated 200 hr of Labview programming and testing. REFERENCE: MSP DATA MODEL CONTACT: PP-LWT DATE: 9/21/99; modified 12/3/99 DATA SYSTEM: AMST-MSP OBJECTIVE: Ensure consistent archiving/access of magnetic susceptibility point-sensor data. RATIONALE: The magnetic susceptibility point sensor (MSP) system is in development. Data acquisition must yet be completed. TASK(S): At this time, create the data model for MSP data so they can be loaded. RESOURCES: Estimated 80 hr of programming. REFERENCE: IMPLEMENT BARCODES CONTACT: PP-LWT DATE: 9/21/99; modified 12/3/99 DATA SYSTEM: ALL PP SYSTEMS IN A FIRST PHASE OBJECTIVE: Avoid operator errors and save time by eliminating typing of section/sample id's. RATIONALE: Shipboard personnel are eager to use barcodes for core section and sample identification. The foundation has been laid a long time ago, and most pieces seem to be in place. However, implementation got stuck somewhere since barcodes cannot be used for any PP station at this time. TASK(S): Complete implementation of the use of barcodes for all PP stations, starting with the WCMST. RESOURCES: Estimated 120 hr of installation and programming. REFERENCE: SYSTEM-DB LINKS CONTACT: PP-LWT DATE: 11/21/00 DATA SYSTEM: ALL PP SYSTEMS, STARTING WITH WC-MST OBJECTIVE: Allow direct retrieval of calibration, standard, and background data from the database as part of a calibration/measurement run. This is a prerequisite for a future 'Direct Upload" project. RATIONALE: The PP measurement systems and database models were designed in such a way that calibration, background, and standard data could be re-used and did not have to be recreated each time. This requires consistent uplaod and time stamping of the relevant values, and their direct retrieval from the database when needed. This link has not been established to date, which results in the need to re-create calibration and background files and causes time stamp mis- matches. TASK(S): Establish direct system-database link. RESOURCES: Estimated 200 hr of programming. REFERENCE: MSL BACKGROUND CORRECTION CONTACT: PP-LWT DATE: 11/21/00 DATA SYSTEM: WCMST-MSL OBJECTIVE: Measure and subtract background (coreboat, dirt) from magnetic susceptibility measurements. RATIONALE: The coreboat carries a magnetic susceptibility signal of a few instrument units. Mud accumulating on the boat can add another few units. This becomes significant in core materials with very low susceptibilities (almost pure carbonate/siliceous oozes). The magnitude of the effect is in the same range as the instrument drift on our MSL system. The background could be removed relatively easily by periodically measuring an empty boat run and then subtracting the values from the core measurements. TASK(S): 1. Implement a background measurement routine in the MST program. 2. Create a table in the data model to hold the data, with a time stamp, and the necessary upload component. 3. Upgrade the data report to subtract the interpolated or selected background values from the core data and display the background values in the first (uncorrected) data column. (The second, corrected data column is to hold the drift- corrected data). Add a column in the report that gives the magnitude of the background correction (placed in front of the column that shows the drift correction). RESOURCES: Estimated 100 hr of programming. REFERENCE: NGR DATABASE EDITOR CONTACT: PP-LWT DATE: 11/20/00 DATA SYSTEM: WC-MST NGR OBJECTIVE: Fix database editor. RATIONALE: Editing capabilities for NGR data seem to be broken as a result of the latest upgrades in NGR data handling. This needs to be fixed otherwise the shore personnel has to be tasked with data clean up. TASK(S): Fix the database editor for NGR data. RESOURCES: Estimated 20 hr of programming. REFERENCE: TC DATABASE EDITOR CONTACT: PP-LWT DATE: 11/20/00 DATA SYSTEM: TC OBJECTIVE: Provide database editing capability for thermal conductivity data. RATIONALE: A data model exists to hold thermal conductivity data. Note that this table only holds the computed final values, and no parameters or raw data (see 'TC Data Model' task for a description of the ultimate data model). ODP personnel has to format the data coming from the Teka04 instrument manually in a spreadsheet and then invoke the upload. This is cumbersome but it works. However, errors in the uploaded data cannot easily be edited because no editor exists. TASK(S): Create a database editor for TC data similar to the MST and PWS database editor. RESOURCES: Estimated 20 hr of programming. REFERENCE: P-WAVE FIXES CONTACT: PP-LWT DATE: 11/20/00 DATA SYSTEM: WC-MST PWL and PWS OBJECTIVE: Adjust data files and data handling to recently installed hardware upgrades; make all P-wave data formats consistent. RATIONALE: The Leg 191 upgrades to transducer displacement measurement systems of the PWL and PWS3 systems require a follow up to make data structure, data formats, database tables, and data upload routines compatible. TASK(S): 1. Create MST data file fields to accommodate new LVDT calibration, eliminate a few fields that were never used (PWL, PWS3); 2. Make all data formats (time and distance) uniform and compatible among all P-wave systems (PWL, PWS); 3. Adjust database tables accordingly; 4. Adjust data uploaders and data reports accordingly. RESOURCES: Estimated 100 hr of programming.