CalCOFI Shipboard Program-Data Network Flow
CalCOFI’s data network has become a key component to data collection at sea. Using several CalCOFI develop software programs, all computer systems interact with the CalCOFI network data server, SeaServ, so network connectivity is highly desirable.
Standalone operation(s) are possible, but not optimal – see the individual program documentation for more details.
1. MetCapture
a. Location: C:\CELogGPS; on CTDBlade2 (backup CTD pc)
b. Configuration file: C:\CELogGPS\metcapture.cfg (see MetCapture documentation)
c. Input: MET, SCS, or GPS serial feed(s).
d. Outputs: two filetypes –
1). currpos.csv, the GPS/positional data used by CELogGPS;
2). MET/SCS data files when MET/SCS is available, YYMMSSMETEV_DDMMYYYY.csv
2). MET/SCS data files when MET/SCS is available, YYMMSSMETEV_DDMMYYYY.csv
(eg 1210NHMETEV_23102012.csv; one file per day). This file compiles MET/SCS data with event numbers (from CELogGPS) appended to the end of the data record.
2. CELogGPS
a. Location: C:\CELogGPS; on CTDBlade2 and/or networked pcs
b. Configuration file: C:\CELogGPS\celoggps.cfg (see CELogGPS documentation)
c. Input: positional feed – either the MET string via METCapture's currpos.csv or a GPS feed (serial, usb, or tablet’s internal GPS; may require external antenna).
Multiple txt files are used to configure this program's event activities & other parameters. The specific filenames are defined in the CELogGPS.cfg file – refer to documentation for details.
Multiple txt files are used to configure this program's event activities & other parameters. The specific filenames are defined in the CELogGPS.cfg file – refer to documentation for details.
d. Outputs: YYMMevents.csv plus individual event csvs if run on multiple workstations; a html version is available for network viewing. CAUTION: opening the SeaServ event csv from anywhere on the network during data logging will crash the program, have users browse the html version.
3. CTDBackup (<Ctrl><Alt>B)
a. Location: C:\Ctdbackup; on CTDBlade1, primary CTD data acquisition pc
b. Configuration file: C:\ctdbackup\ctdbackup.cfg (see CTDBackup documentation)
c. Input: CTD data & cast files whose path are mapped in the cfg file; CTD-At-Depth event file (YYMMCTDatDepth.csv); it is important that the primary CTD operator or Bridge/Aft-control generates a ctd-at-depth event once the CTD reaches terminal depth and the first bottle is tripped.
d. Outputs: YYMM###.log for CESL; a zipped archive of all CTD data which is copied to drives mapped in the cfg (usually to the flash drive and SeaServ); CTD .hex, .bl, .mrk, .nav, .hdr files are copied to the data server CTD subdir (Q:\CODES\YYYY\YYMM\CTD)
4. CESL – CalCOFI Electronic Sample Log
a. Location: C:\CESL; on wet lab tablet pc
b. Configuration file: C:\CESL\cesl.cfg (see CESL documentation)
c. Input: sample log base file (YYMM###.log) generated by the CTDBackup program & prd### for prodo bottle designation.
d. Outputs: base files for most analyses -
1). salt program base files (Q:\CODES\YYYY\YYMM\SALT\salt###);
2). O2 box files (###01.box; copied to the auto-titrator pc's O2 box subdir, mapped in CESL.cfg as O:\);
3). chl base files (Q:\CODES\YYYY\YYMM\chl\chl###) & filtration form;
4). printout of sample log
1). salt program base files (Q:\CODES\YYYY\YYMM\SALT\salt###);
2). O2 box files (###01.box; copied to the auto-titrator pc's O2 box subdir, mapped in CESL.cfg as O:\);
3). chl base files (Q:\CODES\YYYY\YYMM\chl\chl###) & filtration form;
4). printout of sample log
5. SalReCap – Salinity Recording & Capture
a. Location: C:\PSal; on the Portasal pc
b. Configuration file: C:\PSAL\psal.cfg (see SaliReCap documentation)
c. Input: EXPED (C:\PSAL\EXPED); salt### base files (Q:\CODES\YYYY\YYMM\SALT\salt###); analyst.txt; YYMM###.csv sta.csv for CTD salinity comparisons.
d. Outputs: H###02 legacy salt files; salt###.csv .prn .htm files; YYMM_salt###.con (tabulating all average conductivity reads for the run); YYMM_saltdb.csv (combined station salt data csv for data processing database).
| Next > |
|---|
