Added a new "Step 3" button to add Quality Codes to CTD.csv output (see CTD.csv data format web page) -

• PrQ = pressure quality code;
• T1Q & T2Q = primary & secondary temperature quality codes;
• S1Q & S2Q = primary & secondary salinity quality codes;
• Ox1Q & Ox2Q = primary & secondary oxygen sensor quality codes (these carry over to the umol/Kg oxygen values since they are derived from ml/L);
• FlQ = fluorometer quality code;
• ISUSQ = ISUS nitrate sensor quality code;
• SigTheta1Q & SigTheta2 = T1S1 & T2S2 calculated sigma-theta densities
• TransQ = Transmissometer quality code
• pHQ = pH sensor quality code
• SPARQ = Surface PAR quality code
• PARQ = Remote PAR quality code

Codes - the data quality codes will follow the CalCOFI legacy codes

• no code = good data
• 8 = questionable data; bad calibration or bio-fouling
• 9 = bad or no data; sensor or pump failure

These quality codes have been added to flag bad or questionable data collected by our Seabird 911+ CTD sensors. Sensor failure, bio-fouling, or bad calibrations can generate poor or bad data but may still be included in the data file.

User-interface improvement request from JLW & DMW - make the cruise being processed more prominent. So the user interface was changed so the current cruise and datapath are front-n-center. Additional features/tweaks include either manually changing the cruise in the large text box or by selecting the cruises at the bottom of the screen. Either will update the current cruise to the one entered or selected and change the datapath.

Two features - one improved and one added:

Improved - the CSV Respacer module will work properly with the latest 2015 92-column sta.csv format. The additional nutrient datacodes were being excluded from the reformatting routine. This is strictly a visual improvement that allows use of a text editor to view the files easily; columns and values lineup vertically so visual parsing is easier.

Added - ported from the BtlVsCTD program, the column "purge values" routine has been added to DECODR. Using the header to generate the column selection, the user can select a specific column or set of columns to bulk edit or clear. This is designed to purge data that may have imported improperly into the wrong column. As the data processing scheme evolves and new columns are added, the multitude of routines that populate the columns need to be updated. If one isn't, it can import numbers into the wrong column, overwriting the original column occupant. This is rare fortunately, but did happen when derived oxygen in umol/Kg values were imported into the DIC bottle number column. DIC bottle numbers had to be reentered; oxygen in umol/Kg were reprocessed after the correction with the derived data populating the correct column. DIC bottle numbers are from the original CESL sample log.

Note: the BtlVsCTD column clearing routine was updated to work with the latest version of the CTD.csvs as well. It parses the header to generate the column selections.

CELogGPS user-interface has been redesigned for horizontal touch-screen use - CELog1511H is the latest version. The buttons will cycle through the different station activities and when [Record Event] is pressed, the activity will be recorded.

In this version, I've tuned the button selected to match the activity field until the [Record Event] is pressed. Then the next stage of an activity will be auto-selected, the user just needs to press [Record Event] button again. Once all the stages of the station activity are done, the event log user selects the next activity. Example: if CTD DEPLOYED is selected and [Record Event] pressed, the CTD AT DEPTH next stage will automatically fill the activity field, the user only needs to press [Record Event] when the CTD arrives at depth. Once pressed, the activity will auto-select CTD RECOVERED. Once recorded the event log selection will be neutral until the next activity is selected such as PAIROVET DEPLOYED.

A vertical version of the event log program, CELog1511V.exe, has also been created for tablet-use in the vertical orientation. All routines are identical to the horizontal version. Eventually, I'd like to make the horizontal or vertical form-format a dynamic option like most commercial tablet programs.

It came to my attention that salts can be miscalculated if the sample count in the header is wrong. If the last sample indicated by the sample count is not the end sub, the drift will be miscalculated. This was obvious when the bottle and CTD salts were merge by BtlVsCTD.

So there is a new module under the Salinity Tab that will read the selected H###02 files, count the number of samples which should be n-2. It will also check the header for start station and end station - basically it is a header checker. Nothing is done to the H###02 files but a YYMMHSaltCheck.txt file is created and tabulates the correctness or incorrectness of all the files processed. Additional features may be added to future versions.