Cruise: 18HU19960512 (dataset:GLODAPv2.NEW) Data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Synonyms (including errata!) for this cruise: AR07Wf; 18HU19960512; 18HU96006_1; AR07Wf;
IMPORTANT information for GLODAP Reference Group Editors: This adjustment is a published version for GLODAPv2!
Please wait while loading list of related files
- no files! -
Plot/Data files re. Parameter(s) (select parameter on left side to view!):
alkalinity:21
nitrate:26
oxygen:28
phosphate:25
salinity:28
silicate:26
tco2:25
- no files! -
View comment(s) (filtered by salinity in subject)
Autogenerated CTD salinity and CTD oxygen update
Automated update! This overwrites adjustment values (and flags) of CTDoxy and
CTDsal with the values from BOTsal and BOToxy for every cruise, unless CTDsal
(or CTDoxy) is not present or bad.
Salinity action ID:5; CTD salinity data good, setting CTD salinity offset and QC
flag to bottle values.
Oxygen action ID:6; CTD oxygen data good, setting CTD oxygen offset and QC flag
to bottle values.
Posted by svheuven@gmail.com on 2015-02-19 09:22:23 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - salinity
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2_ATL_for_Carsten.xls / 2015-01-08): : make 0. Cruise in highly variable
region. Matches quite well with its contemporaries. QC1. Some extreme flyers,
both high and low, below 1000m.
Posted by svheuven@gmail.com on 2015-01-08 16:40:58 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
18HU19960512/salinity: update slope+intercept
autogenerated: BOTsal is compatible with unchanged CTDsal
Posted by svheuven@gmail.com on 2014-12-18 16:52:39 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
18HU19960512/salinity: init slope+intercept
autogenerated: using BOTsal (few or no CTDsal or BOTsal>80%).
Posted by svheuven@gmail.com on 2014-02-25 17:02:12 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View comment(s) (filtered by ctd_salinity in subject)
Autogenerated CTD salinity and CTD oxygen update
Automated update! This overwrites adjustment values (and flags) of CTDoxy and
CTDsal with the values from BOTsal and BOToxy for every cruise, unless CTDsal
(or CTDoxy) is not present or bad.
Salinity action ID:5; CTD salinity data good, setting CTD salinity offset and QC
flag to bottle values.
Oxygen action ID:6; CTD oxygen data good, setting CTD oxygen offset and QC flag
to bottle values.
Posted by svheuven@gmail.com on 2015-02-19 09:22:23 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View comment(s) (filtered by tco2 in subject)
Autogenerated comment - tCO2
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2_ATL_for_Carsten.xls / 2015-01-08): : Make 0. Cruise is region of strong
trends, and seems to fall approximately on the trend line.
Posted by svheuven@gmail.com on 2015-01-08 16:40:58 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View comment(s) (filtered by alkalinity in subject)
Autogenerated comment - alkalinity
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2_ATL_for_Carsten.xls / 2015-01-08): : make 7. Data are noisy. This makes
it match MT2003 (but might reduce any trend in the data). Note that most Hudson
TA data are of mediocre quality at best. There appear to be occasional
calibration breaks between the southern shelfbreak leg and the main Labrador Sea
leg, and data are generally exceedingly noisy.
Posted by svheuven@gmail.com on 2015-01-08 16:40:58 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View comment(s) (filtered by ph in subject)
18HU19960512 - ph
Changed adjustment to -999 as there are not measured pH, only calculated
Posted by avelo@iim.csic.es on 2015-11-04 10:50:06 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - phosphate
Automated update setting data quality flag from BAD to GOOD in order to retain
these non-QCed data in final product. SvH/GLODAPv2 / 2015-01-19)
Posted by svheuven@gmail.com on 2015-01-20 14:46:45 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - phosphate
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2_ATL_for_Carsten.xls / 2015-01-08): : maintain -888
Posted by svheuven@gmail.com on 2015-01-08 16:40:58 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View comment(s) (filtered by nitrate in subject)
Autogenerated comment - nitrate
Automated update setting data quality flag from BAD to GOOD in order to retain
these non-QCed data in final product. SvH/GLODAPv2 / 2015-01-19)
Posted by svheuven@gmail.com on 2015-01-20 14:46:45 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - nitrate
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2_ATL_for_Carsten.xls / 2015-01-08): : maintain -888
Posted by svheuven@gmail.com on 2015-01-08 16:40:58 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View comment(s) (filtered by phosphate in subject)
Autogenerated comment - phosphate
Automated update setting data quality flag from BAD to GOOD in order to retain
these non-QCed data in final product. SvH/GLODAPv2 / 2015-01-19)
Posted by svheuven@gmail.com on 2015-01-20 14:46:45 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - phosphate
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2_ATL_for_Carsten.xls / 2015-01-08): : maintain -888
Posted by svheuven@gmail.com on 2015-01-08 16:40:58 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View comment(s) (filtered by silicate in subject)
Autogenerated comment - silicate
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2_ATL_for_Carsten.xls / 2015-01-08): : make 1.00. Variable region, and I
don't see strong offsets with cruises in nearby years
Posted by svheuven@gmail.com on 2015-01-08 16:40:58 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View comment(s) (filtered by oxygen in subject)
Autogenerated CTD salinity and CTD oxygen update
Automated update! This overwrites adjustment values (and flags) of CTDoxy and
CTDsal with the values from BOTsal and BOToxy for every cruise, unless CTDsal
(or CTDoxy) is not present or bad.
Salinity action ID:5; CTD salinity data good, setting CTD salinity offset and QC
flag to bottle values.
Oxygen action ID:6; CTD oxygen data good, setting CTD oxygen offset and QC flag
to bottle values.
Posted by svheuven@gmail.com on 2015-02-19 09:22:23 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - oxygen
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2_ATL_for_Carsten.xls / 2015-01-08): : maintain 1.00. Fits on the LabSea
timeseries
Posted by svheuven@gmail.com on 2015-01-08 16:40:58 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
18HU19960512/oxygen: update slope+intercept
autogenerated: BOToxy is compatible with CALIBRATED CTDoxy
Posted by svheuven@gmail.com on 2014-12-18 16:52:39 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
18HU19960512/oxygen: init slope+intercept
autogenerated: using BOToxy because bad fit of CTDoxy.
Posted by svheuven@gmail.com on 2014-02-25 17:02:12 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View comment(s) (filtered by ctd_oxygen in subject)
Autogenerated CTD salinity and CTD oxygen update
Automated update! This overwrites adjustment values (and flags) of CTDoxy and
CTDsal with the values from BOTsal and BOToxy for every cruise, unless CTDsal
(or CTDoxy) is not present or bad.
Salinity action ID:5; CTD salinity data good, setting CTD salinity offset and QC
flag to bottle values.
Oxygen action ID:6; CTD oxygen data good, setting CTD oxygen offset and QC flag
to bottle values.
Posted by svheuven@gmail.com on 2015-02-19 09:22:23 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View 15 comment(s) (Lists all comments)
18HU19960512 - ph
Changed adjustment to -999 as there are not measured pH, only calculated
Posted by avelo@iim.csic.es on 2015-11-04 10:50:06 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated CTD salinity and CTD oxygen update
Automated update! This overwrites adjustment values (and flags) of CTDoxy and
CTDsal with the values from BOTsal and BOToxy for every cruise, unless CTDsal
(or CTDoxy) is not present or bad.
Salinity action ID:5; CTD salinity data good, setting CTD salinity offset and QC
flag to bottle values.
Oxygen action ID:6; CTD oxygen data good, setting CTD oxygen offset and QC flag
to bottle values.
Posted by svheuven@gmail.com on 2015-02-19 09:22:23 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - phosphate
Automated update setting data quality flag from BAD to GOOD in order to retain
these non-QCed data in final product. SvH/GLODAPv2 / 2015-01-19)
Posted by svheuven@gmail.com on 2015-01-20 14:46:45 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - nitrate
Automated update setting data quality flag from BAD to GOOD in order to retain
these non-QCed data in final product. SvH/GLODAPv2 / 2015-01-19)
Posted by svheuven@gmail.com on 2015-01-20 14:46:45 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - oxygen
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2_ATL_for_Carsten.xls / 2015-01-08): : maintain 1.00. Fits on the LabSea
timeseries
Posted by svheuven@gmail.com on 2015-01-08 16:40:58 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - silicate
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2_ATL_for_Carsten.xls / 2015-01-08): : make 1.00. Variable region, and I
don't see strong offsets with cruises in nearby years
Posted by svheuven@gmail.com on 2015-01-08 16:40:58 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - phosphate
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2_ATL_for_Carsten.xls / 2015-01-08): : maintain -888
Posted by svheuven@gmail.com on 2015-01-08 16:40:58 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - nitrate
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2_ATL_for_Carsten.xls / 2015-01-08): : maintain -888
Posted by svheuven@gmail.com on 2015-01-08 16:40:58 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - alkalinity
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2_ATL_for_Carsten.xls / 2015-01-08): : make 7. Data are noisy. This makes
it match MT2003 (but might reduce any trend in the data). Note that most Hudson
TA data are of mediocre quality at best. There appear to be occasional
calibration breaks between the southern shelfbreak leg and the main Labrador Sea
leg, and data are generally exceedingly noisy.
Posted by svheuven@gmail.com on 2015-01-08 16:40:58 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - tCO2
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2_ATL_for_Carsten.xls / 2015-01-08): : Make 0. Cruise is region of strong
trends, and seems to fall approximately on the trend line.
Posted by svheuven@gmail.com on 2015-01-08 16:40:58 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - salinity
Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2_ATL_for_Carsten.xls / 2015-01-08): : make 0. Cruise in highly variable
region. Matches quite well with its contemporaries. QC1. Some extreme flyers,
both high and low, below 1000m.
Posted by svheuven@gmail.com on 2015-01-08 16:40:58 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
18HU19960512/oxygen: update slope+intercept
autogenerated: BOToxy is compatible with CALIBRATED CTDoxy
Posted by svheuven@gmail.com on 2014-12-18 16:52:39 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
18HU19960512/salinity: update slope+intercept
autogenerated: BOTsal is compatible with unchanged CTDsal
Posted by svheuven@gmail.com on 2014-12-18 16:52:39 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
18HU19960512/oxygen: init slope+intercept
autogenerated: using BOToxy because bad fit of CTDoxy.
Posted by svheuven@gmail.com on 2014-02-25 17:02:12 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
18HU19960512/salinity: init slope+intercept
autogenerated: using BOTsal (few or no CTDsal or BOTsal>80%).
Posted by svheuven@gmail.com on 2014-02-25 17:02:12 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Hide comments