Copernicus Marine Service Arctic MFC: Validation of sea level anomaly and geostrophic velocity
Validation based on satellite data from Jason-2, Jason-3
Validation of the Copernicus Marine Arctic MFC results for sea level anomaly and geostrophic velocity is performed using altimeter data from the the Jason-2 satellite and (from 2016-09-08) the Jason-3 satellite. These data have been corrected for a number of processes, including removal of the tidal signal and correction for the inverse barometer effect. Note that altimeter data from Jason-2/-3 are assimilated in the EnKF used in the ARC-MFC (TOPAZ) model. However, we use an updated product for this validation, which may have improvements due to an updated computation of the inverse barometer, and more precise knowledge of the satellite orbit.
Each Jason cycle is diveded into 254 tracks, half of which are ascending and half are descending (more below). The instrument's sampling frequency is approximately 0.927 Hz, corresponding to a horizontal separation of about 18.5 km along the track.
Jason-2/-3 data are available from the Copernicus Marine product SEALEVEL_GLO_PHY_L3_NRT_OBSERVATIONS_008_044.
Validation based on satellite data from CryoSat-2
Validation of the Copernicus Marine Arctic MFC results for sea level anomaly and geostrophic velocity is also performed using altimeter data from the the CryoSat-2 satellite. These data have been corrected similarly to those from the Jason missions (see details above).
The CryoSat repeat cycle is diveded into 5344 tracks, covered during 369 days of operations. This repeat cycle is made up of sub-cycles from approximately 30 days. The orbit period is 99.16 minutes. More information about the CryoSat mission is available from ESA.
CryoSat-2 data are available from the Copernicus Marine product SEALEVEL_GLO_PHY_L3_NRT_OBSERVATIONS_008_044.
Validation based on satellite data from Sentinel-6a
Validation of the Copernicus Marine Arctic MFC results for sea level anomaly and geostrophic velocity is additionally performed using altimeter data from the the Sentinel-6 satellite. These data have been corrected similarly to the other missions (see details above).
Sentinel-6a was placed in the Jason-3 orbit, from which it has provided observations of sea level anomalies from March 2022 onwards. At the same time Sentinel-6a have also substituted Jason-3 as the reference altimeter mission. The repeat cycle and track data are thus identical to the information provided for Jason-2/-3 above. The initial analysis of observations from Sentinel reveals that the data quality beats initial expectations. This analysis is described by ESA.
| January 2024
01-04 01-11 01-18 01-25 |
February 2024
02-01 02-08 02-15 02-22 02-29 |
March 2024
03-07 03-14 03-21 03-28 |
|||||||||
| January 2023
01-05 01-12 01-19 01-26 |
February 2023
02-02 02-09 02-16 02-23 |
March 2023
03-02 03-09 03-16 03-23 03-30 |
April 2023
04-06 04-13 04-20 04-27 |
May 2023
05-04 05-11 05-18 05-25 |
June 2023
06-01 06-08 06-15 06-22 06-29 |
July 2023
07-06 07-13 07-20 07-27 |
August 2023
08-03 08-10 08-17 08-24 08-31 |
September 2023
09-07 09-14 09-21 09-28 |
October 2023
10-05 10-12 10-19 10-26 |
November 2023
11-02 11-09 11-16 11-23 11-30 |
December 2023
12-07 12-14 12-21 12-28 |
| March 2022
03-24 03-31 |
April 2022
04-07 04-14 04-21 04-28 |
May 2022
05-05 05-12 05-19 05-26 |
June 2022
06-02 06-09 06-16 06-23 06-30 |
July 2022
07-07 07-14 07-21 07-28 |
August 2022
08-04 08-11 08-18 08-25 |
September 2022
09-01 09-08 09-15 09-22 09-29 |
October 2022
10-06 10-13 10-20 10-27 |
November 2022
11-03 11-10 11-17 11-24 |
December 2022
12-01 12-08 12-15 12-22 12-29 |
Regions
|
JasonThe ocean circulation model used in Copernicus Marine Arctic MFC covers the Arctic Ocean, the North Atlantic Ocean and adjacent ocean regions. The northern part is depicted in the figure to the left. Validation of sea level anomalies from model results are performed for two domains:
The validation is performed using processed data from the altimeter onboard the Jason-2 and Jason-3 satellites. The region covered by the satellite is limited by the 66° 8' parallell, as indicated in the figure below. This limit in the poleward extent of data significantly reduces the extent of the key domain for Copernicus Marine Arctic Monitoring and Forecasting Centre. However, using Jason-2 data almost eliminates possible problems due to the presence of sea ice at higher latitudes. Like its predecessors TOPEX/Poseidon and Jason-1, Jason-2 and Jason-3 have an orbital period of 6754 s (1:52:34). The full surface trace is constituted by 254 tracks, with one ascending track and one descending track in each orbit. Tracks in the region relevant for the Arctic Monitoring and Forecasting Centre are shown by the black curves below. The repeat period then becomes approximately 10 days. Using tide gauge data from around the world as reference, validation of Jason-2 altimetry data has revealed a standard deviation of the sea level anomaly of approxiately 4 cm. |
|
CryoSatSimilarly to the validation that uses data from the Jason missions, we consider two domains:
Note that the CryoSat mission extends much further north than the extent of the Jason missions. Data from CryoSat are available as far north as approximately 82°N. |
Processing
Sea level anomaly
|
The RMS difference between model sea level and observations is calculated track-by-track. Before the root-mean-square differences and correlations are computed, the following processing is performed:
|
|
|
The full set of Jason ground tracks north of 50°N. Jason-2 suffered from an onboard memory error which was detected on 2013-03-25. As a consequence, there were periods with data outages in late March and early April in 2013. |
|
CryoSat ground tracks north of 50°N. The figure shows an example of the coverage during the time period covered during one of the weekly validation bulletins (17 days). |
Geostrophic velocity component
Here, we take advantage of the relationship between the sea surface slope and geostrophic velocity. Since sea level data are only available along the satellites' ground tracks, we are restricted to assessing the component of velocity normal to these tracks.
The relationship between sea surface slope along the track, hs
and speed of current component normal to the track, vgstr,
is
vgstr = g|hs/f|
where g is the gravitational acceleration and f is the local Coriolis
parameter.
In order to compare the geostrophic velocity component derived from observations, we adopt the same approach for the model results (and not model velocity), i.e., we compute this quantity based on model results for sea level. Note that to comply with the algorithm for computation of anomalies for sea level as described above, we here add the model climatology to the observed sea level anomalies (we choose to compare speed, not speed anomalies).
Finally, in order to account for directional differences in the derived results for speed of the geostrophic velocity component, the model results are set to a negative value in cases were the slope sign is opposite in model and observations.
ARC-MFC (TOPAZ)
The model results are produced with the TOPAZ ocean data assimilation model system (Copernicus Marine product ARCTIC_ANALYSIS_FORECAST_PHYS_002_001_a). Presently, TOPAZ is run weekly with data assimillation one week prior to the bulletin date, followed by a one-week 100 member ensemble simulation ending on the bulletin date, and finally a 10 day deterministic forecast. TOPAZ was developed and is maintained by the Nansen Center.
ARC-MFC PHYS (TOPAZ) results are available as Copernicus Marine product ARCTIC_ANALYSIS_FORECAST_PHYS_002_001_a. An archive of historical forecasts are available from a thredds server.
