CalCOFI Electronic Sample Log (CESL): replaces the paper sample form used to log seawater samples taken from the rosette. The CESL electronic form, once saved (in csv format), can be recalled for additional data entry or editing.
Input: CESL reads in the sample log base file (YYMM###.log) generated by the CTDBackup program using the CTD .mrk, .hdr, & CTDatDepth.txt files. (See CTDBackup).
CESL's design is modular, using txt files to auto fill the drop-down selection lists.
- Location: Tablet pc in the wetlab; base dir and setup files are in C:\CESL including how-to-setup-CESL txt files; output files are saved to the shared events dir (and are stored redundantly locally).
- Line & Sta are set automatically but may be changed by selecting from the drop-down lists; stas available are based on the line (ex selecting line 90 loads line90.txt sta list);
- CastType options are set in the casttype.txt file
- O2 Case (O2cases.txt): when a case is selected, CESL loads the default O2 flask numbers (which should be verified at the start of each cruise for agreement to the O2 case files); flask switching is possible by double-clicking the first flask, then single-clicking the destination. To save this change for next use, double-click the column header and select “OK” at the save prompt. Select the “# cont’d” option when continuing a case for shallow stations, selecting the flask # for the 1st sample.
- Salt Case (Saltcases.txt) sets the salt case number
- Nut Rack: colors rack codes selection is set by the nutracks.txt file
- manual key-entry override of default values is possible (for most fields)
- Auto-renumbering of sample numbers is accomplished by entering in the new start number is the first field then press <Enter> and “OK” when prompted; useful for multiple stations in one salt case
- There are a variety of ancillary bottle flags available by double-clicking the Nisk or Sam #; the list is set by bottles.txt and usually includes “mistrip”, “LTER-only”, “Prodo” which should already be flagged by the prod### file
Output: press F2 to save the log (when saving over the network it can be slow); CESL will prompt you to save a chl base file do so if not already generated. Next it will prompt you to save the O2 .box file, do so if not already done (O2 workstation dir must be available and mapped in CESL.cfg).
Important Facts about the file interactions necessary to make the data network work
It is very important that the cfg files for each program be configured properly at the start of the cruise. CODES will auto-generate the base directories on the server using the cfg module so once the data server is setup, do this next. Most program will function locally, if necessary.
Key systems to network:
- Event Log Tablet PC (celoggps.cfg), on New Horizon is setup in the Aft control winch shack; edit watch.txt with crew’s initials
- Primary CTD PC (ctdbackup.cfg; seasave.cfg); add latest sensor calibration coefficients; CTD pressure display output to MET using com 4; check CTD hdr & mrk formats
- Backup CTD PC (SCIMS; metcap.cfg) systems; connect to MET (NH), SCS (JD) or GPS via a 9pin (9 by 9 or 9 by 25) com cable
- Sample Log Tablet PC (cesl.cfg; lter.cfg, watch.txt, & misc txt files) in the wet lab;
- Synology External Hard Drive Data Server (network visibility then CODES subdirs); login as admin & password are on an external label; use the Synology Assistant utility to find, setup and manage the drive
- CODES/Prodo PC (codes.cfg) workstation; check print capability; needed for CODES’ PIC (prodo bottle spacing) module usually on 1st station
- Color laser printer (network availabilty).
- O2 PC: the “.box” dir should be shared and available to CESL system
- Flog PC: located in the chl/prodo van, run Cat5e and check network & printer visibility
- Email PC: setup a small workstation on the forward bench for general email use, can be wireless
Map the data server drive on all data acquisition computers - it is useful to map the drive as “Q” on all systems (Q is far enough down the list it should be available on all systems) since most config files are setup for that drive letter, cruise dirs will have to be updated to YYMM.
The CTD hdr and mrk file formats are critical since these programs search for specific words and formats to parse the information (refer to previous cruises for column or field specifics). Line & Sta numbering should be decimal such as 93.3 26.7, a single space separating decimal line & decimal sta.
CELogGPS should be available to the CTD operator on the primary or backup workstations so he/she can generate the CTDatDepth event number (if the Aft control pilot does not)
Prodo bottles are numbered properly in PIC; the sample log uses the prd### file so it is important the bottle numbers in the pop-up window match the rosette bottle numbering.
Versioning: be sure the programs being run are the latest versions since updates usually correct bugs/glitches/data format changes/etc. Typically, the latest versions are in the master directories on the data server.
|< Prev||Next >|