TNPD detection and treatment

This page is automatically created by code which scans all files in the Argo USGODAE GDAC.

Plots and listings analysing the Surface Pressure for TNPD floats for each DAC are accessed through the Plots Index Tables.


TNPD detected, and Reponses in D files

TNPD
AOMLBODCCORIOLISCSIRONMDISJMAMEDSCSIOINCOISKMAKORDITotal all DACs
# floats452141114735581911733431312731611199182
Trunc & known offset1051245416227-67821544139104893208
Floats apparently truncating and known offset, but corrected SP is negative at some stage
(ignoring whether profiles are DM or RT)
Very few -ve SP311-3-1146222888
more -ve SPs1----5----28
min SP > -14--1-15-11619
min SP = -5121-1-112--321
min SP < -51-----3----4
Floats with apparent TNPD
TNPD whole series169515226-962314341718500
TNPD part series256575938-1553715271525684
Counts of floats with these conditions in TNPD D-file profiles
TNPD in D-files309998046-20844285130-895
TNPD 6months DM290926643-18338254827-812
Some QC=1192244234-18528163029-580
Some min(QC)=2247906141-922927483-638
Some min(QC)=3716---15-----38
Some min(QC)=48842910-567-122-226
Imperfect COMMENTS present------13--21-34
Some COMMENTS present252946143-90162749--632
Some COMMENTS absent10622224-1322431017-340
Some min err 2.4316866549-20845165132-868
Some min err 2037132718-206277--155
Some not 2.4 or 20-21---------21

Table based on GDAC as at 9 March 2013


Explanation of categories

All values are the number of floats exhibiting the described conditions for each DAC.

# floats - number of floats in each DAC

Trunc & known offset - floats which are believed (from info in tech and meta files) to be a type which truncates, and for which the fixed firmware surface offset value (eg 5dbar) is known.

Floats apparently truncating and known offset, but corrected SP is negative at some stage - In theory this should not happen, however the occasional small -ve value is not a worry. Frequent or large negatives could arise from the float being wrongly identified as a truncating type. Values of exactly -5 can indicate missing SP reported as 0, or maybe 5dbar offset removed twice!

TNPD whole series - truncating floats with no +ve SP

TNPD part series - truncating floats with no +ve SP after some point

All the following conditions are determined for the D-files only.

TNPD in D-files - floats with TNPD in DM processed profiles (rather than only in profiles which have not yet been DM processed.)

TNPD 6months DM - floats with TNPD in DM processed profiles spanning at least 18 cycles, so would expect TNPD status to be acknowledged.

Some QC=1 - floats with some TNPD profiles with minimum PRES_ADJUSTED_QC==1

Some QC=2 - floats with some TNPD profiles with minimum PRES_ADJUSTED_QC==2

Some QC=3 - floats with some TNPD profiles with minimum PRES_ADJUSTED_QC==3

Some QC=4 - floats with some TNPD profiles with minimum PRES_ADJUSTED_QC==4

Looking for the approved TNPD comment string in the SCIENTIFIC_CALIB_COMMENTS variable. Now allow for the first dimension of that variable, NCALIB to be >1 (thanks to John Gilson). However, I still expect to find the TNPD string in the parts of the variable that correspond to the pressure parameter. That is, we always expect PARAMETER(1,:) = 'PRES', so any comments associated with pressure should be in SCIENTIFIC_CALIB_COMMENTS(n,1,:)

Imperfect COMMENTS present - floats where some profiles have comment containing "ncated" and "TNPD" or "TNDP", but not the full correct string.

Some COMMENTS present - floats where some profiles have correct TNPD comment.

Some COMMENTS absent - - floats where some of TNPD profiles do NOT have a correct or even imperfect TNPD comment.

Some min err 2.4 - floats where some of TNPD profiles have a minimum PRES_ADJUSTED_ERROR of 2.4

Some min err 20 - floats where some of TNPD profiles have a minimum PRES_ADJUSTED_ERROR of 20

Some not 2.4 or 20 - floats where some of TNPD profiles have a minimum PRES_ADJUSTED_ERROR of neither 2.4 nor 20.

 

Legal Notice and Disclaimer | Copyright | Privacy | Page author: Jeff Dunn | Contact: Jeff.Dunn@csiro.au