Transmission Monitoring


Return to sio-argo.ucsd.edu.home


Argo Float Cycle Iridium Transmission Monitoring

        (Updated 18 Dec 2017 02:27 GMT )





Percentage Success of Argo float Iridium cycle data transmission between SIO and AOML

SIO decodes the Iridium data transmitted by our floats. This data is then communicated to AOML, who passes the data onward to the GDAC and GTS. Argo strives to make float data available within 24 hours of transmission. The below figure tracks SIOs success in aiding this goal. This figure is updated daily.

Percentage Success is defined as the percentage of Argo float cycle data that is transmitted to AOML within 5 hrs. This measure was chosen to leave more than sufficent time for the data to reach the GDAC/GTS within 24 hrs.

Horizontal Axis: Time
Veritcal Axis: Percentage Success and Number of Cycles. Both share the same axis scale.

Black Line: Percentage Success determined daily.
Red Circle: Percentage Success averaged over the given month
Green Circle: Percentage of Argo float cycles that were successfully transmitted to AOML within 12 hours, averaged over the given month. This measure is more lenient then Percentage Success, but still provides sufficient time for the data to reach the GDAC/GTS within 24 hrs.
Cyan Line: Percentage of SIO Argo float cycles ('R' files) that were submitted to the GDAC by AOML within 24 hours, averaged daily.
Magenta Circle: Percentage of SIO Argo float cycles ('R' files) that were submitted to the GDAC by AOML within 24 hours, averaged over the given month.
Blue Line: Number of daily Argo float Iridium cycles collected and processed by SIO, followed by transmission to AOML.
Red Dashes (top of plot): Days on which an AOML ftp server outage occurred which affected SIO file transmission. On these days the most likely cause of reduced Percentage Success is due to the unavailability of the AOML ftp server.

Note that the number of cycles in the AOML daily/monthly percentage can be reduced due to the exchange of the 'R' for 'D' profile netCDF files at the GDAC. The AOML percentage is based on this reduced number.




ftp stability plot



Here is the same plot highlighting the top 20% of the y-axis.


ftp stability plot detail



A preliminary study to determine how quickly SIO needs to transmit the Argo data to AOML, in order for AOML to successfully place the data at the Argo GDAC within 24 hrs was performed on March 20,2015. It is based on 2.5 months of monitoring (January 8th, 2015 through March 20th, 2015). This study will be updated occasionally. Averaging over all cycles which reached the GDAC within 36 hrs, the average time between AOML receiving the data from SIO and the data being delivered to the GDAC is 7hrs.

If SIO sent the data to
AOML within X hrs...
Data arrives at the GDAC
within X hrs... (on average)
Number of Cycles
in Average
Maximum hrs for a data file
to arrive at the GDAC
1 8.5 321 15
2 9.1 819 20
3 10.1 770 24
4 10.9 495 25
5 11.0 21 15
6 11.9 13 13
7 12.5 8 14
8 14.1 8 16
9 15.4 8 17
10 15.7 6 16
11 16.4 5 17
12 17.7 3 18
13 19.0 1 19
14 19.5 2 20
16 21.0 1 21
Average=2.8 hrs Average=9.8 hrs Sum=2481