Cruise: 74DI19950106 (dataset:CARINA) Data product: CARINA Successor: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Synonyms (including errata!) for this cruise: 74DI213_1; 74DI19950106; 74DI213_1; iss1sv; ISS01_i
IMPORTANT information for GLODAP Reference Group Editors: This adjustment version is immutable and published in CARINA! Click here to switch to new version (CARINA)
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!):
cfc11:1
cruise:2
nitrate:1
oxygen:1
phosphate:1
salinity:1
silicate:1
- no files! -
Filename: | Comment: | Action | |
---|---|---|---|
salinity_5_1014_cluster1_Claire.jpg | [Copy of salinity plot for crossover: 74AB20020301 / 74DI19950106!]; |
View |
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:3; no CTD salinity data. Setting CTD salinity offset to -999,
QC flag removed.
Oxygen action ID:3; no CTD oxygen data. Setting CTD oxygen offset to -999, QC
flag removed.
Posted by svheuven@gmail.com on 2015-02-19 09:22:20 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106/salinity: update slope+intercept
autogenerated: only BOTsal available (no CTDsal)
Posted by svheuven@gmail.com on 2014-12-18 16:52:45 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 Adjustment IND and PAC_SvH_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:46 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106/salinity: init slope+intercept
autogenerated: using BOTsal (no CTDsal)
Posted by svheuven@gmail.com on 2014-02-25 17:02:15 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - salinity
There are only few valid crossovers for this cruise. The inversion suggest a
correction of 2 and the mean of the crossovers is -1.5. GLODAP applied an
adjustment of 0.5 ppm and CARINA suggested that no adjustment should be applied.
We suggest that no adjustment should be applied.
Posted by ttanhua@geomar.de on 2012-07-18 17:14:25 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - salinity
GLOBAL ANALYSIS (Cruise plot file: RC_SO):
The average of all cross overs is +2.7 ppm.
The global inversion (WDLSQ) suggests no significant adjustment (-4.2 +/-8.1
ppm).
REGIONAL ANALYSIS:
6 cross overs were analyzed. The average of all cross overs is +1.3 (+/-2.5)
ppm.
All cross overs show no significant differences (< 5 ppm) and involve cruises
that are thought to have no significant offset in salinity. This suggests that
no adjustment would be required.
CONCLUSION:
The global and regional analyses agree.
Based on this I suggest no adjustment for salinity.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-04 12:18:42 UTC for data product: CARINA
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:3; no CTD salinity data. Setting CTD salinity offset to -999,
QC flag removed.
Oxygen action ID:3; no CTD oxygen data. Setting CTD oxygen offset to -999, QC
flag removed.
Posted by svheuven@gmail.com on 2015-02-19 09:22:20 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 Adjustment IND and PAC_SvH_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:46 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 Adjustment IND and PAC_SvH_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:46 UTC for data product: 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): : scrap these PO4 data, from
the NO3vsPO4 graph, they are scattery to the point of appearing random
Posted by svheuven@gmail.com on 2014-06-16 15:50:46 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - phosphate
Based on new inversion results it was decided in Groeningen to adjust phosphate
by an additional -7%
Posted by siv.lauvset@uib.no on 2014-02-11 16:57:53 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - phosphate
The inversion suggest a correction of 0.95 and the mean of the crossovers is
1.02. No adjustment was applied to GLODAP but an adjustment of 0.98 was
suggested by CARINA.
We suggest to follow the recommendation of CARINA and apply an adjustment of
0.98.
Posted by ttanhua@geomar.de on 2012-07-19 09:46:35 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - phosphate
GLOBAL ANALYSIS (Cruise plot file: RC_SO):
The average of all cross overs is 1.025.
The global inversion (WDLSQ) suggests that an adjustment of 0.95 could be
required (0.946 +/-0.030).
REGIONAL ANALYSIS:
6 cross overs were analyzed, but only 1 of them appears reliable indicating an
offset of 1.016 (+/-0.039) with cruise 74AB20020301 which is thought to have no
offset in phosphate. This suggest that an adjustment of 0.98 could be required.
CONCLUSION:
The global and regional analyses suggest that phosphate values could be high,
but different adjustments are proposed (0.95 and 0.98, respectively). The
lowest correction is preferred.
Based on this I suggest an adjustment of 0.98 for phosphate.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-04 12:21:33 UTC for data product: CARINA
Filename: | Comment: | Action | |
---|---|---|---|
nitrate_5_1014_cluster1_Claire.jpg | [Copy of nitrate plot for crossover: 74AB20020301 / 74DI19950106!]; |
View |
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): : make 1.05. This is the
only 74DI cruise that connects to the wider network (through RR2008)
Posted by svheuven@gmail.com on 2014-06-16 15:50:46 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - nitrate
The inversion suggest a correction of 1.046 and the mean of the crossovers is
0.942. An adjustment of -0.96 was applied to GLODAP and an adjustment of 1.03
was suggested by CARINA. All crossovers with GLODAP cruises suggest that this
cruise report low nitrate values. We suggest to follow the recommendations by
CARINA, i.e an adjustment of 1.03.
Posted by ttanhua@geomar.de on 2012-07-18 17:20:37 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - nitrate
GLOBAL ANALYSIS (Cruise plot file: RC_SO):
The average of all cross overs is 0.955.
The global inversion (WDLSQ) suggests no significant adjustment (0.998
+/-0.014).
REGIONAL ANALYSIS:
6 cross overs were analyzed, but 1 is discarded due to large uncertainty (with
cruise INDIGO3). The average of the 5 considered cross overs is 0.964
(+/-0.019).
All cross overs show offsets lower or close to 0.98, which suggest that the
cruise would have low nitrate values. The largest offsets are found with cruises
35MF19960220 and 74AB20020301 which are thought to have high nitrate values.
When the offsets suggested for those 2 cruises are taken into account the
average of all cross overs is 0.972 (+/-0.007). This suggests that an adjustment
of 1.03 could be required.
CONCLUSION:
The result of the global inversion is not coherent with the result of individual
cross overs from the global analysis (see Cruise plot file: RC_SO). Because the
latter is supported by the regional analysis, it is likely that the inversion
has failed here.
Based on this I suggest an adjustment of 1.03 for nitrate.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-04 12:19:48 UTC for data product: CARINA
Filename: | Comment: | Action | |
---|---|---|---|
phosphate_5_1014_cluster1_Claire.jpg | [Copy of phosphate plot for crossover: 74AB20020301 / 74DI19950106!]; |
View |
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): : scrap these PO4 data, from
the NO3vsPO4 graph, they are scattery to the point of appearing random
Posted by svheuven@gmail.com on 2014-06-16 15:50:46 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - phosphate
Based on new inversion results it was decided in Groeningen to adjust phosphate
by an additional -7%
Posted by siv.lauvset@uib.no on 2014-02-11 16:57:53 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - phosphate
The inversion suggest a correction of 0.95 and the mean of the crossovers is
1.02. No adjustment was applied to GLODAP but an adjustment of 0.98 was
suggested by CARINA.
We suggest to follow the recommendation of CARINA and apply an adjustment of
0.98.
Posted by ttanhua@geomar.de on 2012-07-19 09:46:35 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - phosphate
GLOBAL ANALYSIS (Cruise plot file: RC_SO):
The average of all cross overs is 1.025.
The global inversion (WDLSQ) suggests that an adjustment of 0.95 could be
required (0.946 +/-0.030).
REGIONAL ANALYSIS:
6 cross overs were analyzed, but only 1 of them appears reliable indicating an
offset of 1.016 (+/-0.039) with cruise 74AB20020301 which is thought to have no
offset in phosphate. This suggest that an adjustment of 0.98 could be required.
CONCLUSION:
The global and regional analyses suggest that phosphate values could be high,
but different adjustments are proposed (0.95 and 0.98, respectively). The
lowest correction is preferred.
Based on this I suggest an adjustment of 0.98 for phosphate.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-04 12:21:33 UTC for data product: CARINA
Filename: | Comment: | Action | |
---|---|---|---|
silicate_5_1014_cluster1_Claire.jpg | [Copy of silicate plot for crossover: 74AB20020301 / 74DI19950106!]; |
View |
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): : make 1.08. This based on
specially made figures with 400km station radius, linking 74DI to WOCE.
Posted by svheuven@gmail.com on 2014-06-16 15:50:46 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - silicate
Based on new inversion results it was decided in Groeningen to change the
previous adjustment from +11% to +5%
Posted by siv.lauvset@uib.no on 2014-02-11 16:51:30 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - silicate
After some email correspondence regarding the large silicate adjustment of this
cruise, we were faced with the challenge: Include data with a large adjustment
that is difficult to assess correctly, or to have a large hole with no data.
We decided to go with including these data after all, hoping that better
assessment of the adjustment can be done by the complete GLODAPv2 collection
Posted by ttanhua@geomar.de on 2012-08-02 17:28:46 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - silicate
Mario and Toste
SInce the crossovers with other cruises here is inconsistent, and an adjustment
in the order of 10% is needed, we decided to flag the silicate values for this
cruise and not use the data in the data-product
Posted by ttanhua@geomar.de on 2012-08-01 17:08:41 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - silicate
The inversion suggest a correction of 1.06 and the mean of the crossovers is
0.89. GLODAP adjusted this cruise with -8.2 and an adjustment of 1.11 is
suggested by CARINA (which is very different form the GLODAP adjustment in the
deep waters in this region).
We suggest to follow the recommendation of CARINA and apply an adjustment of
1.11.
Posted by ttanhua@geomar.de on 2012-07-19 09:52:52 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - silicate
GLOBAL ANALYSIS (Cruise plot file: RC_SO):
The average of all cross overs is 0.872.
The global inversion (WDLSQ) suggests that an adjustment of 1.11 could be
required (1.114 +/-0.033).
REGIONAL ANALYSIS:
6 cross overs were analyzed, but only 3 appear reliable (with cruises
35MF19960220, 74AB20020301 and 74DI20041213). All 3 cruises are thought to have
high silicate values. When the suggested offsets are taken into account the
average for the 3 considered cross overs is 0.894 (+/-0.010). This suggests that
an adjustment of 1.11 could be required.
CONCLUSION:
The global and regional analyses agree.
Based on this I suggest an adjustment of 1.11 for silicate.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-04 12:22:24 UTC for data product: CARINA
Filename: | Comment: | Action | |
---|---|---|---|
oxygen_5_1014_cluster1_Claire.jpg | [Copy of oxygen plot for crossover: 74AB20020301 / 74DI19950106!]; |
View |
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:3; no CTD salinity data. Setting CTD salinity offset to -999,
QC flag removed.
Oxygen action ID:3; no CTD oxygen data. Setting CTD oxygen offset to -999, QC
flag removed.
Posted by svheuven@gmail.com on 2015-02-19 09:22:20 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106/oxygen: update slope+intercept
autogenerated: only BOToxy available (no CTDoxy)
Posted by svheuven@gmail.com on 2014-12-18 16:52: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 Adjustment IND and PAC_SvH_20140611.xlsx): : Maintain. There are 5
74DI, the inversion would to them +2 +1 +1 +1 -3, but it might be better to do
+1 0 0 0 -4, which is what was already decided in CARINA.
Posted by svheuven@gmail.com on 2014-06-16 15:50:46 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106/oxygen: init slope+intercept
autogenerated: using BOToxy (no CTDoxy)
Posted by svheuven@gmail.com on 2014-02-25 17:02:15 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - oxygen
The inversion suggest a correction of 1.005 and the mean of the crossovers is
0.994. An adjustment of -0.003 ml/L is applied and CARINA suggest that no
adjustment is applied.
We suggest that no adjustment is applied.
Posted by ttanhua@geomar.de on 2012-07-19 09:56:03 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - oxygen
GLOBAL ANALYSIS (Cruise plot file: RC_SO):
The average of all cross overs is 0.997.
The global inversion (WDLSQ) suggests no significant adjustment (1.006
+/-0.006).
REGIONAL ANALYSIS:
6 cross overs were analyzed. The average of all cross overs is 1.000 (+/-0.007).
All cross overs show no significant differences (<1%) and all but 1 (with cruise
74DI19940219) involve cruises that are thought to have no offset in oxygen.
This suggests that no adjustment would be required.
CONCLUSION:
The global and regional analyses agree.
Based on this I suggest no adjustment for oxygen.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-04 12:23:06 UTC for data product: CARINA
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:3; no CTD salinity data. Setting CTD salinity offset to -999,
QC flag removed.
Oxygen action ID:3; no CTD oxygen data. Setting CTD oxygen offset to -999, QC
flag removed.
Posted by svheuven@gmail.com on 2015-02-19 09:22:20 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
Filename: | Comment: | Action | |
---|---|---|---|
cfc11_4_1014_Marta.eps | [Copy of cfc11 plot for crossover: 74AB20020301 / 74DI19950106!]; |
View |
View comment(s) (filtered by cfc11 in subject)
74DI19950106 - cfc11
Only CFC11 available, making QC more difficult. However, the surface saturation
is 105%, and compared to other cruises near in space and time this should rather
be closer to full saturation, or even slightly lower. Also, the depth profiles
suggest that the values may be somewhat too high. We recommend an adjustment of
0.95. This should be re-evaluated in the final analysis.
Posted by emje@norceresearch.no on 2013-01-09 17:48:41 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
View 27 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:3; no CTD salinity data. Setting CTD salinity offset to -999,
QC flag removed.
Oxygen action ID:3; no CTD oxygen data. Setting CTD oxygen offset to -999, QC
flag removed.
Posted by svheuven@gmail.com on 2015-02-19 09:22:20 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106/oxygen: update slope+intercept
autogenerated: only BOToxy available (no CTDoxy)
Posted by svheuven@gmail.com on 2014-12-18 16:52:45 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106/salinity: update slope+intercept
autogenerated: only BOTsal available (no CTDsal)
Posted by svheuven@gmail.com on 2014-12-18 16:52: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 Adjustment IND and PAC_SvH_20140611.xlsx): : Maintain. There are 5
74DI, the inversion would to them +2 +1 +1 +1 -3, but it might be better to do
+1 0 0 0 -4, which is what was already decided in CARINA.
Posted by svheuven@gmail.com on 2014-06-16 15:50:46 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 Adjustment IND and PAC_SvH_20140611.xlsx): : make 1.08. This based on
specially made figures with 400km station radius, linking 74DI to WOCE.
Posted by svheuven@gmail.com on 2014-06-16 15:50:46 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 Adjustment IND and PAC_SvH_20140611.xlsx): : scrap these PO4 data, from
the NO3vsPO4 graph, they are scattery to the point of appearing random
Posted by svheuven@gmail.com on 2014-06-16 15:50:46 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 Adjustment IND and PAC_SvH_20140611.xlsx): : make 1.05. This is the
only 74DI cruise that connects to the wider network (through RR2008)
Posted by svheuven@gmail.com on 2014-06-16 15:50:46 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 Adjustment IND and PAC_SvH_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:46 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 Adjustment IND and PAC_SvH_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:46 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 Adjustment IND and PAC_SvH_20140611.xlsx): : maintain
Posted by svheuven@gmail.com on 2014-06-16 15:50:46 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106/oxygen: init slope+intercept
autogenerated: using BOToxy (no CTDoxy)
Posted by svheuven@gmail.com on 2014-02-25 17:02:15 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106/salinity: init slope+intercept
autogenerated: using BOTsal (no CTDsal)
Posted by svheuven@gmail.com on 2014-02-25 17:02:15 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - phosphate
Based on new inversion results it was decided in Groeningen to adjust phosphate
by an additional -7%
Posted by siv.lauvset@uib.no on 2014-02-11 16:57:53 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - silicate
Based on new inversion results it was decided in Groeningen to change the
previous adjustment from +11% to +5%
Posted by siv.lauvset@uib.no on 2014-02-11 16:51:30 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - cfc11
Only CFC11 available, making QC more difficult. However, the surface saturation
is 105%, and compared to other cruises near in space and time this should rather
be closer to full saturation, or even slightly lower. Also, the depth profiles
suggest that the values may be somewhat too high. We recommend an adjustment of
0.95. This should be re-evaluated in the final analysis.
Posted by emje@norceresearch.no on 2013-01-09 17:48:41 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - silicate
After some email correspondence regarding the large silicate adjustment of this
cruise, we were faced with the challenge: Include data with a large adjustment
that is difficult to assess correctly, or to have a large hole with no data.
We decided to go with including these data after all, hoping that better
assessment of the adjustment can be done by the complete GLODAPv2 collection
Posted by ttanhua@geomar.de on 2012-08-02 17:28:46 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - silicate
Mario and Toste
SInce the crossovers with other cruises here is inconsistent, and an adjustment
in the order of 10% is needed, we decided to flag the silicate values for this
cruise and not use the data in the data-product
Posted by ttanhua@geomar.de on 2012-08-01 17:08:41 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - oxygen
The inversion suggest a correction of 1.005 and the mean of the crossovers is
0.994. An adjustment of -0.003 ml/L is applied and CARINA suggest that no
adjustment is applied.
We suggest that no adjustment is applied.
Posted by ttanhua@geomar.de on 2012-07-19 09:56:03 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - silicate
The inversion suggest a correction of 1.06 and the mean of the crossovers is
0.89. GLODAP adjusted this cruise with -8.2 and an adjustment of 1.11 is
suggested by CARINA (which is very different form the GLODAP adjustment in the
deep waters in this region).
We suggest to follow the recommendation of CARINA and apply an adjustment of
1.11.
Posted by ttanhua@geomar.de on 2012-07-19 09:52:52 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - phosphate
The inversion suggest a correction of 0.95 and the mean of the crossovers is
1.02. No adjustment was applied to GLODAP but an adjustment of 0.98 was
suggested by CARINA.
We suggest to follow the recommendation of CARINA and apply an adjustment of
0.98.
Posted by ttanhua@geomar.de on 2012-07-19 09:46:35 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - nitrate
The inversion suggest a correction of 1.046 and the mean of the crossovers is
0.942. An adjustment of -0.96 was applied to GLODAP and an adjustment of 1.03
was suggested by CARINA. All crossovers with GLODAP cruises suggest that this
cruise report low nitrate values. We suggest to follow the recommendations by
CARINA, i.e an adjustment of 1.03.
Posted by ttanhua@geomar.de on 2012-07-18 17:20:37 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - salinity
There are only few valid crossovers for this cruise. The inversion suggest a
correction of 2 and the mean of the crossovers is -1.5. GLODAP applied an
adjustment of 0.5 ppm and CARINA suggested that no adjustment should be applied.
We suggest that no adjustment should be applied.
Posted by ttanhua@geomar.de on 2012-07-18 17:14:25 UTC for data product: GLODAPv2, v2.2019, v2.2020, v2.2021, v2.2022, v2.2023
74DI19950106 - oxygen
GLOBAL ANALYSIS (Cruise plot file: RC_SO):
The average of all cross overs is 0.997.
The global inversion (WDLSQ) suggests no significant adjustment (1.006
+/-0.006).
REGIONAL ANALYSIS:
6 cross overs were analyzed. The average of all cross overs is 1.000 (+/-0.007).
All cross overs show no significant differences (<1%) and all but 1 (with cruise
74DI19940219) involve cruises that are thought to have no offset in oxygen.
This suggests that no adjustment would be required.
CONCLUSION:
The global and regional analyses agree.
Based on this I suggest no adjustment for oxygen.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-04 12:23:06 UTC for data product: CARINA
74DI19950106 - silicate
GLOBAL ANALYSIS (Cruise plot file: RC_SO):
The average of all cross overs is 0.872.
The global inversion (WDLSQ) suggests that an adjustment of 1.11 could be
required (1.114 +/-0.033).
REGIONAL ANALYSIS:
6 cross overs were analyzed, but only 3 appear reliable (with cruises
35MF19960220, 74AB20020301 and 74DI20041213). All 3 cruises are thought to have
high silicate values. When the suggested offsets are taken into account the
average for the 3 considered cross overs is 0.894 (+/-0.010). This suggests that
an adjustment of 1.11 could be required.
CONCLUSION:
The global and regional analyses agree.
Based on this I suggest an adjustment of 1.11 for silicate.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-04 12:22:24 UTC for data product: CARINA
74DI19950106 - phosphate
GLOBAL ANALYSIS (Cruise plot file: RC_SO):
The average of all cross overs is 1.025.
The global inversion (WDLSQ) suggests that an adjustment of 0.95 could be
required (0.946 +/-0.030).
REGIONAL ANALYSIS:
6 cross overs were analyzed, but only 1 of them appears reliable indicating an
offset of 1.016 (+/-0.039) with cruise 74AB20020301 which is thought to have no
offset in phosphate. This suggest that an adjustment of 0.98 could be required.
CONCLUSION:
The global and regional analyses suggest that phosphate values could be high,
but different adjustments are proposed (0.95 and 0.98, respectively). The
lowest correction is preferred.
Based on this I suggest an adjustment of 0.98 for phosphate.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-04 12:21:33 UTC for data product: CARINA
74DI19950106 - nitrate
GLOBAL ANALYSIS (Cruise plot file: RC_SO):
The average of all cross overs is 0.955.
The global inversion (WDLSQ) suggests no significant adjustment (0.998
+/-0.014).
REGIONAL ANALYSIS:
6 cross overs were analyzed, but 1 is discarded due to large uncertainty (with
cruise INDIGO3). The average of the 5 considered cross overs is 0.964
(+/-0.019).
All cross overs show offsets lower or close to 0.98, which suggest that the
cruise would have low nitrate values. The largest offsets are found with cruises
35MF19960220 and 74AB20020301 which are thought to have high nitrate values.
When the offsets suggested for those 2 cruises are taken into account the
average of all cross overs is 0.972 (+/-0.007). This suggests that an adjustment
of 1.03 could be required.
CONCLUSION:
The result of the global inversion is not coherent with the result of individual
cross overs from the global analysis (see Cruise plot file: RC_SO). Because the
latter is supported by the regional analysis, it is likely that the inversion
has failed here.
Based on this I suggest an adjustment of 1.03 for nitrate.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-04 12:19:48 UTC for data product: CARINA
74DI19950106 - salinity
GLOBAL ANALYSIS (Cruise plot file: RC_SO):
The average of all cross overs is +2.7 ppm.
The global inversion (WDLSQ) suggests no significant adjustment (-4.2 +/-8.1
ppm).
REGIONAL ANALYSIS:
6 cross overs were analyzed. The average of all cross overs is +1.3 (+/-2.5)
ppm.
All cross overs show no significant differences (< 5 ppm) and involve cruises
that are thought to have no significant offset in salinity. This suggests that
no adjustment would be required.
CONCLUSION:
The global and regional analyses agree.
Based on this I suggest no adjustment for salinity.
___________________
Paris, August 2008
Claire Lo Monaco
Posted by claire.lomonaco@locean.upmc.fr on 2008-10-04 12:18:42 UTC for data product: CARINA
Hide comments