Real-time Data Transfer:
Data transfer occurs each hour (see timing table below) and is initiated from our remote sites via a
Bash script that calls rsync to physically perform the transferring of files. The methodology behind this is that this allows for greater flexibility on our central server to be "listening" or "passively" accepting files from remote sites, which ssh-key authetication exists, and not have to run a time consuming routine on the server to retrieve data. If you think about it, this mehtod also does not create hiccups and unnecessary time delays on the server end and it can be safefully assumed that if a file from a remote site did not make the transfer for a particular hour then there was some communication problem or remote site problem. Further by using rsync we are able to regain lost information due to communication failures after the communication has been restored.
The above Bash script is run on each remote site at 5 minutes past each hour. The reason it is not run at 00 minutes past each hour is that radials are not outputed each hour at a consistent time due to hiccups in processing and averaging of radials at each out sites.
Time series plot showing the amount of time that the above script took to complete at each of Monterey Bay's remote sites.
Real-time Data Processing:
After a brief period to allow file transfers to come in from the remote sites we run HFR_Progs for each of the domains to the left at the times below.
Product Timing:
| PRODUCT | HOURLY TIMING (min) |
| rsync from remote sites | 05 |
| MNTY | 15 |
| SFOO | 16 |
| ANVO | 17 |
| CENT | 18 |
| Radial & Elliptical Plotting | 19 |
| BDGA | 20 |
