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 DatasetCCHDO-1.0 CF netCDF files converted from bottle exchange file
CCHDO-1.0 CF netCDF files converted from ctd exchange file
74DI233_1 processing - BTL 2022-10-06 C Berys Submissions id submit date submitted by file name ---- ------------- -------------- -------------------- 4572 2014-01-14 Robert Key 74DI19980423_hy1.csv Changes * changed PHAEO to PPHYTN * changed units for CTDPRS from DBARS to DBAR note: unresolved flag 0 for SALNTY, OXYGEN 74DI233_1_hy1.csv and 74DI233_1_nc_hyd.zip opened in JOA with no apparent problems. Conversions file converted from software -------------------- ----------------- ----------------------- 74DI233_1_nc_hyd.zip 74DI233_1_hy1.csv hydro 0.8.2-61-g3353cfe 74DI233_1hy.txt 74DI233_1_hy1.csv hydro 0.8.2-61-g3353cfe 74DI233_1_bottle.nc 74DI233_1_hy1.csv cchdo.hydro 1.0.2.2 Updated Files Manifest file stamp -------------------- ----------------- 74DI233_1_hy1.csv 20221006CCHSIOCBG 74DI233_1_nc_hyd.zip 20221006CCHSIOCBG 74DI233_1hy.txt 20221006CCHSIOCBG 74DI233_1_bottle.nc 20221006CCHSIOCBG
There is not enough information to know where this file should go in the timeline.
There is not enough information to know where this file should go in the timeline.
There is not enough information to know where this file should go in the timeline.
There is not enough information to know where this file should go in the timeline.
There is not enough information to know where this file should go in the timeline.
There is not enough information to know where this file should go in the timeline.
There is not enough information to know where this file should go in the timeline.
There is not enough information to know where this file should go in the timeline.
There is not enough information to know where this file should go in the timeline.
There is not enough information to know where this file should go in the timeline.
There is not enough information to know where this file should go in the timeline.
Added a short note on the 3rd page of Appendix A in the on-line documentation that the latitude in the table for station 13465 is likely 44 29.9 and not 43 29.
My file has the same value and I agree with your conclusion. I?ll correct mine, reprint, and send a copy to Alex. Also, for the notes (I added to my version of the header), the paper that Greg Johnson refers to in your note #330861 is Johnson, G.C., S.G. Purkey and J.M. Toole, Reduced Antarctic meridional overturning circulation reaches the North Atlantic Ocean, Geophys. Res. Lett., 35, L22601, doi:10.1029/2008GL035619, 2008. Don?t know that it is any help, but my edited/corrected file attached.
from CARINA Collection
The following files are now available online under 'Files as received', unprocessed by the CCHDO. 74DI19980423_hy1.csv
1. There is an error in the header information for CARINA cruise (74DI19980423, cruise number 172). It says that there are 44 full depth stations when in fact there are 138 stations. This is probably easier to fix with a simple text editor rather than going through the full normal procedures. If not, let me know and I'll resubmit (copy of edited file already e-mailed to Alex). The northern end of this cruise is a repeat of the A16N line from Iceland to about 33N 2. Yesterday I learned from Jon Olafsson that the Iceland Sea and Irminger Sea time series (cruise numbers 184 and 185) actually go back to 1983 (Taro was running the carbon back then). The current CARINA files start with 1991 (when Jon started carbon measurements). Jon will send me the older data this week. I'll merge and produce new versions of these 2 "cruise" files. Alex, we're going to want to issue a DOI for each of these files (separate from the CARINA data product DOIs). Jon will provide titles and author list for the DOIs (probably "The Iceland Sea Time Series" and "The Irminger Sea Time Series" or similar). I'll also "insert" these new records into the CARINA data products (for Alex and Reiner only). This will result in a new DOI and version for both the AMS and ATL data products. Since these files were not included in the 2nd QC, the only CARINA papers that will be affected are Jon's.
I have indeed published a paper on LSW differences along A16N including oxygen analyses in GRL (Johnson et al. 2005) this year using A16N data. The manuscript on SPMW oxygen differences is not yet out but it will be published (someday) in Prog. Oceanogr. in a special issue. That manuscript (Johnson & Gruber) has been accepted by the special issue guest editor (I. Yashayaev) and forwarded to one of the two editors-in-chief (D. Quadfasel), but I am not sure just how far along the whole issue is at present. You can find the 1998 data at the CCHDO under the repeat data (AR21): http://whpo.ucsd.edu/data/tables/repeat/subs/ar21_table.htm which is where I got them. The 1993 data are also listed in that table as residing at the WHPO, but the bottle data are still "not public". However, you can find them at this web side http://www.aoml.noaa.gov/ocd/oaces/natl93.html
I have unencrypted the bottle and ctd data for this cruise. In the process of updating the web files, it was found that the sumfile contained incorrectly formatted dates. This was corrected, along with other minor reformatting edits. The bottle and ctd exchange files were re-created and NetCDF bottle and exchange files were created for the first time, all with corrected dates. xml and html files were re-created and station track images were generated as well. All data files are now public and updated web pages reflect current status of data.
*See SUM entry.
*See SUM entry.
Sumfile was formatted. The data contained BE BO and EN data on the same line for all stations, the lines were split into 3 and the appropriate modifications were made. CTD and Bottle were converted to exchange. However this data remains encrypted. NETCDF and Inventory files will not be made until data are public.
*See BTL entry.
*See BTL entry.
E-mail ChiSci for pub status and help figuring out cast problem. Create exchange BOT CTD.
Rfmt all files. Email Smythe-Wright for PUB status. Create exchg
I think there has been a further misunderstanding as I understood from Peter that when he submitted the CFC data for me that he told WHPO that the CFC data couldn't be made public without checking with me first. My problem is that I have a graduate student working on the CHAOS data and while I am more than happy for the data to be public when the CD is released I should like ALL the data to remain restricted until then if at all possible. Penny Holiday thought it was possible for the data to be included in the CD but remain restricted until it was cut. I hope this is possible - please let me know if there are problems.
Replacement bottle, summary and CTD files have been obtained from the SOC ftp site as per M. Gould. Readme file in original subdirectory describes data edits and comments. this file will be emailed to meta-data manager. Sum file needs significant reformatting, bottle and CTD need minor reformatting. Files have replaced previously online data and index file has updated to reflect this change. No reformatting has been undertaken at this time. Data Edits Due to the contents of the BODC database and the WOCE data received the following comments are made: .SUM ---- Some changes were made to the dates and times from those received from the data originator's. The dates and times presented are correct and the date applies to the start time. .SEA ---- * SAMPNO -- this is not stored and is set to -9 * BTLNBR -- this is not stored and is set to -9 but it's flag is set to 2 if no problems were noted CTD-bottles that fire within +/- 4db of each other are averaged and the resultant values stored at BODC. In these instances, the data from the individual bottles are not stored. The bottle oxygen values for stations 13443 and 13444 are identical so both have been made suspect. The individual 'duplicate' bottle oxygen values for station 13551 were okay except that the 'averages' were set to 2.0 (a flag value). BODC re-calculated the 'average' values from these. CTD files --------- Data are upcast temperature and salinity, not downcast. The CTD oxygen within these files has been set null on the request of the data originators (since oxygen is downcast and T+S is upcast). The sampling rate and number of observations are not stored and are set to -9. Due to the suspect nature of the bottle oxygen data for stations 13443 and 13444, the calibration of the CTD oxygen for these 2 stations may also be suspect. Due to the bottle oxygen values for statin 13551 being set to a flag value of 2.0, the CTD oxygen for this station should therefore be ignored. Additional ---------- BODC stores as /l and not /kg and so the CTD temperature and salinity are used for the conversion. If either of these are null then the bottle data are multiplied by the factor 0.973.
This data (AR21 74DI233) *is* up online already, but I have also obtained the new data described below from Gould's website. RCS will follow. These files will replace current online files, but will still need minor reformatting. -Danie ------------------ Dear Martin, I will have to let Steve or Danie answer your question regarding whether they have grabbed your data and, if so, why the data are not yet up. (I don't know offhand whether Di233 is One Time [Steve] or Repeat [Danie], but they'll know.) Since we are many moons away from the V.3 CDs, there should be no problem on that account. You should hear soon from one of them. -Jim ---------- I've just been speaking with Peter Saunders about Di233 CTD and bottle data. He was anxious that the data were not up on your web site but we do understand the pressure you are all under. I made the data available on 04/04/2001, I'm not sure if you picked this stuff up. It's still on our anonymous ftp site but I've made a couple of small amendments, just ftp to ftp.pol.ac.uk and change directory to pub/bodc/demg/whpo The only difference between these CTD files and those of 04/04/2001 is that I've made the oxygen null for you, ie -9.0 (since this is downcast and the T+S are upcast). In his email to me today, Peter provided Di233 bottle CFC data and these are included, along with all other bottle parameters, in the .SEA file. The file di233.readme has just a minor update regarding the CTD oxygen being made null. I hope the data can make it onto version 3 of the CD-ROM. If you have any queries please do not hesitate to contact me. -Martin Gould
Steve Diggs referred to me the matter referred to in the email(s) copied below. I can see that the problem you face is that the up cast CTD P/T/S data have been recommended as the primary processed CTD P/T/S data for the cruise in question, but the CTD down cast CTD O2 data are the valid processed CTD O2 data for the cruise. I agree that your plan to also supply a set of files with down cast P/T/S/O2 is the only reasonable way to retain and archive the CTD O2 data for this cruise. This may create a small problem unless the up and down cast files are given distinctive names, but you have probably already thought about naming. If Steve finds the file names will fit well enough within WHP practice, or can be made to fit well enough, we are all set. Somehow we must flag the up cast data as the primary data set for CTD P/T/S, but we'll figure that out. Jerry Kappa, who keeps track of WHP documentation, will want to be sure to retain and archive the relevant documentation for this issue. The explanation in the messages you and Penny Holliday sent looks good to me, so long as this is accompanied by a statement clarifying which file names are associated with the up casts and which are associated with the down casts. Jim Swift At 5:35 PM 4/4/01, Martin Gould wrote: I visited the WHPO web site for AR21 and noticedthat you received the data previously from Denise Smythe-Wright but not in WHPO format. More importantly, the problem with the data was that there was a salinity hysteresis, see attached email. The CTD files that I have provided you with have upcast temp and sal but downcast oxygen. We can't put both up and down cast temp and sal in WHPO format files here in BODC without a software re-write. It might be possible though to put down casttemp and sal with the oxygen in one set of data files, and then just up cast temp and sal in a separate set of files. Shall I do this for you? from Martin Gould April 2001 I have Discovery 233 (WOCE section AR21) CTD profile and CTD bottle data for you. I have put them in our anonymous ftp area, just ftp to ftp.pol.ac.uk and change directory to pub/bodc/demg/whpo Please get back to me with any problems. Wed, 1 Dec 1999 from Penny Holliday This is to let you know that after much thought, plotting, investigation etc I have concluded that we should use the upcast CTD data from CHAOS for analysis, and not the downcast. The reason for this is that the CTD data suffers from a mismatch between the downcast and upcast data, which reveals itself most dramatically in deep T-S plots of the 1hz data. The problem came to light on D242 when I was able to make direct comparisons with another instrument. The offset in salinity amounts to approximately 0.003 psu in deep water (at constant T). I believe the problem is not caused by pressure hysteresis, but most likely by a pressure or temperature effect on the temperature sensor or some electronic component of the CTD. It is less likely to be the conductivity cell because the problem persisted despite a change of cell on D242 (unless both were faulty). I've yet to discuss the implications of this with John Smithers, but obviously this needs to be addressed for future cruises. The D233 upcast salinity data have been calibrated exactly to the water bottle samples and so have the most accurate salinity. Standard deviation of salinity residuals was low so I think we can have reasonable faith in this calibration. The upcast data has less vertical resolution because of the mixing by the motion of the package through the water, but for most of our purposes I believe this is not critical. For CTD oxygen, the downcast data are calibrated since the upcast data suffer from hysteresis - if you use these data you should stick to the .2db files. I have created a new directory in /data/gdd/dtt1/d233 called ctd2up. This contains 2dbar averaged upcast files for each station (*.2up) - they are sorted on pressure so look the same as the .2db files (same variables etc) except they derive from the upcast. The permissions are set to be readable by the chaos group. Penny But please send the CTD, and bottle sals, oxys, nuts, chl, nav and tsg to WHPO for both Di223 and Di233. The data are also in /working/gdd/dht3/nph/d233/ctd which you should have permission to read. fluor and trans are worked up, because those calibs are done to the 1 second down-up files from which the 2dbar files are created.
Steve Diggs referred to me the matter referred to in the email(s) copied below. I can see that the problem you face is that the up cast CTD P/T/S data have been recommended as the primary processed CTD P/T/S data for the cruise in question, but the CTD down cast CTD O2 data are the valid processed CTD O2 data for the cruise. I agree that your plan to also supply a set of files with down cast P/T/S/O2 is the only reasonable way to retain and archive the CTD O2 data for this cruise. This may create a small problem unless the up and down cast files are given distinctive names, but you have probably already thought about naming. If Steve finds the file names will fit well enough within WHP practice, or can be made to fit well enough, we are all set. Somehow we must flag the up cast data as the primary data set for CTD P/T/S, but we'll figure that out. Jerry Kappa, who keeps track of WHP documentation, will want to be sure to retain and archive the relevant documentation for this issue. The explanation in the messages you and Penny Holliday sent looks good to me, so long as this is accompanied by a statement clarifying which file names are associated with the up casts and which are associated with the down casts. At 5:35 PM 4/4/01, Martin Gould wrote: I visited the WHPO web site for AR21 and noticed that you received the data previously from Denise Smythe-Wright but not in WHPO format. More importantly, the problem with the data was that there was a salinity hysteresis, see attached email. The CTD files that I have provided you with have upcast temp and sal but downcast oxygen. We can't put both up and down cast temp and sal in WHPO format files here in BODC without a software re-write. It might be possible though to put down cast temp and sal with the oxygen in one set of data files, and then just up cast temp and sal in a separate set of files. Shall I do this for you? On Wednesday, April 04, 2001 Martin Gould wrote: I have Discovery 233 (WOCE section AR21) CTD profile and CTD bottle data for you. I have put them in our anonymous ftp area, just ftp to ftp.pol.ac.uk and change directory to pub/bodc/demg/whpo On Wed, 1 Dec 1999 at 16:25:42 +0100 Penny Holiday Wrote: This is to let you know that after much thought, plotting, investigation etc I have concluded that we should use the upcast CTD data from CHAOS for analysis, and not the downcast. The reason for this is that the CTD data suffers from a mismatch between the downcast and upcast data, which reveals itself most dramatically in deep T-S plots of the 1hz data. The problem came to light on D242 when I was able to make direct comparisons with another instrument. The offset in salinity amounts to approximately 0.003 psu in deep water (at constant T). I believe the problem is not caused by pressure hysteresis, but most likely by a pressure or temperature effect on the temperature sensor or some electronic component of the CTD. It is less likely to be the conductivity cell because the problem persisted despite a change of cell on D242 (unless both were faulty). I've yet to discuss the implications of this with John Smithers, but obviously this needs to be addressed for future cruises. The D233 upcast salinity data have been calibrated exactly to the water bottle samples and so have the most accurate salinity. Standard deviation of salinity residuals was low so I think we can have reasonable faith in this calibration. The upcast data has less vertical resolution because of the mixing by the motion of the package through the water, but for most of our purposes I believe this is not critical. For CTD oxygen, the downcast data are calibrated since the upcast data suffer from hysteresis - if you use these data you should stick to the .2db files. I have created a new directory in /data/gdd/dtt1/d233 called ctd2up. This contains 2dbar averaged upcast files for each station (*.2up) - they are sorted on pressure so look the same as the .2db files (same variables etc) except they derive from the upcast. The permissions are set to be readable by the chaos group. But please send the CTD, and bottle sals, oxys, nuts, chl, nav and tsg to WHPO for both Di223 and Di233. The data are also in /working/gdd/dht3/nph/d233/ctd which you should have permission to read. fluor and trans are worked up, because those calibs are done to the 1 second down-up files from which the 2dbar files are created.
I am presently in Bergen doing fieldwork and I need to clarify a few things before the AR21 data goes public because we found some errors with the CTD salinity. I shall try to sort this out remotely but it may not be possible until I return to SOC on 5 June. It will only be the bottle (T, S, Nuts, O2) and CTD data that will be ready for public release. The CFC data needs further quatlity check and is also the subject of a PhD thesis. We don't have any C14 data. So please leave this with me and remind me before the final cut off date
Now that we have agreed that the AR21 identification I will finish the document and get an electronic copy to you.