PP-LWT MEETING MINUTES
18 APRIL 2000

Attending: Blum, Fackler, Freeman, Mills, Moortgat, 
Prince

AGENDA

1. Reports
     * Leg 188 cruise evaluations
     * Leg 188 Tech Report
     * Leg 189 Preliminary Tech Report
2. Other issues
     * Transit
     * Color reflectance
     * Bar codes
     * MSCL (Geotek)
     * Transfer of application custodianship
3. Action items
     * Tasks completed
     * Old tasks not completed
     * New tasks

Appendix I: PP application task list, 18 April 2000


1. REPORTS

1.1. LEG 188 CRUISE EVALUATIONS

PP scientists commented on three well-known problems 
that should be fixed ASAP: 1. Pycnometer did not perform 
well because of electronics problems and sea state 
sensitivity (see tech reports); 2. Problems with PWS 
user interface, particularly data saving (see "Upgrade 
PWS" on application task list); 3. MAD data upload was 
not functioning (see tech reports). In addition, one 
person suggested a lack of sufficient computers in the 
core lab which led PP scientists to occupy core 
description stations.

1.2. LEG 188 TECH REPORT

Almost the entire PP lab was reassembled, reconnected, 
and/or rebuilt during the first part of the leg. 

The WCMST was relocated to the center of the core lab 
for better access. New belt retainers were installed to 
allow the core to be returned to the loading point 
without slipping on the timed drive gear. The control 
program was converted to the PC (Pentium III) platform.

The MS drift measurement can now be made at the same 
point where zeroing occurred. [Better timing of drift 
measurement is not resolved yet.) Communication was 
changed from GPIB to the serial port for the MS.

Part of the PWL data acquisition box from Geotek was 
replaced with a National Instruments oscilloscope board 
for acquisition of acoustic signal and displacement 
data. The new signal source has not been completed yet 
and the Geotek box is still used for that purpose. 
[Also, a new PWL sensor displacement system is in 
development 
(hard-coded opening mechanism instead of optical sensor) 
to provide more accurate and robust displacement 
measurements.]

NGR data transfer is not up to speed yet (see "NGR Data 
Transfer" on application task list). It was discovered 
that new PCI Maestro boards must be purchased to change 
NGR (and GRA) data transfer from the slow serial to the 
faster DMA bus.

Serious problems with the pycnometer at the first site 
were apparently fixed for the remainder of the leg: (1) 
Drierite was changed to a coarser material, (2) The gas 
bottle was moved closer to the pycnometer, and (3) the 
gas regulator was replaced. The second pycnometer was 
also installed and tested but had a different set of 
problems and was put away again.

The Macintosh version of the MAD program was used 
because tests with the PC version showed problems at the 
beginning of the leg. Once the problems were ironed out 
and tests were positive at the end of the leg it was 
decided to use the PC version on Leg 189. The upload 
function did not work yet, however, and the data had to 
be uploaded offline with the generic upload routine.

The PWS3 measurements showed apparent errors related to 
data saving problems and some other factor [displacement 
measurement? Is frequency exactly 500 kHz?] [see 
"Upgrade PWS" on application task list].

The AVS failed during mid-leg. The ETs diagnosed the 
problem in the relay that drives the motor, patched a 
quick fix, and ordered new parts.

1.3. LEG 189 PRELIMINARY TECH REPORT

Summary of relevant issues received from Anastasia 
during the last few days.

The MST boat snapped at one end and had to be replaced. 
New boats must be ordered. Track seems to be somewhat 
too fast now, causing positioning errors, hang-ups, and 
dumping of cores. Lost some PWL data when sprinkler pump 
had to be replaced. Generic upload routines for PWL, 
GRA, and MS work well. Scientists' recommendations for 
touching up the MST control program are being collected.

On 15 April Anastasia reported some serious, apparent 
memory leak, problems with the MST program, resulting in 
very slow operation and disappearance of dialog windows. 
This is being addressed right now.

Both pycnometers keep having problems. Volume could 
apparently not be measured for some period. The one 
instrument brought up from the second-look lab leaked 
and could not be calibrated - it was packed up to be 
sent to shore. The other instrument was fixed by the ETs 
(circuit board), placed closer to the helium bottle, and 
the serial cable was replaced - it seems to be working 
fine now. MAD upload problems persisted but the generic 
uploader was completed, bugs were fixed, and it seems to 
be working fine.

Some PWS3 data were bad because the separation 
measurement was not zeroed correctly - this is a 
weakness in this system and should be eliminated with 
the MSCL and PWS4 installation in the future (see 
application task list for description).


2. OTHER ISSUES

2.1. TRANSIT

Peter and Cyndi will join Anastasia in Sydney, and stay 
on for the Townsville-Guam transit, to exercise and 
troubleshoot all PP systems (tuning, calibration, data 
acquisition, data upload, data retrieval), assess data 
quality, identify and describe problems to be addressed, 
update the PP Handbook, and plan for ongoing and new 
tasks such as the deployment of the MSCL (Geotek). The 
IS representatives were alerted again that the ship test 
database needs to be functional for a successful test of 
data upload and retrieval.

2.2. COLOR REFLECTANCE

Automated CR measurements were implemented on Leg 188, 
eliminating this applications task from the list.

A color reflectance measurement parameter protocol was 
implemented at the Leg 189 port call. Observer and 
illumination standards should always be set to 10° and 
65D. These settings should be recorded in the database 
for each run (section). Old color data will be 
recalculated using these parameters.

Color parameters (X, Y, Z, L*, a*, b*) are not 
calculated by the AMST program anymore. They are 
recorded directly from the Minolta CM2002 by the AMST 
program and are available for upload. It was decided 
that the database group upload data and calculations 
(performed by the CM2002) directly into the database 
starting with Leg 189, and recalculate color parameter 
values for all previous legs (except the "bad data 
legs"). In addition, the database group will calculate 
color parameters for Leg 189 for comparison with the 
uploaded Minolta calculations.

What standard data is the database group using to 
calculate XYZ? The constant factory values or the 
operators control measurement after white calibrations? 
Is the ASTM used to expand the spectrum for XYZ 
calculations?

2.3. BAR CODES

Fackler will sail on the transit and Leg 190. One of his 
top priorities will be implementation of bar codes for 
the MST. This will be a basic implementation without 
fancy database checks. The human-readable section ID 
will be read, parsed, and entered into the appropriate 
fields in the MST program.

2.4. MSCL (GEOTEK)

The PP hard core met earlier to discuss options for 
implementing the multi-sensor core logger (MSCL) from 
Geotek. The track should allow measurement of GRA, PWL 
(=PWS3), and MS on split cores, and perhaps on full 
cores (depending on implementation). Still need to 
decide if cores should be pushed or transported on a 
boat. One tentative plan is to
   1. Confirm with SCIMP that the AVS can be removed 
(second-look lab);
   2. Build a simple PWS4 system to replace PWS3 in part 
(perhaps in Downhole lab?);
   3. Build a new PWS1/2 track at the auxiliary sampling 
table;
   4. Get MSCL ready on shore (including new PWS3 and 
GRA; and perhaps MSP)
   5. Dismantle present VS-track and install MSCL in its 
place.
The main question is if (3) is possible in the rather 
crammed core lab. In any case. (3) to (5) are on hold 
until the higher-priority digital imaging is 
implemented. Logistical and resource options need to be 
re-evaluated at that time.

2.5. TRANSFER OF APPLICATION CUSTODIANSHIP

The WCMST application custodianship has been transferred 
to the ISD. The next target for transfer is the AMST 
program.


3. ACTION ITEMS

(ATL = PP application task list; JRL = Janus Review 
List; G2-2 = JRL Group 2, priority 2)

3.1. TASKS COMPLETED

Application development tasks
€ Automated CR (eliminate from ATL and JRL-G2-11)
€ Implement updated MAD (eliminate from ATL and JRL-G3-
16)
Other tasks
€ Reinstalled PP lab systems during Leg 188.
€ Converted MST program to the PC platform
€ Transferred custodian ship for MST program from Mills 
to the ISD

3.2. OLD TASKS NOT COMPLETED

Application development tasks
€ NGR (and GRA) data transfer (see ATL; G3-9) [Mills].
€ Upgrade PWS (see ATL; G2-3) [Ledwon/Mills].
€ MAD control measurements (see ATL; G3-13) [ISD/Blum].
€ PWL calibration report (see ATL and JRL-G3-17) 
[ISD/Blum/Mills]
€ TC user interface (see ATL; G2-7) [Becker/Blum].
€ TC data model (see ATL; G3-12) [Mithal/Blum].
€ Implement bar codes (see ATL; G2-2) [ISD/Mills].
€ WCMST threshold warnings (see ATL; G3-10) 
[ISD/Mills/Blum].
€ MSL drift correction (partly addressed) (see ATL; G3-
22) [Mills/Blum].
€ WCMST control data (see ATL; G2-13) [Mills/Blum/ISD].
€ Implement PWS4 system (see ATL; G2-14) [Mills/Ledwon].
€ Simultaneous MSP (MSCL or AMST) (see ATL; G2-16) 
[Mills].
€ Upgrade "Strength" (on hold; see ATL; G3-28)
Other tasks
€ Upgrade PWL displacement measurement [Mills].
€ Upgrade PWL signal source [Mills].
€ Purchase a third pycnometer [Prince/Julson].
€ Prepare an upgraded PWS1/2 (& AVS) system to free up 
the space for the MSCL.
€ Finalize plan for MSCL (Geotek) installation [PP LWT].

3.3. NEW TASKS

Application development tasks
€ Fix MAD report (see ATL) [ISD/Blum].
Other tasks
€ Specify and order spare core boats [Mills]
€ Order PCI Maestro boards for NGR (and GRA) data 
transfer [Mills]
€ What happened to WCMST control program (or system 
software) on Leg 189 [Mills].
€ Test MST logging speed and reported core boat problems 
[Ledwon/Blum/Prince].
€ Verify/specify scientists' problems/suggestions for 
MST program fixes (transit) [Blum].
€ Clarify with SCIMP if AVS is coming off the track or 
not [Blum].
€ Investigate how X,Y,Z are calculated in respect to 
which calibration data [Freeman/Clark]
€ Database group to present their color calculations for 
comparison with CM2002 calculations for Leg 189 
[Clark/Blum]

APPENDIX I: PP APPLICATION TASK LIST, 18 APRIL, 2000
 
REFERENCE: NGR DATA TRANSFER
CONTACT: PP-LWT
DATE: 9/21/99; modified 12/3/99
DATA SYSTEM: WCMST-NGR
OBJECTIVE: Increase speed and/or 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 planned change of the 
WCMST control software to the PC platform.
RESOURCES: Estimated 20 hr of hardware modifications and 
Labview programming.

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) and density (g/cm^3) 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: 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: PWL CALIBRATION DATA
CONTACT:PP-LWG
DATE: 9/21/99; modified 12/3/99; updated 4/18/00
DATA SYSTEM: WCMST-PWL
OBJECTIVE: Fix calibration data report and check 
calculation of "Time M0" in MST program.
RATIONALE: The present web query for PWL calibration 
data has a few errors that need to be fixed. This report 
is important for routine quality control and 
troubleshooting. Needs to be fixed. It is also possible 
that one coefficient (Time M0 = delay) is not calculated 
correctly in the MST program, which could explain 
observed deviation from expected values when measuring 
the water standard.
TASK(S): 1. Web report: Eliminate redundant record for 
each measurement (query bug). Change label "Time M1" to 
"Time 1/M1". Increase format of "Time 1/M1" to 4 
significant digits. 2. MST program: Increase format of 
"Time 1/M1" to 4 significant digits. Check if "Time M0" 
(= delay) is calculated using standard length as 
independent variable and measured time as dependent 
variable. Suspect the reverse is true.
RESOURCES: Estimated 10 hr of programming.

REFERENCE: UPGRADE "PWS"
CONTACT: PP-LWT
DATE: 9/21/99; modified 12/3/99
DATA SYSTEM: "PWS"
OBJECTIVE: Provide a bug-free, more user-friendly PWS 
user interface incl. upload/editing (on PC platform).
RATIONALE: Problems with the PWS user interface (part of 
present "VS" program) have been reported from many legs 
(e.g., description from Leg 177; many tech reports). 
Data saving, sample identification, and setting options 
are not clear and/or intuitive enough, resulting in bad 
and/or lost data. The upload and backup of "VS" data 
(using the JANUS.PhysProps application) has never been 
satisfactory. Finally, a general plan to transfer the 
program to a PC platform exists.
TASK(S): Option 1: Quick-fix Mac version (minimum data 
saving problem and PWS separation problem). Option 2: 
Clone PC version. Split the "PWS" (PWS1, PWS2, and PWS3) 
from the "Strength" (AVS, TOR, and PEN) application in 
preparation for upcoming changes. Integrate the saving, 
upload and edit functions more closely with the 
operational interface. Upgrade the sample positioning 
hardware in the course of this project (hardware 
component!).
RESOURCES: Estimated 120 hr of Labview programming and 
testing.

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: PWL CALIBRATION DATA
CONTACT: PP-LWT
DATE: 9/21/99; modified 12/3/99
DATA SYSTEM: WCMST-PWL
OBJECTIVE: Make calibration data available.
RATIONALE: The present web query for PWL calibration 
data returns all core data records associated with each 
calibration instead of only the calibration data.
TASK(S): Fix the web query.
RESOURCES: Estimated 40 hr of programming.
 
REFERENCE: REPLACE JANUS.MST WITH "DIRECT" UPLOAD
CONTACT: PP-LWT
DATE: 9/21/99; modified 12/3/99
DATA SYSTEM: WCMST-ALL SENSORS
OBJECTIVE: Make WCMST data upload and access more 
automated, thus efficient.
RATIONALE: With the present WCMST upload application 
"JANUS.MST" (which does not handle NGR data anymore), 
data upload and availability on the ship require an 
experienced operator to perform regular batch jobs. 
Scientists often depend on ODP personnel to upload the 
data. There is presently a trend away from JANUS.* 
applications, and towards Labview upload programs that 
interact more smoothly with the instrument 
control/output components.
TASK(S): Replace manual data upload with a more 
automated and integrated function that makes data more 
consistently available in near-real time. When the 
operator saves a section run, write data not only to 
local disk (backup), but also directly to the database. 
Don't save/upload if operator cancels the save dialog. 
At the same time, integrate the edit function and add a 
user-friendly interface that allows a run to be deleted 
or a section id to be changed. The local database 
(backup files) should be edited at the same time as the 
central database. Completion of this task would 
eliminate the JANUS.MST application from the inventory.
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: UPGRADE "STRENGTH"
CONTACT: PP-LWT
DATE: 9/21/99; modified 12/3/99
DATA SYSTEM: " STRENGTH "
OBJECTIVE: Provide an upgraded interface, incl. 
upload/editing (on PC platform).
RATIONALE: The "VSR" application needs an upgrade for 
some of the reasons outlined in UPGRADE "PWS" task, 
although it is not that much affected. However, if the 
PWS component is upgraded and transferred to the PC 
platform, the same needs to happen to the AVS component. 
The two applications should then replace the present 
"VSR" application, and the JANUS.PHYSPROPS upload 
application would be replaced as well.
TASK(S): As the application is updated for the PC 
platform, split it from the "PWS" application. It will 
include AVS, TOR, and PEN. Integrate upload and editing 
functions. Upgrade the sample positioning hardware in 
the course of this project (hardware component!).
RESOURCES: Estimated 80 hr of Labview programming and 
testing.