Files in the Dataset have been checked for format consistency, and merged into a single, integrated, downloadable file.
Download Entire Dataset Submit Data For This Cruise How to Cite DatasetFiles listed here may be useful and are provided 'as is'. Files might include raw data, intermediate processing, or other data collected on a cruise that is outside the current scope of CCHDO.
| Role | Data Type | Format | Filename (Download) |
|---|---|---|---|
| residual | bottle | exchange | 3220CGC92_1_noncompliant_hy1.csv (8.0 kB) |
CCHDO-1.0 CF netCDF files converted from bottle exchange file
CCHDO-1.0 CF netCDF files converted from ctd exchange file
File created in the CCHDO system
File created in the CCHDO system
File created in the CCHDO system
File created in the CCHDO system
3220CGC92_1 processing - BTL
2022-10-03
A Barna
Submissions
id submit date submitted by file name
---- ------------- -------------- -----------
5168 p13_hy1.csv
Changes
* Split rows with missing pressure into residual file
* Removed rows that were completely empty (all -999 and no flag 1s) from residual file
3220CGC92_1_hy1.csv and 3220CGC92_1_nc_hyd.zip opened in JOA with no apparent problems.
Conversions
note: converted and put online by E Aitoro
file converted from software
---------------------- ------------------- -----------------------
3220CGC92_1_nc_hyd.zip 3220CGC92_1_hy1.csv hydro 0.8.2-62-gb1f9390
3220CGC92_1hy.txt 3220CGC92_1_hy1.csv hydro 0.8.2-62-gb1f9390
Updated Files Manifest
file stamp
-------------------------------- -----------------
3220CGC92_1_hy1.csv 20221003CCHSIOAMB
3220CGC92_1_nc_hyd.zip 20221003CCHSIOAMB
3220CGC92_1hy.txt 20221003CCHSIOAMB
3220CGC92_1_noncompliant_hy1.csv 20221003CCHSIOAMB
File was created on or before this date
File was created on or before this date
File was created on or before this date
File was created on or before this date
File was created on or before this date
File was created on or before this date
File was created on or before this date
File was created on or before this date
Changed Q1 and Q2 flage for DELHE3 at sta. 56, bottle 128 from 2 to 3 re email from Lynne Talley, see below.
Date: Mon, 29 Mar 2004 23:41:42 -0800 (PST)
From: Lynne Talley <lynne@gyre.ucsd.edu>
Subject: p13 delhe3 flag sta 56
Sarilee - on P13, when the helium value at sta. 56, bottle 128, was flagged as "3", the DELHE3 value should also have been flagged as "3". Can you make this change? Thanks - Lynne
I had a look at the P13 sample, going back through all the sampling notes, extraction files, and mass spec analysis and see nothing pathological about them. However, the data DOES look odd, and in fact appears to be either contaminated with air (from an undetected leak during extraction) or a mis-identified sample from deeper in the water column. I frankly don't believe the result is real for that depth/location, so how do we flag it?
Changed Q1 and Q2 flag for helium on station 56 sample 128 from 2 to 3 re Jenkins and Talley.
Changed Q1 and Q2 flag for helium on station 56 sample 128 from 2 to 3 re Jenkins and Tallay. Made new exchange file, sent notes to Jerry.
Changed DELC14 value at station 71, bottle 120 from 120.2 to -120.2 re e-mail from Bob Key. Made new exchange file, sent notes to Jerry.
We're plotting p13.
We have a bullseye on station 71, bottle 120, ~500 dbar, value 120.2
It is very possible that it's just a sign problem - all other values nearby are negative. On the other positive values lurk just 200 dbar shallower.
Can you (Bob) please confirm positive or negative sign?
Thanks - I also tried to find your sections Bob on the internet, looked in the GLODAP site but couldn't figure out how to get to them. Can I get some new directions if they are still linked?
I have the value you mention (+120.2) flagged as 4, but it does appear to be a sign problem only. I checked the final report from NOSAMS for this cruise, but it did not include this station.
I forwarded your message to Ann McNichol to get the final answer on this sample and will let you know as soon as I hear.
Merged helium and tritium sent by Jenkins on July 22, 2003. Made new exchange file.
Merged the helium and tritium submitted by Jenkins on July 22, 2003.
The BTLNBR in his files did not agree with the BTLNBR in the online file. After comparing the pressures and his bottle number it was apparent (at least to me) that it was really the SAMPNO and that 100 had to be added to it (ie 33 was really 133). After changing those numbers everything merged without any problems.
I copied the QUALT1 flag into the QUALT2 flag for DELHE3, HELIUM, NEON, and TRITUM.
There was a station 5 in the helium and tritium files, but not in the online file, so it was not merged.
*See TRITUM entry.
*See TRITUM entry.
*See TRITUM entry.
Put excel file with helium and tritium submitted by Jenkins into p13/original/2003.07.22_UPDT_HE_TRIT_JENKINS. I am in the process of remerging.
Put excel file with helium and tritium submitted by Jenkins into p13/original/2003.07.22_UPDT_HE_TRIT_JENKINS. I am in the process of remerging.
Found email from Kent Fanning with revised NITRATE and NITRITE attached. Merged the revised values into online file. Made new exchange file.
Found email from Kent Fanning re revised NITRATE and NITRITE values for p13. The file CORRNO3NO2DATA.txt was appended to the email from Fanning with the note from Howard Masserin, see below. These reviesed values had never been merged, so I merged them.
There were 5 stations in the CORRNO2NO3DATA.txt file that were not in the online file (stas. 1-5). There was only one quality flag, so I set the QUALT2 flag to the same value as the QUALT1 flag.
*See NITRAT entry.
P13 Sta 40 BE should be corrected to 39 29.72N
Corrected sta. 40 BE latitude re Lynne Talley and John Bullister. Sent notes to Jerry and made new exchange file.
Replaced DELC13 decimal-1-data with decimal-2-data from same original data files. Notes file sent to Jerry with details.
Notes on P13 Feb. 21, 2003 D. Muus
1. Replaced 1-decimal-place DELC13 in p13hy.txt (20011003WHPOSIODM)
with 2-decimal-place DELC13 from:
/usr/export/html-public/data/onetime/pacific/p13/p13/
original/2000.06.12_P13_C13_McNICHOL
2. C13 data file starts with Station 5 (30 samples, Test station).
Web bottle file starts with Station 6.
3. Made new exchange file for Bottle data.
4. Checked new bottle file with Java Ocean Atlas.
New pdf and txt docs online
July 2001 CFCs merged into Sept 2000 bottle file containing all nutrients. See DQE discussion in DOC for discussion of NO3 and No2 problems. Deleted Sta 60 Ca 1 BO entry in SUM file since missing position would not allow conversion to exchange file.
New bottle, sum and exchange files now on web.
Notes on P13 CFC merging Oct 4, 2001. D. Muus
1. New CFC-11 and CFC-12 from:
/usr/export/html-public/data/onetime/pacific/p13/p13/original/2001.07.09_CFC_UPDT_WISEGARVER_P13/20010709.172534_WISEGARVER_P13/20010709.172534_WISEGARVER_P13_p13_CFC_DQE.dat
merged into SEA file prepared by Stacey Anfuso containing questioned nitrates and nitrates. (20000928WHPOSIOSRA)
No changes to Sept 2000 nutrients were made. SEE DQE documentation.
Nitrate and Nitrite from:
/usr/export/html-public/data/onetime/pacific/p13/p13/original/1999.02.23_Nitrat_Phspht_P13/p13fla~1.txt
All "1"s in QUALT1 changed to "9"s and QUALT2 replaced by new QUALT1 prior to merging.
2. SUMMARY file had no position for Station 60, Cast 1 BO. No data in Bottle file. Deleted BO line and left BE and EN lines in place to allow conversion to exchange format.
3. Exchange file checked using Java Ocean Atlas.
CTD and Bottle files in exchange format have been put online.
New documents have been put online. Old document was renamed and put into original directory.
It was brought to my attention that the WOCE Pacific/Indian He-Tr data was not as yet made public. After submitting it to you last year, I had intended on going through it one more time to ensure there were no problems with it. Unfortunately, I have not had the time to do this. Is it possible, therefore, to release it as public data, and if there are any subsequent minor revisions, to make changes? I suspect there might be a few samples in the set that might have got through our initial quality control.
2000.12.11 KJU
File contained here is a CRUISE SUMMARY and NOT sumfile. Documentation is online.
2000.10.11 KJU
Files were found in incoming directory under whp_reports. This directory was zipped, files were separated and placed under proper cruise. All of them are sum files.
Received 1997 August 15th.
I have put the Jenkins tritium data into WOCE format. There were no quality codes so I set the TRITUM to 2.
*Files for Tritium Data:
WOCE Indian Ocean = WITrit.dat Contains all legs
WOCE Pacific P10 = WP10Trit.dat
WOCE Pacific P13 = WP13Trit.dat
WOCE Pacific P14c = WP14cTrit.dat
WOCE Pacific P18 = WP18Trit.dat
WOCE Pacific P19 = WP19Trit.dat
WOCE Pacific P21 = WP21Trit.dat
SAVE South Atlnt = SAVETrit.dat
*Column Layout as follows: Station, Cast, Bottle, Pressure, Tritium, ErrTritium
*Units as follows: Tritium and ErrTritium in T.U.
*All data are unfortunately still preliminary until we have completed the laboratory intercomparision and intercalibration that is still underway.
Bottle: (ctdraw, cfc113, ccl4, helium, delhe3, delc14, delc13, tcarbn, alkali, helier, delher, c14err, c13err) REMERGED various parameters into updated hyd file sent by Bullister. DelC13 data has been masked until A. McNichol confirms the data are public. Hyd file from Bullister didn't contain CTDRAW data; these were extracted from outdated hyd file and merged into updated hyd file.
Bottle: (silcat, nitrat, nitrit, phspht, delc13, c13err)
NO3 and NO2 data in the on-line hyd file have been masked pending review by nutrient PI. DQE reports concerns regarding the quality of these data. Phosphate and silicate data are from the updated Bullister hyd file; these data have not been remerged (see comments in original subdir *REMERGE for further detail).
Regarding delC13 data, A.McNichol confirmed these data are public; data unmasked.
Bottle: (silcat, nitrat, nitrit, phspht, delc13, c13err)
NO3 and NO2 data in the on-line hyd file have been masked pending review by nutrient PI. DQE reports concerns regarding the quality of these data. Phosphate and silicate data are from the updated Bullister hyd file; these data have not been remerged (see comments in original subdir *REMERGE for further detail).
Regarding delC13 data, A.McNichol confirmed these data are public; data unmasked.
All the Pacific data (most of which I still need to send you) is public. I should be sending you a pile of data next month.
Also, if the future, if you have a question that you need answered immediately, the best person to get in contact with besides me is Dana Stuart. Her contact info is dstuart@whoi.edu
conclusion of meeting w/ L. Talley
Bullister submitted an updated version of the bottle file (original/1999.08.16_P13_SEA_SUM_BULLISTER/P13.sea). This version did not have rawCTD data. Had to pull rawCTD data, CFC113 data, and CCL4 data out of the outdated version of the bottle file and reformat to merge into updated bottle file. Done - 2000.09.26 SRA.
Related files data files are in the MERGED_DATA subdir:
P13.sea_edt.dat - pressure sorted bottle data file from Bullister (1999.08.16)
CFC113.dat - CFC113 data pulled out of outdated bottle file;remerged into new btl file
CCL4.dat - CCL4 data pulled out of outdated bottle file;remerged into new btl file
Merged TCARB/ALKALI data from Kozyr into updated btl file: 2000.02.04_P13_CO2_KOZYR/p13carb.txt ---> reformatted and edited.
These data are slightly different than the TCARB/ALKALI data that came in the bottle data file submitted as an updated by Bullister (mostly flag changes). Overwrote existing data with this data from Kozyr.
Merged [He]/delHe from Evans into updated btl file:
2000.04.13_P13_HE_DELHE_EVANS/p13woce.csv.txt ---> reformatted and edited (p13woce_csv_edt.txt).
Missing data fields were white space, edited into -9. Extracted delhel and delher data from btl file after merge, reformatted missing data to -999.0 (was -9.00); also, some missing data flags were '1', others were '9'...don't know why, couldn't make any correlation. Changed all missing data flags to '9'.
**Note : no tritium data to merge on this cruise?**
Merged DelC13 data from McNichol into updated btl file:
2000.06.12_P13_C13_McNICHOL/p13submt2.csv ---> reformatted and editied (p13_delc13_edt.dat).
This file needed to be opened in MSWord, and saved as 'text only w/ line breaks'.
Had to edit sample numbers.
Merged C14, extracted from updated Bullister btl file and reformatted so missing values were -999.0 (not -9.00). Remerged with existing bottle data flags.
Did not remerge NUTRIENTS. Data values in updated Bullister file are same as the resent values from Fanning's group, 1999.02.23_Nitrat_Phspht_P13/p13fla~1.txt. The Bullister nutrient data seems to be better because many of the flags on the questionable data (samples that were resubmitted by Fanning's group per DQE request) are at set at '3', where the Fanning data has many flags set as "~"....not sure what to make of this, but suspect it is better to post the nutrient data that came with the updated Bullister hyd file.
Also, 00_README in 1999.08.16_P13_SEA_SUM_BULLISTER states that nutrient data is updated in this version of the hyd file.
**NOTE** Do we want to mask these values as they are suspect, per DQE?
YES - per conversation with sd.
Masked only suspicious parameters, nitrate and nitrite. No comments made regarding problems with phosphate and silicate - these parameters not masked.
The complete hyd file is p13hy.txt in the *REMERGE dir. NO3 and NO2 will be masked out in the on-line version.
2000.09.25 SRA
Bullister submitted an updated version of the bottle file (original/1999.08.16_P13_SEA_SUM_BULLISTER/P13.sea).
This version did not have rawCTD data. Had to pull rawCTD data, CFC113 data, and CCL4 data out of
the outdated version of the bottle file and reformat to merge into updated bottle file. Done - 2000.09.26 SRA.
Related files data files are in the MERGED_DATA subdir:
P13.sea_edt.dat - pressure sorted bottle data file from Bullister (1999.08.16)
CFC113.dat - CFC113 data pulled out of outdated bottle file;remerged into new btl file
CCL4.dat - CCL4 data pulled out of outdated bottle file;remerged into new btl file
Merged TCARB/ALKALI data from Kozyr into updated btl file:
2000.02.04_P13_CO2_KOZYR/p13carb.txt ---> reformatted and edited.
These data are slightly different than the TCARB/ALKALI data that came in the bottle data file
submitted as an updated by Bullister (mostly flag changes). Overwrote existing data with
this data from Kozyr.
Merged [He]/delHe from Evans into updated btl file:
2000.04.13_P13_HE_DELHE_EVANS/p13woce.csv.txt ---> reformatted and edited (p13woce_csv_edt.txt).
Missing data fields were white space, edited into -9. Extracted delhel and delher data from
btl file after merge, reformatted missing data to -999.0 (was -9.00); also, some missing data flags
were '1', others were '9'...don't know why, couldn't make any correlation. Changed all missing
data flags to '9'.
**Note : no tritium data to merge on this cruise?**
Merged DelC13 data from McNichol into updated btl file:
2000.06.12_P13_C13_McNICHOL/p13submt2.csv ---> reformatted and editied (p13_delc13_edt.dat).
This file needed to be opened in MSWord, and saved as 'text only w/ line breaks'.
Had to edit sample numbers.
Merged C14, extracted from updated Bullister btl file and reformatted so missing values were -999.0
(not -9.00). Remerged with existing bottle data flags.
Did not remerge NUTRIENTS. Data values in updated Bullister file are same as the resent values from Fanning's group,
1999.02.23_Nitrat_Phspht_P13/p13fla~1.txt. The Bullister nutrient data seems to be better
because many of the flags on the questionable data (samples that were resubmitted by
Fanning's group per DQE request) are at set at '3', where the Fanning data has many flags
set as "~"....not sure what to make of this, but suspect it is better to post the nutrient
data that came with the updated Bullister hyd file.
Also, 00_README in 1999.08.16_P13_SEA_SUM_BULLISTER states that nutrient data is updated in this version
of the hyd file.
**NOTE** Do we want to mask these values as they are suspect, per DQE?
YES - per conversation with sd.
Masked only suspicious parameters, nitrate and nitrite. No comments made regarding problems with
phosphate and silicate - these parameters not masked.
The complete hyd file is p13hy.txt in the *REMERGE dir. NO3 and NO2 will be masked out in the on-line version.
I have just uploaded the file p13sbmt2.csv to your ftp site. It contains the following fields in a comma-delimited file: LabID, Trackline, Station, cast, niskin, del13C, QC
****Please tell me if this file and its format are acceptable to your office and I will start sending the remaining Pacific 13C data files.****
The LabID is to distinguish between the two laboratories where the majority of the measurements were made--University of Washington and NOSAMS, WHOI.
I have another file associated with this one which contains descriptions of the samples flagged with a "6". Do you have an appropriate location for this file or should I keep it?
P13 Changed to indicate data are at WHPO but not in WOCE format (RAW) and therefore not yet merged.
As of 3/2000 the 2 year clock expired on the last of the Pacific Ocean C14 data (P10). All Pacific Ocean WOCE C-14 data should be made public.
I just ftp'ed 4 files to your /INCOMING directory i8nwoce.csv p13woce.csv p16cwoce.csv p19cwoce.csv ... of the same form as before, comma delimited columns of station, cast, bottle, %delta He3, delta He3 data flag, molal [He], [He] data flag.
P13 data files have been appended to one file as per John Bullister (Nov. 1999). The first five stations were test stations and have been removed at his request. CO2 data have been merged into the bottle file.
The old directory structure has been consolidated into one entry for both legs. All files and tables have been edited to reflect the change in file structre and the CO2 addition.
CO2 data into p13:
-obtained p13 bottle files from WHPO. Two files were obtained (p13ahy.txt, p13bhy.txt).
-both files had same station numbers and header lines. Ran a diff on them with no results (exited with no differences).
-Only one CO2 file sent for p13 from Alex Kozyr to WHPO on 2000.02.04. File contains TCARBN and ALKALI with associated quality bytes.
-Used David Newton's fortran merging code mrgsea for merging.
-As per WHPO sumfiles for p13_a and p13_b were appended together. Changed blackslash to underscore in expocode.
Ran sumchk with no errors.
-Since both files were the same, I used p13a as the representative bottle file and merged on that file. Ran wocecvt on final merged bottle file(p13mrgout2.txt). Error from wocecvt resulted from first five (test) stations being left in the sumfile. These stations were removed from the bottle files as test stations at the request of John Bullister, the Chief Sci. However since there are data in the first five stations, this will be clarified with Bullister (at the request of Jim Swift and Steve Diggs). Final file containing first five stations is p13_co2_hy.txt, file w/o stations 1-5 is p13_co2_edt_hy.txt.
regarding the revised nutrient data for the WOCE P13 cruise (Aug-Oct, 1992; Chief Sci was John Bullister) that was sent to the WHPO on Feb 23, 1999. There were a few discrepancies between the reprocessed data and the updated bottle file from the Chief Scientist. Upon closer look at the revised nutrient values by our in-house DQE, some concerns were generated. Can
you please review the attached file from the DQE and comment on his concerns and/or questions. We want make sure there aren't any uncertainties remaining regarding the nutrient data and that we get the correct values and quality flags into the bottle file.
Notes follow on the reprocessing of the NO2 data from the P13 cruise.
The original DQE work clearly recognized and addressed the problems with the nutrient data set from Cruise P13. Relevant to the nitrite and nitrate data processing, let me reiterate some of these comments:
"The...nitrate profiles look very noisy and varying both layer by layer and station by station especially among the first half of the stations." (page 2). "DQE observes that the nitrite concentrations in the deeper layers at entire stations are unreasonably high and show unreliable values up to 0.4 umol/kg even at deeper layers....this 0.4 umol/kg of nitrite correspond 1% of the nitrate concentrations there and obviously affect the precision of the nitrate analyses...DQE, then, thinks that we can not ignore these high nitrite concentrations." (page 2).
Continuing page 2 and on page 3 of the report, the problems and two possible reasons for these problems are discussed.
In response, the data originator reviewed the "deep" nitrite data. Reprocessing has been done; the revised data listing incorporates the following:
1. all nitrite values of 0.05 or less have been changed to 0.00,
2. the Q1 flag for these values has been changed from 3 to 2 if not originally flagged 2,
3. the number in the nitrate column is now the nitrate + nitrite value, in other words, the value calculated from the nitrate channel is tabulated with no correction for the value calculated from the nitrite channel.
4. for nitrite values greater than 0.05umoles/kg, the nitrite value is shown in the data listing and is flagged 3
5. as in the original data listing the corresponding nitrate value has been corrected for the "high" nitrite value.
6. in the case of nitrite values exceeding 0.28 umol/kg, the nitrate value has been flagged 3.
I have some concerns about the reprocessed data.
1. the DQE gave an example (page 3) which indicated that at station 61, the high nitrite value (0.43 umol/kg) shouldn't be subtracted from the nitrate channel calculation before listing the corrected nitrate value. Examining the nitrate versus db curve and the phosphate/nitrate relationship in the deeper water column are excellents ways of evaluating the "goodness" of a particularly nitrate value. This doesn't seem to have been done on the 13 stations where high nitrite values occurred. This would not have taken very much time and certainly would have been helpful in evaluating all "high" deep nitrite data and in turn the corresponding nitrate value.
I plotted the nitrate and phosphate data from Table 2 for station 61. The uncorrected nitrate value at 3396 db fits better on the N03-db curve than the corrected value and the corrected value definitely falls below the PO4/NO3 curve for this station. In this case, the high nitrite value clearly shows a problem with the nitrite channel and not a general sample contamination problem.
2. based on measurements of duplicates, the data originator chose a detection limit of 0.05 umol/kg for nitrite and 0.28 for nitrate. These relatively large values indicate problems with both analyses. Full span for the nitrite channel is generally set at ~2. An absorbance difference of ~0.025 with a factor of ~2 gives a nitrite value of 0.05 umol/kg. An absorbance of 0.025 or even 0.0125 (1 std. dev.) is significantly different than zero. If 0.05 is taken as being equivalent to zero, why aren't all nitrite values decreased by 0.05 before being subtracted from the results of the nitrate channel computation? Why make the treatment of the nitrite data concentration dependent? I believe it is critical that data be handled consistently. This certainly has not been done with the revised nitrite data set.
All of the data sets I submitted recently (the ones with comma delimiters between data fields) can be considered to be public.
I just ftp'ed revised P13.sea and P13.sum files to the WHPO site. The salinity, nutrient and oxygen groups have gone over the DQE comments (made by Michio Oyama) and made most of the suggested changes in the revised version. We have also gone over the CFC data and made some
revisions.
You should have received a copy of the revised nutrient data and document file directly from the nutrient group (University of South Florida, Kent Fanning and Howard Rutherford) a while ago.
I have intentionally omitted the first five stations at the beginning if the expedition (stations 1-5). These were test casts made on the transit to the start of the P13 section. The locations of Sta 1-5 are still included in the P13.sum file.
We had a lot of PDR problems on this cruise, and some uncorrected depth values are missing from the .sum file. If UNC DEPTH values are unavailable for either the beginning, bottom or end (BE,BO,EN) of a cast, can the available values from the cast be used to fill in the missing slot(s)?
There are 4 stations (28,48,53,61) where no UNC depths are available for BE, BO or EN. Should these be:
a.) left blank?
b.) filled in with estimated values from a bathymetric chart or other source?
c.) interpolated from adjacent stations?
d.) other options?
There were 2 legs to this cruise, separated by a port stop in Kwajalein. I noticed that the cruise is broken into 2 sets of files (p13a and p13b) at the WHPO site. Unless there are compelling reasons, I would prefer if the data from the 2 legs were not split up.
We would welcome Michio Oyamaa (or other DQE'er) going over the revised file and checking that we have responded satisfactorily to any problems in the original files, and adding appropriate DQE flags go the revised version.
c14 collected and sent to AMS/WHOI. Checking w/ Quay re c14 data status. Tr/He data requested from Lupton/Jenkins
"but not published"
We are withholding the P13 data because the nutrients
are still not revised following DQE
There are still some issues for the P13 data set, especially related to the nutrients. I've tried to contact the nutrient PI a number of times over the past 18 months to resolve these, and so far received no reply. I'll try again and get back to you (hopefully with a final data set) in a couple of weeks.
I have just placed C-14 data and report for P13N into the WHPO incoming directory. The data should be ok as is except that the values have too many decimal places.
The data have been through qc and flags are in the data table.
The final data report was sent in 2 formats: a postscript file a FrameMaker mif file and all of the figures in compressed epsi format. If you have FrameMaker, the mif + epsi files should be most useful, otherwise, ps file.