California Cooperative Oceanic Fisheries Investigations

  • Increase font size
  • Default font size
  • Decrease font size
Home References CalCOFI Handbook CTD Primary Operator Duties

CTD Primary Operator Duties

E-mail Print PDF

CTD Primary Operator Duties (0911 version)

1). Maintain, repair, and replace the CTD “fish”, sensors, cables, carousel, and rosette frame.  Temperature, conductivity, & oxygen sensor calibrations every 6 months, cruise-schedule permitting; CTD “fish” and carousel service every five years.
At sea: monitor the carousel and sensor performance and service or replace accordingly.  If the sensor is questionable, replace it with the backup; if the carousel is mistripping, service the trigger mechanism in question, replacing if necessary..

2). Setup data server (calcofi_webdb) with current cruise dir – using CODES, select the [Config Settings] tab then [Edit/Update cfg…] tab, edit the cruise information and new data path then [Update and create new dirs].  This is only done once pre-cruise.

3). Network the primary and secondary CTD workstations to the data server, printer and ship interfaces: GPS/NMEA; MET: primary CTD should output to Seabird remote readout or MET winch readout; secondary CTD logs MET data to the server events dir with event #; run CELog on the backup CTD computer and monitor the aft control entries.  It is important the CTDatDepth event is created..

4).Update and configure the Seabird software, pre-cruise: download and install the latest version of the Seabird acquisition and data processing programs on the primary & secondary CTD computers.  Pre-cruise, setup the primary acquisition software with the latest calibration coefficients, file paths C:\YYMMSS, year, month, cruise; plus archived dir (C:\YYMMSS\archived; plus backup dirs, D:\YYMMSS & flash dir J:\YYMMSS (the backup dirs require a “readme.txt” file to zip properly).  On the task bar, set Ztree quick launch icon’s “start in” path (in properties) to automatically open the YYMM ctd dir.  Duplicate the setup on the secondary CTD computer so it can be swapped quickly; copy the Seabird program dir to the server then overwrite the Seabird dir on the backup CTD system so coefficients and display files are mirrored. 

At sea, run a deck calibration every other day to insure the fluorometer and transmissometer sensor responses are stable.  If not listed on the ODF provided calibration sheet, calculate the coefficients for the transmissometer after the first deck test so the tranmissometer data will calculate properly.  This is the main reason for the deck test.  There is an Excel spreadsheet preconfigured to do this.

5). During the cruise, using Filesync or ZTree, do daily backups of the CTD archived dir to the data server and personal workstation. 

6). Generate/update the stacst, weather, misc base files: using CODES, select [Import CTD Files >> Email] under the CTD Importer tab, select the new mrks to import, toggle any options like fluorometer sensitivity as needed then [OK]. 
Run the add anomalies module next, default settings are usually fine.  This routine compares the current observations vs the 50 year mean value, tabulating the differences into csvs which the contouring routine can plot.

7). Backup/sync the entire dataserver CODES\YYMM dir to your personal workstation.

8). Process the CTD downcast data using Seasoft with SVPG configs for Data Conversion, Filter, Cell TM, LoopEdit, Derive, BinAvg.  Run the SVPG app from the C:\SVPG dir, select Target Filetype 2: CTD then the 1st .cnv to import.  Required edits are: Cast # is always 1; Cruise # should be SSMMYY ie NH1008 for 0810NH; Ship Name is OTHER (with New Horizon defined in the svpg.par configuration file as WKWB, the NH call sign).  Select OK and a horizontal plot will display, press Enter or select Quit Plot from the menu.  Click R-T Message, add a data point (up to 30) if the plot needs additional resolving, click OK or Enter, Enter again to Quit Plot, then Yes or No for hit bottom (if shallower than 515, select Yes).  Repeat for all new cnvs then Exit when finished.  Navigate to the C:\_TEMP\TESTLONG\CTD\MESSAGES dir and merge the .KKY files together using NTSplit into YYMM_##-##.txt.  Open this file with Ultraedit, select all, and copy to clipboard.  Run your email program, address the message to This e-mail address is being protected from spambots. You need JavaScript enabled to view it ; in the subject line put XBTDATA in all caps and nothing else; 1st line of the text body is UNCLASSIFIED then pastes the data on the next lines.
Send the message. (Read the SVPG docs CLOSELY to properly install this quirky software – this is NOT uber-important but it is worthwhile on 0911).

9). After the completion of two lines, run DECODR’s horizontal plot module; select e-mail data source; set the Lines to contour then run.  This will generate preliminary plots of primary measurements.  Post on webserver, if available.

Common problems:
1). Using YYMMSS instead of YYMM.  I’ve tried to program around this but some programs (particularly CESL and CELog) will have trouble finding the each others files if the cruise is not consistently reference on ALL systems.  If one is configured as YYMMSS (where SS is ship code) and another is configured as YYMM they will create different filenames.  I recommend using YYMM.

2).  Processing number – most the programs expect consecutive station number and if a ‘500’, ‘900’ or ‘b’ cast is performed, the CTDbackup and CESL programs can have trouble.  Simplest solution is edit the C:\ctdbackup\ctdbackup.cfg to the desire number, hit <Ctrl><Alt>B, create your CESL base file (you will have to type the processing number into the upper right box on CESL to get it to load or edit C:\CESL\cesl.cfg’s procnum). 

The processing number (along with Line & Station numbering) tend to be the thing that causes the most problems with the software interaction.  It is important that the CTD operators fill out the header properly especially the cast # and line+sta.  The cast type (ROS, PRODO, SCOOS,ANC) are also important to reference in the header and event log.

Missing CTDatDepth event can cause mis-indexing, mis-dating of the sample log so be sure this event is done before CTDbackup is run even if it is well after the actual event. 
 

 

Newsflash

Follow the latest CalCOFI cruise status on Twitter at http://twitter.com/calcofi