GLODAPv2 Adjustments

Stations:	[1-last]
The selected Calculated Carbon Parameter has been dismissed in October 2017! Legacy values will be exported as is and displayed in red with subscript "c", e.g. -0.123456_c! No data available? Insert -999 No suggestion for adjustment possible? Insert -888 To calibrate CTDsal use: CTDsal_calibrated = (CTDsal - CTDsal_intercept) / CTDsal_slope To calibrate CTDoxy use: CTDoxy_calibrated = (CTDoxy - CTDoxy_intercept) / CTDoxy_slope
Insert your commit message below explaining your change(s) before you save…
Salinity [+]
CTD-Sal. [+] slope/intercept - action [ID]	/ - #
TCO₂ [+]
Alkalinity [+]
pH [+]
pCO₂ [+]
Nitrate [x]
Phosphate [x]
Silicate [x]
Oxygen [x]
CTD-Oxyg. [x] slope/intercept - action [ID]	/ - #
CFC12 [x]
CFC11 [x]
CFC113 [x]
CCl4 [x]
C13 [+]
SF6 [x]

Cruise Info

Annotations for this cruise:

View 0 annotation(s) (Lists all annotations)

Files for Adjustment Plot files re. Cruise:

Filename:	Comment:	Action…
RC_SO.png	[autogenerated from RC_Toste/adjustments!]	View

Data files re. Cruise: - no files! -

Plot/Data files re. Parameter(s) (select parameter on left side to view!):
cruise:1

Plot files re. Cluster: - no files! -

Comments re. this cruise in GLODAPv2

View 20 comment(s) (Lists all comments)

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:6; CTD salinity data good, setting CTD salinity offset and QC
flag to bottle values.
Oxygen action ID:5; 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:19 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

Autogenerated comment - alkalinity

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:42 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

35MF20040103/oxygen: update slope+intercept

autogenerated: BOToxy is compatible with unchanged CTDoxy

Posted by svheuven@gmail.com on 2014-12-18 16:52:45 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

35MF20040103/salinity: update slope+intercept

autogenerated: BOTsal is compatible with CALIBRATED CTDsal

Posted by svheuven@gmail.com on 2014-12-18 16:52:45 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

35MF20040103 - salinity

Manually set CTDsal calibration for this cruise, to avoid CTDsal data being
lost.

Posted by svheuven@gmail.com on 2014-12-15 21:13:24 UTC for data product: CARINA, 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 Adjustment IND and PAC_SvH_20140611.xlsx): : maintain

Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, 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 Adjustment IND and PAC_SvH_20140611.xlsx): : maintain. I cannot solve
these 35MF cruises for Silicate, and by this stage will happily just accept
anything Clair suggested for them.

Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, 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 Adjustment IND and PAC_SvH_20140611.xlsx): : maintain

Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, 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 Adjustment IND and PAC_SvH_20140611.xlsx): : Maintain. The inversion
result comes from the only deep station, which is offset high. All shallower
data seem to be fine(-ish)...

Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, 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 Adjustment IND and PAC_SvH_20140611.xlsx): : set to -888

Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, 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 Adjustment IND and PAC_SvH_20140611.xlsx): : maintain

Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, 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 Adjustment IND and PAC_SvH_20140611.xlsx): : maintain

Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

35MF20040103/oxygen: init slope+intercept

autogenerated: using BOToxy because bad fit of CTDoxy.

Posted by svheuven@gmail.com on 2014-02-25 17:02:15 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

35MF20040103/salinity: init slope+intercept

autogenerated: using BOTsal because bad fit of CTDsal

Posted by svheuven@gmail.com on 2014-02-25 17:02:15 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

35MF20040103 - oxygen

OISO11: only one deep profiles (at 56°S).
INTERNAL OISO CONSISTENCY:
6 cross overs were analyzed (all found at 56°S). The average of all cross overs
is 0.997 (+/-0.028).
Only 1 cross over shows no significant differences (<1%) and involve a cruise
that is thought to have no offset in oxygen, whereas 3 other cross overs also
involving cruises that are thought to have no offset in oxygen show a ratio
around 0.99. When the offsets suggested for the other cruises are taken into
account the average of all cross overs is 0.988 (+/-0.005). This suggests that
an adjustment of 1.01 could be required.
OTHER CROSS OVERS:
The cross over with the cruise INDIGO3 shows a ratio of 0.999 (+/-0.005), which
disagree with the analysis above. However, very few measurements are compared
here. The analysis of CTD oxygen profiles at 30°S and 56°S supports the
adjustment suggested above.
CONCLUSION:
Based on the regional analyses above I suggest an adjustment of 1.01 for oxygen.
___________________
Paris, August 2008
Claire Lo Monaco

Posted by claire.lomonaco@locean.upmc.fr on 2008-10-21 14:28:55 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

35MF20040103 - silicate

OISO11: two deep profiles (at 35°S and 56°S) + 4 profiles down to 2000m
(30°S-50°S).
INTERNAL OISO CONSISTENCY:
6 cross overs were analyzed (all found at 56°S). The average of all cross overs
is 1.076 (+/-0.040).
1 reliable cross over which involves a cruise that is thought to have no offset
in silicate suggests an offset of 1.055 (+/-0.011). When the offsets suggested
for the other cruises as well as the suggested natural variability are taken
into account the average of all cross overs is 1.054 (+/-0.002). This suggests
that an adjustment of 0.95 could be required.
OTHER CROSS OVERS:
The cross overs with cruises INDIGO1 (30°S) and 74DI19940219 (30°S) show ratios
of 1.068 (+/-0.015) and 1.078 (+/-0.014), which is in good agreement with the
analysis above (given that cruises INDIGO1 and 74DI19940219 are thought to have
slightly low silicate).
The cross over with the cruise INDIGO3 (56°S) shows a ratio of 0.986 (+/-0.015),
but INDIGO3 is thought to have high silicate values. When the suggested offset
is taken into account as well as the suggested natural variability, a good
agreement is found with the OISO analysis above (1.06).
CONCLUSION
All cross overs found at 30°S and 56°S agree to suggest an offset around 1.05.
Based on this I suggest an adjustment of 0.95 for silicate.
___________________
Paris, August 2008
Claire Lo Monaco

Posted by claire.lomonaco@locean.upmc.fr on 2008-10-21 14:28:11 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

35MF20040103 - nitrate

OISO11: two deep profiles (at 35°S and 56°S) + 4 profiles down to 2000m
(30°S-50°S).
INTERNAL OISO CONSISTENCY:
6 cross overs were analyzed (all found at 56°S). The average of all cross overs
is 1.129 (+/-0.039).
All cross overs show significant differences (>2%). Only one of them involves a
cruise that is thought to have no offset in nitrate and appears reliable (1.134
+/-0.008 with 35MF20010103). When the natural changes in nitrate suggested for
the other cruises are taken into account, the average of all cross overs is
1.132 (+/-0.006). This suggests that an adjustment could be required, but it is
not warranted since Antarctic deep waters are entitled to natural variability,
which could play a role in the observed differences (all cross overs are found
at 56°S).
OTHER CROSS OVERS:
The cross overs with cruises GEOSECS_INDIAN (30°S) and INDIGO1 (30°S) show no
significant differences (<2%), while the cross over with the cruise 74DI19940219
(30°S) shows a small offset (1.025 +/-0.008). This is different from the
analysis above at 56°S, which support the idea that natural variability would
also play a role in the observed differences.
The cross overs with the cruise INDIGO3 found at 56°S show a ratio of 1.174
(+/-0.030), but INDIGO3 is thought to have low nitrate values. When the
suggested offset is taken into account as well as the suggested natural
variability, it translates into an offset of 1.134, which supports the analysis
above.
CONCLUSION:
The different results obtained at 30°S and 56°S are probably due to natural
changes that would have operate in Antarctic deep waters as suggested by the
analysis of other parameters.
Based on this I suggest no adjustment for nitrate.
___________________
Paris, August 2008
Claire Lo Monaco

Posted by claire.lomonaco@locean.upmc.fr on 2008-10-21 14:27:33 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

35MF20040103 - alkalinity

OISO11: two deep profiles (at 35°S and 56°S) + 4 profiles down to 2000m
(30°S-50°S).
INTERNAL OISO CONSISTENCY:
5 cross overs were analyzed (all found at 56°S). The average of all cross overs
is -3.2 (+/-3.5) umol/kg.
All cross overs show no significant differences (<5 umol/kg) and involve cruises
that are thought to have no offset in alkalinity. This suggests that no
adjustment would be required.
Note that the large scatter around the mean is probably due to natural
variability. And indeed, if a decrease in alkalinity of 1 umol/kg/yr is assumed
(as suggested in this study) the scatter and the mean are reduced (+0.7 +/-2.2
umol/kg).
OTHER CROSS OVERS:
The cross overs with cruises GEOSECS_INDIAN (30°S) shows an offset of -13 (+/-4)
umol/kg, which is not coherent with the previous results.
The cross overs with cruises INDIGO1 (30°S) and INDIGO3 (56°S) show differences
of -16 (+/-4) umol/kg and -17 (+/-4) umol/kg, respectively, but INDIGO1 is known
to have high alkalinity values by about 16 umol/kg and INDIGO3 would have no
offset but alkalinity might have decreased by about 17 umol/kg. If this is taken
into account the offsets with INDIGO cruises translate into no significant
differences, which supports the analysis above.
CONCLUSION:
Based on the regional analyses above I suggest no adjustment for alkalinity.
___________________
Paris, August 2008
Claire Lo Monaco

Posted by claire.lomonaco@locean.upmc.fr on 2008-10-08 23:59:18 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

35MF20040103 - tco2

OISO11: two deep profiles (at 35°S and 56°S) + 4 profiles down to 2000m
(30°S-50°S).
INTERNAL OISO CONSISTENCY:
6 cross overs were analyzed (all found at 56°S). The average of all cross overs
is -1.0 (+/-3.5) umol/kg.
All cross overs but 1 show no significant differences (<4 umol/kg), and 4 of
them involve cruises that are thought to have no offset in TCO2. When the
offsets suggested for the other cruises are taken into account the average of
all cross overs is -2.4 (+/-1.7) umol/kg. This suggests that no adjustment would
be required.
OTHER CROSS OVERS:
The cross overs with cruises GEOSECS_INDIAN, INDIGO1 and INDIGO3 (found around
30°S and 56°S) show offsets ranging from -9.1 to -28.9 umol/kg, but all 3
cruises are known to have high TCO2 values. When the suggested offsets are taken
into account the average of the 3 cross overs is -4.6 (+/-1.2) umol/kg. This
suggests that a small adjustment could be required.
CONCLUSION:
Comparison with the other OISO cruises suggests that no adjustment would be
required, whereas the comparison with historical cruises suggests that a small
adjustment could be required (about +4 umol/kg). However, lowest confidence is
given to latter result, due to the time interval between historical cruises and
OISO11.
Based on this I suggest no adjustment for TCO2.
___________________
Paris, August 2008
Claire Lo Monaco

Posted by claire.lomonaco@locean.upmc.fr on 2008-10-08 23:58:44 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

35MF20040103 - salinity

OISO11: two deep profiles (at 35°S and 56°S) + 4 profiles down to 2000m
(30°S-50°S).
INTERNAL OISO CONSISTENCY:
6 cross overs were analyzed (all found at 56°S). The average of all cross overs
is +26.9 (+/-5.3) ppm.
4 cross overs show offsets ranging from +23 to +28 ppm and involve cruises that
are thought to have no significant offset in salinity. When the offsets
suggested for the other cruises are taken into account the average of all cross
overs is +27.0 (+/-2) ppm. This suggests that an adjustment could be required.
OTHER CROSS OVERS:
The other cross overs with cruises 74DI19940219, GEOSECS_INDIAN, INDIGO1 and
INDIGO3 (found around 30°S and 56°S) indicate a mean offset of +22.3 (+/-2.6)
ppm. This suggests that an adjustment could be required.
CONCLUSION:
The comparison among OISO cruises and the comparison with other cruises agree,
but slightly different numbers are suggested: -27 ppm and -22 ppm respectively.
The latter result is preferred in order to warrant consistency between OISO and
the other cruises. Moreover, it is based on cross overs found north and south of
the Polar Front, whereas the analysis with other OISO cruises only compares
profiles south of the Polar Front (56°S).
Based on this I suggest an adjustment of -22 ppm for salinity.
___________________
Paris, August 2008
Claire Lo Monaco

Posted by claire.lomonaco@locean.upmc.fr on 2008-10-08 23:58:15 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

Hide comments

View other postings and files re. this adjustment

ReadMe file(s) for this cruise

View 1 ReadMe(s) (Lists all ReadMes)

Files and Comments for salinity

Files

Plot files re. Salinity
[+]: - no files! -

Data files re. Salinity
[+]: - 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:6; CTD salinity data good, setting CTD salinity offset and QC
flag to bottle values.
Oxygen action ID:5; 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:19 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

35MF20040103/salinity: update slope+intercept

autogenerated: BOTsal is compatible with CALIBRATED CTDsal

Posted by svheuven@gmail.com on 2014-12-18 16:52:45 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

35MF20040103 - salinity

Manually set CTDsal calibration for this cruise, to avoid CTDsal data being
lost.

Posted by svheuven@gmail.com on 2014-12-15 21:13:24 UTC for data product: CARINA, 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 Adjustment IND and PAC_SvH_20140611.xlsx): : maintain

Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

35MF20040103/salinity: init slope+intercept

autogenerated: using BOTsal because bad fit of CTDsal

Posted by svheuven@gmail.com on 2014-02-25 17:02:15 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

35MF20040103 - salinity

OISO11: two deep profiles (at 35°S and 56°S) + 4 profiles down to 2000m
(30°S-50°S).
INTERNAL OISO CONSISTENCY:
6 cross overs were analyzed (all found at 56°S). The average of all cross overs
is +26.9 (+/-5.3) ppm.
4 cross overs show offsets ranging from +23 to +28 ppm and involve cruises that
are thought to have no significant offset in salinity. When the offsets
suggested for the other cruises are taken into account the average of all cross
overs is +27.0 (+/-2) ppm. This suggests that an adjustment could be required.
OTHER CROSS OVERS:
The other cross overs with cruises 74DI19940219, GEOSECS_INDIAN, INDIGO1 and
INDIGO3 (found around 30°S and 56°S) indicate a mean offset of +22.3 (+/-2.6)
ppm. This suggests that an adjustment could be required.
CONCLUSION:
The comparison among OISO cruises and the comparison with other cruises agree,
but slightly different numbers are suggested: -27 ppm and -22 ppm respectively.
The latter result is preferred in order to warrant consistency between OISO and
the other cruises. Moreover, it is based on cross overs found north and south of
the Polar Front, whereas the analysis with other OISO cruises only compares
profiles south of the Polar Front (56°S).
Based on this I suggest an adjustment of -22 ppm for salinity.
___________________
Paris, August 2008
Claire Lo Monaco

Posted by claire.lomonaco@locean.upmc.fr on 2008-10-08 23:58:15 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

Hide comments

Files and Comments for ctd_salinity

Files

Plot files re. CTD-Sal. [+]
adj. - slope/intercept - action [ID]: - no files! -

Data files re. CTD-Sal. [+]
adj. - slope/intercept - action [ID]: - no files! -

View comment(s) (filtered by ctd_salinity in subject)

Files and Comments for tco2

Files

Plot files re. TCO₂
[+]: - no files! -

Data files re. TCO₂
[+]: - no files! -

View comment(s) (filtered by tco2 in subject)

Files and Comments for alkalinity

Files

Plot files re. Alkalinity
[+]: - no files! -

Data files re. Alkalinity
[+]: - no files! -

View comment(s) (filtered by alkalinity in subject)

Autogenerated comment - alkalinity

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:42 UTC for data product: CARINA, 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 Adjustment IND and PAC_SvH_20140611.xlsx): : set to -888

Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

35MF20040103 - alkalinity

OISO11: two deep profiles (at 35°S and 56°S) + 4 profiles down to 2000m
(30°S-50°S).
INTERNAL OISO CONSISTENCY:
5 cross overs were analyzed (all found at 56°S). The average of all cross overs
is -3.2 (+/-3.5) umol/kg.
All cross overs show no significant differences (<5 umol/kg) and involve cruises
that are thought to have no offset in alkalinity. This suggests that no
adjustment would be required.
Note that the large scatter around the mean is probably due to natural
variability. And indeed, if a decrease in alkalinity of 1 umol/kg/yr is assumed
(as suggested in this study) the scatter and the mean are reduced (+0.7 +/-2.2
umol/kg).
OTHER CROSS OVERS:
The cross overs with cruises GEOSECS_INDIAN (30°S) shows an offset of -13 (+/-4)
umol/kg, which is not coherent with the previous results.
The cross overs with cruises INDIGO1 (30°S) and INDIGO3 (56°S) show differences
of -16 (+/-4) umol/kg and -17 (+/-4) umol/kg, respectively, but INDIGO1 is known
to have high alkalinity values by about 16 umol/kg and INDIGO3 would have no
offset but alkalinity might have decreased by about 17 umol/kg. If this is taken
into account the offsets with INDIGO cruises translate into no significant
differences, which supports the analysis above.
CONCLUSION:
Based on the regional analyses above I suggest no adjustment for alkalinity.
___________________
Paris, August 2008
Claire Lo Monaco

Posted by claire.lomonaco@locean.upmc.fr on 2008-10-08 23:59:18 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

Hide comments

Files and Comments for ph

Files

Plot files re. pH
[+]: - no files! -

Data files re. pH
[+]: - no files! -

View comment(s) (filtered by ph in subject)

Files and Comments for pco2

Files

Plot files re. pCO₂
[+]: - no files! -

Data files re. pCO₂
[+]: - no files! -

View comment(s) (filtered by pco2 in subject)

Files and Comments for nitrate

Files

Plot files re. Nitrate
[x]: - no files! -

Data files re. Nitrate
[x]: - no files! -

View comment(s) (filtered by nitrate in subject)

Autogenerated comment - nitrate

Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2 Adjustment IND and PAC_SvH_20140611.xlsx): : Maintain. The inversion
result comes from the only deep station, which is offset high. All shallower
data seem to be fine(-ish)...

Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

35MF20040103 - nitrate

OISO11: two deep profiles (at 35°S and 56°S) + 4 profiles down to 2000m
(30°S-50°S).
INTERNAL OISO CONSISTENCY:
6 cross overs were analyzed (all found at 56°S). The average of all cross overs
is 1.129 (+/-0.039).
All cross overs show significant differences (>2%). Only one of them involves a
cruise that is thought to have no offset in nitrate and appears reliable (1.134
+/-0.008 with 35MF20010103). When the natural changes in nitrate suggested for
the other cruises are taken into account, the average of all cross overs is
1.132 (+/-0.006). This suggests that an adjustment could be required, but it is
not warranted since Antarctic deep waters are entitled to natural variability,
which could play a role in the observed differences (all cross overs are found
at 56°S).
OTHER CROSS OVERS:
The cross overs with cruises GEOSECS_INDIAN (30°S) and INDIGO1 (30°S) show no
significant differences (<2%), while the cross over with the cruise 74DI19940219
(30°S) shows a small offset (1.025 +/-0.008). This is different from the
analysis above at 56°S, which support the idea that natural variability would
also play a role in the observed differences.
The cross overs with the cruise INDIGO3 found at 56°S show a ratio of 1.174
(+/-0.030), but INDIGO3 is thought to have low nitrate values. When the
suggested offset is taken into account as well as the suggested natural
variability, it translates into an offset of 1.134, which supports the analysis
above.
CONCLUSION:
The different results obtained at 30°S and 56°S are probably due to natural
changes that would have operate in Antarctic deep waters as suggested by the
analysis of other parameters.
Based on this I suggest no adjustment for nitrate.
___________________
Paris, August 2008
Claire Lo Monaco

Posted by claire.lomonaco@locean.upmc.fr on 2008-10-21 14:27:33 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

Hide comments

Files and Comments for phosphate

Files

Plot files re. Phosphate
[x]: - no files! -

Data files re. Phosphate
[x]: - no files! -

View comment(s) (filtered by phosphate in subject)

Files and Comments for silicate

Files

Plot files re. Silicate
[x]: - no files! -

Data files re. Silicate
[x]: - no files! -

View comment(s) (filtered by silicate in subject)

Autogenerated comment - silicate

Auto-uploaded comment from GLODAPv2 assessment by Steven van Heuven (src:
GLODAPv2 Adjustment IND and PAC_SvH_20140611.xlsx): : maintain. I cannot solve
these 35MF cruises for Silicate, and by this stage will happily just accept
anything Clair suggested for them.

Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

35MF20040103 - silicate

OISO11: two deep profiles (at 35°S and 56°S) + 4 profiles down to 2000m
(30°S-50°S).
INTERNAL OISO CONSISTENCY:
6 cross overs were analyzed (all found at 56°S). The average of all cross overs
is 1.076 (+/-0.040).
1 reliable cross over which involves a cruise that is thought to have no offset
in silicate suggests an offset of 1.055 (+/-0.011). When the offsets suggested
for the other cruises as well as the suggested natural variability are taken
into account the average of all cross overs is 1.054 (+/-0.002). This suggests
that an adjustment of 0.95 could be required.
OTHER CROSS OVERS:
The cross overs with cruises INDIGO1 (30°S) and 74DI19940219 (30°S) show ratios
of 1.068 (+/-0.015) and 1.078 (+/-0.014), which is in good agreement with the
analysis above (given that cruises INDIGO1 and 74DI19940219 are thought to have
slightly low silicate).
The cross over with the cruise INDIGO3 (56°S) shows a ratio of 0.986 (+/-0.015),
but INDIGO3 is thought to have high silicate values. When the suggested offset
is taken into account as well as the suggested natural variability, a good
agreement is found with the OISO analysis above (1.06).
CONCLUSION
All cross overs found at 30°S and 56°S agree to suggest an offset around 1.05.
Based on this I suggest an adjustment of 0.95 for silicate.
___________________
Paris, August 2008
Claire Lo Monaco

Posted by claire.lomonaco@locean.upmc.fr on 2008-10-21 14:28:11 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

Hide comments

Files and Comments for oxygen

Files

Plot files re. Oxygen
[x]: - no files! -

Data files re. Oxygen
[x]: - no files! -

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:6; CTD salinity data good, setting CTD salinity offset and QC
flag to bottle values.
Oxygen action ID:5; 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:19 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

35MF20040103/oxygen: update slope+intercept

autogenerated: BOToxy is compatible with unchanged CTDoxy

Posted by svheuven@gmail.com on 2014-12-18 16:52:45 UTC for data product: CARINA, 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 Adjustment IND and PAC_SvH_20140611.xlsx): : maintain

Posted by svheuven@gmail.com on 2014-06-16 15:50:37 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

35MF20040103/oxygen: init slope+intercept

autogenerated: using BOToxy because bad fit of CTDoxy.

Posted by svheuven@gmail.com on 2014-02-25 17:02:15 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

35MF20040103 - oxygen

OISO11: only one deep profiles (at 56°S).
INTERNAL OISO CONSISTENCY:
6 cross overs were analyzed (all found at 56°S). The average of all cross overs
is 0.997 (+/-0.028).
Only 1 cross over shows no significant differences (<1%) and involve a cruise
that is thought to have no offset in oxygen, whereas 3 other cross overs also
involving cruises that are thought to have no offset in oxygen show a ratio
around 0.99. When the offsets suggested for the other cruises are taken into
account the average of all cross overs is 0.988 (+/-0.005). This suggests that
an adjustment of 1.01 could be required.
OTHER CROSS OVERS:
The cross over with the cruise INDIGO3 shows a ratio of 0.999 (+/-0.005), which
disagree with the analysis above. However, very few measurements are compared
here. The analysis of CTD oxygen profiles at 30°S and 56°S supports the
adjustment suggested above.
CONCLUSION:
Based on the regional analyses above I suggest an adjustment of 1.01 for oxygen.
___________________
Paris, August 2008
Claire Lo Monaco

Posted by claire.lomonaco@locean.upmc.fr on 2008-10-21 14:28:55 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

Hide comments

Files and Comments for ctd_oxygen

Files

Plot files re. CTD-Oxyg. [x]
adj. - slope/intercept - action [ID]: - no files! -

Data files re. CTD-Oxyg. [x]
adj. - slope/intercept - action [ID]: - no files! -

Dataproduct: GLODAPv2 :: Adjustments

Cruise: 35MF20040103 (dataset:CARINA) Data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023

Please wait while loading list of related files…

Autogenerated CTD salinity and CTD oxygen update

Autogenerated comment - alkalinity

35MF20040103/oxygen: update slope+intercept

35MF20040103/salinity: update slope+intercept

35MF20040103 - salinity

Autogenerated comment - oxygen

Autogenerated comment - silicate

Autogenerated comment - phosphate

Autogenerated comment - nitrate

Autogenerated comment - alkalinity

Autogenerated comment - tCO2

Autogenerated comment - salinity

35MF20040103/oxygen: init slope+intercept

35MF20040103/salinity: init slope+intercept

35MF20040103 - oxygen

35MF20040103 - silicate

35MF20040103 - nitrate

35MF20040103 - alkalinity

35MF20040103 - tco2

35MF20040103 - salinity

35MF20040103 - 2008-06-17 14:28:38 - version: 0Posted on 2008-06-17 14:28:38 - last updated on 2008-06-17 14:28:38 as version number 0

Autogenerated CTD salinity and CTD oxygen update

35MF20040103/salinity: update slope+intercept

35MF20040103 - salinity

Autogenerated comment - salinity

35MF20040103/salinity: init slope+intercept

35MF20040103 - salinity

Autogenerated CTD salinity and CTD oxygen update

Autogenerated comment - tCO2

35MF20040103 - tco2

Autogenerated comment - alkalinity

Autogenerated comment - alkalinity

35MF20040103 - alkalinity

Autogenerated comment - phosphate

Autogenerated comment - nitrate

35MF20040103 - nitrate

Autogenerated comment - phosphate

Autogenerated comment - silicate

35MF20040103 - silicate

Autogenerated CTD salinity and CTD oxygen update

35MF20040103/oxygen: update slope+intercept

Autogenerated comment - oxygen

35MF20040103/oxygen: init slope+intercept

35MF20040103 - oxygen

Autogenerated CTD salinity and CTD oxygen update