sg271_20260302T193828_R.nc

mission.yaml against the data

Lines for the mission.yaml this conversion was given, where it and the output disagree or fall short: the requested dives against the dives that reached the file; platform fields set in the config against the values the files carry (the config wins by design, e.g. a local nickname for PLATFORM_SERIAL_NUMBER, so a pair is a value to check, not an error); platform fields written as UNK or omitted; institution ids the registry resolved; and missing ACDD globals. Only checks that find something are shown.

Missing globals

OG1 highly desirable and ACDD 1.3 globals the file does not carry (the OG1 ones are those validate warns about). Not listed, because the converter should supply them (computed from the data, or a constant): geospatial_bounds_crs, geospatial_bounds_vertical_crs, standard_name_vocabulary, time_coverage_resolution. Not listed, because OG1 records people and organisations in contributor_* and contributing_institutions_* instead: creator_email, creator_name, creator_url, publisher_email, publisher_name, publisher_url.

Variables OG1 defines differently

These passed through under their basestation names; OG1 has no home for them, or names them for a different quantity. Add them to drop_variables to leave them out of the file. dissolved_oxygen_sat: a per-mass saturation concentration (micromoles/kg); OG1 OXYSAT is percent saturation, a different quantity, so this is not mapped to OXYSAT. gsw_sigma0: the density anomaly (sigma0 = potential density - 1000); OG1 POTDENS0 is full potential density, which is derived separately, so gsw_sigma0 has no OG1 home.

Duplicate variables

These passed through under their basestation names but hold the same values as a mapped OG1 variable, so they are redundant. density is identical to DENSITY, which maps to the OG1 variable; legato_conduc is identical to CNDC_RAW, which maps to the OG1 variable. Keep the mapped one and drop the copy.

1. Before → after

What the conversion read and what it wrote. The basestation column is read from the conversion record beside the file. "same" means the quantity is unchanged by conversion.

542 of 542 inputs accounted for · nothing dropped · nothing removed · OG1 mandatory complete

1b. Unit corrections

What the conversion did to each variable's units. Label corrected: the basestation label was wrong for the magnitude, so only the label was fixed and the value left unchanged. Converted: the values were scaled by the factor shown to reach the OG1 units. OG1 label adopted: the basestation file carried no units, so the OG1 label was taken (the value is unchanged, assumed to be in those units). A pure spelling rewrite with no value change is not listed; the Unit mapping docs page carries the full spelling view. Only variables whose units were corrected, converted, or adopted are shown.

2. The OG1 file

The output read by what OG1 says it must and may contain, not by where it came from — the view that answers "where did the elements of my OG1 file come from". Orig var names the basestation variable (or how the converter built it) and Orig dim its basestation dimension.

Required by OG1

OG1 required: 14 of 14 variables present. The list is the upstream checker's (ioos/cc-plugin-og); amber: a required variable or the required dimension is absent.

Sensors named by OG1 (not required)

3 SENSOR_* variables, from the basestation calibration comments and config/OG1_sensor_attributes.yaml. Used by lists the variables whose sensor attribute names the sensor. Amber: the serial number or calibration date is a placeholder (empty, or every digit zero), so the basestation configuration did not record it; or two sensors share a serial number, which usually means a calibration comment was copied from another instrument. Both come from the basestation sg_calib_constants; check them against the calibration sheets.

Named by OG1 (not required)

53 variables OG1 has a defined name and meaning for, present but not required — the science payload, phase and profile variables, and QC flags (the sensors are in the table above).

Candidate for OG1 — flight model — input

3 of 3 present. Variables the project proposes to canonise (not yet in the OG1 vocabulary); recorded in vocabularies.OG1_CANDIDATE_VARS. An absent candidate (amber) is informational — a file may predate it.

Candidate for OG1 — flight model — output

14 of 14 present. Variables the project proposes to canonise (not yet in the OG1 vocabulary); recorded in vocabularies.OG1_CANDIDATE_VARS. An absent candidate (amber) is informational — a file may predate it.

Carried through (not OG1)

Basestation variables kept so the conversion loses nothing, summarised by family; expand a row to list its variables.

Same quantity, more than once

Where more than one output variable encodes the same quantity (shared standard_name, not matched by name). The reference row (first, from the OG1-required or OG1-named member) sets the baseline; each other row is that variable minus the reference (mean offset, RMSD and max |diff|), over the samples both carry, in the reference's units. "not comparable" where the unit alias table relates no conversion; the difference-against-depth figure is a deferred follow-up.

depth — reference DEPTH (m)

latitude — reference LATITUDE (degrees_north)

longitude — reference LONGITUDE (degrees_east)

sea_water_density — reference DENSITY (kg m-3)

sea_water_electrical_conductivity — reference CNDC (mS cm-1)

sea_water_practical_salinity — reference PSAL (1e-3)

sea_water_pressure — reference PRES (dbar)

sea_water_sigma_theta — reference SIGTHETA (kg m-3)

sea_water_temperature — reference TEMP (degree_Celsius)

3. Reconciliation — where the variables went

The six fates sum to the 542 basestation input variables.

Fate	Count	Meaning
Renamed from a basestation name	57	In the file under its OG1 name; original_name holds the basestation name.
Passed through unrenamed	475	In the file under its basestation name.
Consumed → derived	9	Not in the file itself; its data went into a variable the converter built (see Derived variables).
Removed (package drop list)	0	Not in the file; was on the package drop list, now empty (see Dropped and removed variables).
Dropped (keep_variables)	0	Not in the file; left out by your keep_variables.
Skipped (dimension)	1	Not in the file; its dimension is not placed on N_MEASUREMENTS (see Dimensions).
Basestation inputs	542

4. Presence across dives

542 variables over 3 dives; 500 on every dive, 42 on some (5 patterns). The converter works from the union of the input files' variables.

One row per pattern: the dives a group of variables has values in (Valid in) and the dives it exists in at all (Present in), each with its share of the input dives. Amber: a Valid % below 100 — has values on fewer than every input dive (a sensor switched on or off mid-mission, a quantity only computed after the first dive, or an occasional log entry). Each % is the share of the input dives.

5. Dimensions

Amber: dimension skipped — no variable from it reaches this file. Fate is read from the output: backbone — the dimension whose samples define N_MEASUREMENTS; merged — its samples are added to N_MEASUREMENTS at their own times; skipped — not in the file. Samples in is that dimension's length summed over the input files ("—" when the conversion record is absent).

6. Derived variables

Variables the converter built rather than renamed. Sources names the basestation variables consumed, or "(computed)" when built from other OG1 variables, vocabulary or global attributes.

7. Dropped and removed variables

Dropped on request (keep_variables)

Not applicable to this file: no variables were dropped on request.

Removed by the converter (package drop list)

Not applicable to this file: the package drop list is empty, so every basestation variable is retained.

8. By basestation origin (variables grouped by original dimension)

The same output variables read the other way — what became of each dive file's variables, grouped by the basestation dimension they came from.

Variables on codaTODO_data_point

codaTODO_data_point supplied 1,956 of 9,318 samples (21.0 %); a variable with a lower Valid % has missing values of its own. Amber marks any Valid % below 100 — the variable sits at its own times on the shared axis, not interpolated.

Variables on ctd_data_point

ctd_data_point supplied 3,904 of 9,318 samples (41.9 %); a variable with a lower Valid % has missing values of its own. Amber marks any Valid % below 100 — the variable sits at its own times on the shared axis, not interpolated.

Variables on depth_data_point

depth_data_point supplied 719 of 9,318 samples (7.7 %); a variable with a lower Valid % has missing values of its own. Amber marks any Valid % below 100 — the variable sits at its own times on the shared axis, not interpolated.

Variables on gc_event

gc_event supplied 21 of 9,318 samples (0.2 %); a variable with a lower Valid % has missing values of its own. Amber marks any Valid % below 100 — the variable sits at its own times on the shared axis, not interpolated.

Variables on gc_state

gc_state supplied 25 of 9,318 samples (0.3 %); a variable with a lower Valid % has missing values of its own. Amber marks any Valid % below 100 — the variable sits at its own times on the shared axis, not interpolated.

Variables on gps_info

gps_info supplied 9 of 9,318 samples (0.1 %); a variable with a lower Valid % has missing values of its own. Amber marks any Valid % below 100 — the variable sits at its own times on the shared axis, not interpolated.

Variables on legato_data_point

legato_data_point supplied 3,904 of 9,318 samples (41.9 %); a variable with a lower Valid % has missing values of its own. Amber marks any Valid % below 100 — the variable sits at its own times on the shared axis, not interpolated.

Variables on magnetometer_data_point

magnetometer_data_point supplied 721 of 9,318 samples (7.7 %); a variable with a lower Valid % has missing values of its own. Amber marks any Valid % below 100 — the variable sits at its own times on the shared axis, not interpolated.

Variables on sg_data_point

sg_data_point supplied 721 of 9,318 samples (7.7 %); a variable with a lower Valid % has missing values of its own. Amber marks any Valid % below 100 — the variable sits at its own times on the shared axis, not interpolated.

Variables on tridentebb700chla470fdom365_data_point

tridentebb700chla470fdom365_data_point supplied 1,957 of 9,318 samples (21.0 %); a variable with a lower Valid % has missing values of its own. Amber marks any Valid % below 100 — the variable sits at its own times on the shared axis, not interpolated.

Variables on Derived (no basestation dimension)

Converter-built variables carry values at their own times on the shared axis; a low Valid % is expected here. Amber marks any Valid % below 100 — the variable sits at its own times on the shared axis, not interpolated.

9. Global attributes

OG1 requirement: mandatory 9/9 present · highly desirable 8/14 (missing: internal_mission_identifier, site_vocabulary, program, program_vocabulary, data_url, doi) · suggested 8/11 (missing: network, uri, web_link)

Identity & discovery

Spatiotemporal coverage

People & institutions

Rights & access

Provenance & processing

History

10. Scalar parameters

Split by whether the converter renamed the scalar to an OG1 name, then by basestation prefix. A per-dive scalar's Value shows the decoded per-dive values; its raw JSON serialization stays in the Attributes disclosure. The renamed group is open; expand the others as needed.