Cruise: 35MF19980818 (dataset:CARINA) Data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Synonyms (including errata!) for this cruise: OISO-2; 35MF19980818; OISO-2;
IMPORTANT information for GLODAP Reference Group Editors: This adjustment is a published version for GLODAPv2!
Please wait while loading list of related files
Filename: | Comment: | Action | |
---|---|---|---|
RC_SO.png | [autogenerated from RC_Toste/adjustments!] |
View | |
manualXovers.png | [autogenerated from manual_xovers/adjustments!] |
View |
- no files! -
Plot/Data files re. Parameter(s) (select parameter on left side to view!):
cruise:2
- no files! -
View 1 ReadMe(s) (Lists all ReadMes)
35MF19980818 - 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
5/1/07 Initialized README file
Data from C. Lo Monaco 1/15/07
Ship and cruise designation: Marion Dufresne; 35M199808, OISO-02
Cruise dates: 8-18-9/9/1998
EXPOCODE: 35MF19980818
14 stations
Chief Scientist: N. Metzl
Hydro: Who - ; Status - final; S Plus - up to date
Notes: only enough salinity to calibrate CTD
Nuts/O2: Who - ; Status - final; S Plus - up to date
Notes: No phosphate
TCO2: Who - C.LoMonaco; Status - final; S Plus - up to date
Notes: CRM?
TA: Who - C.LoMonaco; Status - final; S Plus - up to date
Notes: CRM?
fCO2: Who - ; Status - not measured; S Plus -
Notes: Underway only
pH25: Who - ; Status - not measured; S Plus -
Notes:
CFC: Who - ; Status - not measured; S Plus -
Notes:
C-14: Who - ; Status - not measured; S Plus -
Notes:
C-13: Who - ; Status - unknown; S Plus -
Notes: no data in file
H-3/He-3: Who - ; Status - ; S Plus -
Notes:
Other: O18 - no data in file
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: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:25 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19980818/salinity: update slope+intercept
autogenerated: BOTsal is compatible with unchanged CTDsal
Posted by svheuven@gmail.com on 2014-12-18 16:52:44 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
35MF19980818/salinity: init slope+intercept
autogenerated: using mean of BOTsal and UNCHANGED 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
35MF19980818 - salinity
OISO2: only one deep profile (at 30°S).
INTERNAL OISO CONSISTENCY:
5 cross overs were analyzed. The average of all cross overs is -1.9 (+/-4.2)
ppm.
4 cross overs show no significant differences (<5 ppm) and involve cruises that
are thought to have no significant offset in salinity. When the offset suggested
for the other cruise is taken into account the average of all cross overs is
-0.1 (+/-1.0) ppm. This suggests that no adjustment would be required.
OTHER CROSS OVERS:
The cross over with cruise INDIGO1 shows an offset of -1 (+/-8) ppm, which
supports no adjustment.
CONCLUSION:
Based on the regional analyses above I suggest no adjustment for salinity.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-08 23:42:45 UTC for data product: CARINA, 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: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:25 UTC for data product: CARINA, 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 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
35MF19980818 - tco2
OISO2: only one deep profile (at 30°S).
INTERNAL OISO CONSISTENCY:
5 cross overs were analyzed. The average of all cross overs is +5.4 (+/-2.9)
umol/kg.
Only one cross overs shows no significant differences (<4 umol/kg). The 4 cross
overs involving cruises that are thought to have no offset in TCO2 show offsets
ranging from +1.7 to +6.7 umol/kg. When the offset suggested for the other
cruise is taken into account the average of all cross overs is +4.1 (+/-1.9)
umol/kg. This suggests that an adjustment of -4 umol/kg could be required.
OTHER CROSS OVERS:
The cross over with cruise INDIGO1 shows a difference of -5.2 (+/-2.7) umol/kg,
but since INDIGO1 is known to have high TCO2 values by about 10 umol/kg
(according to this study and GLODAP), it translates into an offset of +5 mol/kg.
This supports the result of the analysis above.
CONCLUSION:
Based on the regional analyses above I suggest an adjustment of -4.0 umol/kg for
TCO2.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-08 23:43:11 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
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:46 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
35MF19980818 - alkalinity
OISO2: only one deep profile (at 30°S).
INTERNAL OISO CONSISTENCY:
4 cross overs were analyzed. The average of all cross overs is +9.1 (+/-1.4)
umol/kg.
All cross overs show significant differences ranging from +7.9 to +10.8, and all
involve cruises that are thought to have no offset in alkalinity. This suggests
that an adjustment of -9 umol/kg could be required.
OTHER CROSS OVERS:
The cross over with the cruise INDIGO1 shows a difference of -7.8 (+/-1.9)
umol/kg, but since INDIGO1 is known to have high alkalinity values by about 16
umol/kg (according to this study), it translates into an offset of +8 mol/kg.
This supports the result of the analysis above.
CONCLUSION:
Based on the regional analyses above I suggest an adjustment of -9 umol/kg for
alkalinity.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-08 23:43:46 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View comment(s) (filtered by ph in subject)
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
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
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
35MF19980818 - nitrate
OISO2: only one deep profile (at 30°S).
INTERNAL OISO CONSISTENCY:
4 cross overs were analyzed. The average of all cross overs is 0.998 (+/-0.040).
2 cross overs show no significant differences (<2%) and involve cruises that are
thought to have no offset in nitrate. When the offsets suggested for the other
cruises are taken into account the average of all cross overs is 0.991
(+/-0.005). This suggests that no adjustment would be required.
OTHER CROSS OVERS:
The cross over with the cruise INDIGO1 shows a ratio of 1.003 (+/-0.013) and
since INDIGO1 is thought to have no offset in nitrate, this supports the result
of the analysis above.
CONCLUSION:
Based on the regional analyses above I suggest no adjustment for nitrate.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-21 13:06:29 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View comment(s) (filtered by phosphate in subject)
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
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
35MF19980818 - silicate
OISO2: only one deep profile (at 30°S).
INTERNAL OISO CONSISTENCY:
5 cross overs were analyzed. The average of all cross overs is 0.962 (+/-0.036).
Only 2 cross overs show no significant differences (<2%), but they involve
cruises that are thought to have offsets in silicate. When the suggested offsets
are taken into account, the average of all cross overs is 0.960 (+/-0.004). This
suggests that an adjustment of 1.04 could be required.
OTHER CROSS OVERS:
The cross over with the cruise INDIGO1 shows a ratio of 0.975 (+/-0.009), which
is in good agreement with the analysis above (given that INDIGO1 is thought to
have slightly low silicate).
CONCLUSION:
Based on the regional analyses above I suggest an adjustment of 1.04 for
silicate.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-21 13:06:47 UTC for data product: CARINA, 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: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:25 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - oxygen
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:46 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19980818/oxygen: update slope+intercept
autogenerated: BOToxy is compatible with unchanged CTDoxy
Posted by svheuven@gmail.com on 2014-12-18 16:52:44 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): : 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
35MF19980818/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
35MF19980818 - oxygen
OISO2: only one deep measurement (at 30°S).
CROSS OVERS ANALYSIS:
Only 1 deep oxygen measurement was collected at 30°S during each OISO cruise
that tends to suggest that no (or small) adjustment would be required (1.01 or
less). This results is supported by the analysis of CTD oxygen profiles showing
no significant differences.
CONCLUSION:
Based on the regional analysis above I suggest no adjustment for oxygen.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-21 13:07:11 UTC for data product: CARINA, 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: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:25 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
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:5; 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:25 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Autogenerated comment - oxygen
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:46 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:46 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19980818/oxygen: update slope+intercept
autogenerated: BOToxy is compatible with unchanged CTDoxy
Posted by svheuven@gmail.com on 2014-12-18 16:52:44 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19980818/salinity: update slope+intercept
autogenerated: BOTsal is compatible with unchanged CTDsal
Posted by svheuven@gmail.com on 2014-12-18 16:52:44 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): : 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 - 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
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
35MF19980818/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
35MF19980818/salinity: init slope+intercept
autogenerated: using mean of BOTsal and UNCHANGED 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
35MF19980818 - oxygen
OISO2: only one deep measurement (at 30°S).
CROSS OVERS ANALYSIS:
Only 1 deep oxygen measurement was collected at 30°S during each OISO cruise
that tends to suggest that no (or small) adjustment would be required (1.01 or
less). This results is supported by the analysis of CTD oxygen profiles showing
no significant differences.
CONCLUSION:
Based on the regional analysis above I suggest no adjustment for oxygen.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-21 13:07:11 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19980818 - silicate
OISO2: only one deep profile (at 30°S).
INTERNAL OISO CONSISTENCY:
5 cross overs were analyzed. The average of all cross overs is 0.962 (+/-0.036).
Only 2 cross overs show no significant differences (<2%), but they involve
cruises that are thought to have offsets in silicate. When the suggested offsets
are taken into account, the average of all cross overs is 0.960 (+/-0.004). This
suggests that an adjustment of 1.04 could be required.
OTHER CROSS OVERS:
The cross over with the cruise INDIGO1 shows a ratio of 0.975 (+/-0.009), which
is in good agreement with the analysis above (given that INDIGO1 is thought to
have slightly low silicate).
CONCLUSION:
Based on the regional analyses above I suggest an adjustment of 1.04 for
silicate.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-21 13:06:47 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19980818 - nitrate
OISO2: only one deep profile (at 30°S).
INTERNAL OISO CONSISTENCY:
4 cross overs were analyzed. The average of all cross overs is 0.998 (+/-0.040).
2 cross overs show no significant differences (<2%) and involve cruises that are
thought to have no offset in nitrate. When the offsets suggested for the other
cruises are taken into account the average of all cross overs is 0.991
(+/-0.005). This suggests that no adjustment would be required.
OTHER CROSS OVERS:
The cross over with the cruise INDIGO1 shows a ratio of 1.003 (+/-0.013) and
since INDIGO1 is thought to have no offset in nitrate, this supports the result
of the analysis above.
CONCLUSION:
Based on the regional analyses above I suggest no adjustment for nitrate.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-21 13:06:29 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19980818 - alkalinity
OISO2: only one deep profile (at 30°S).
INTERNAL OISO CONSISTENCY:
4 cross overs were analyzed. The average of all cross overs is +9.1 (+/-1.4)
umol/kg.
All cross overs show significant differences ranging from +7.9 to +10.8, and all
involve cruises that are thought to have no offset in alkalinity. This suggests
that an adjustment of -9 umol/kg could be required.
OTHER CROSS OVERS:
The cross over with the cruise INDIGO1 shows a difference of -7.8 (+/-1.9)
umol/kg, but since INDIGO1 is known to have high alkalinity values by about 16
umol/kg (according to this study), it translates into an offset of +8 mol/kg.
This supports the result of the analysis above.
CONCLUSION:
Based on the regional analyses above I suggest an adjustment of -9 umol/kg for
alkalinity.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-08 23:43:46 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19980818 - tco2
OISO2: only one deep profile (at 30°S).
INTERNAL OISO CONSISTENCY:
5 cross overs were analyzed. The average of all cross overs is +5.4 (+/-2.9)
umol/kg.
Only one cross overs shows no significant differences (<4 umol/kg). The 4 cross
overs involving cruises that are thought to have no offset in TCO2 show offsets
ranging from +1.7 to +6.7 umol/kg. When the offset suggested for the other
cruise is taken into account the average of all cross overs is +4.1 (+/-1.9)
umol/kg. This suggests that an adjustment of -4 umol/kg could be required.
OTHER CROSS OVERS:
The cross over with cruise INDIGO1 shows a difference of -5.2 (+/-2.7) umol/kg,
but since INDIGO1 is known to have high TCO2 values by about 10 umol/kg
(according to this study and GLODAP), it translates into an offset of +5 mol/kg.
This supports the result of the analysis above.
CONCLUSION:
Based on the regional analyses above I suggest an adjustment of -4.0 umol/kg for
TCO2.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-08 23:43:11 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
35MF19980818 - salinity
OISO2: only one deep profile (at 30°S).
INTERNAL OISO CONSISTENCY:
5 cross overs were analyzed. The average of all cross overs is -1.9 (+/-4.2)
ppm.
4 cross overs show no significant differences (<5 ppm) and involve cruises that
are thought to have no significant offset in salinity. When the offset suggested
for the other cruise is taken into account the average of all cross overs is
-0.1 (+/-1.0) ppm. This suggests that no adjustment would be required.
OTHER CROSS OVERS:
The cross over with cruise INDIGO1 shows an offset of -1 (+/-8) ppm, which
supports no adjustment.
CONCLUSION:
Based on the regional analyses above I suggest no adjustment for salinity.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-08 23:42:45 UTC for data product: CARINA, GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Hide comments