Argo Float Cycle Iridium Transmission Monitoring
|(Updated 28 Jun 2017 22:20 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.
|Here is the same plot highlighting the top 20% of the y-axis.|
|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
|Maximum hrs for a data file
to arrive at the GDAC
|Average=2.8 hrs||Average=9.8 hrs||Sum=2481|