The-clock-synchronization-problem.md

 Satellites send a signal and users’ receptor receives it. But in order to read the signal properly, both clocks (the satellites and the receptor’s) must have the same time scale.
 
+[![synchronisation](uploads/a3264678e17c3e22a1ab8659dab8f137/synchronisation.png)](https://www.bodet-time.com/time-servers/articles-and-resources/1595-why-is-time-synchronization-so-important.html)
+
 # **1st synchronization problem: the distance calculation is very sensitive to clock errors**
 
 Indeed, if we calculate the time a signal makes to go from the satellites to the receptor, in an ideal world, we only would have to use the fact that ![f11](http://chart.apis.google.com/chart?cht=tx&chl=d=ct). As time is multiplied by the speed of light, distance is very sensible to time mistake: ![f1](http://chart.apis.google.com/chart?cht=tx&chl=dD=%5Cfrac%7Bdt%7D%7Bt%7D)
@@ -24,4 +26,5 @@ Therefore, the localisation problem has 4 unknown parameters : the speed followi
 
 #### Sources :
 
-Calero, D., & Fernandez, E., & Parés, E. (2016) Positioning performance of Chip-Scale Atomic Clock GNSS augmentation systems. https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=7849326
\ No newline at end of file
+- Calero, D., & Fernandez, E., & Parés, E. (2016) Positioning performance of Chip-Scale Atomic Clock GNSS augmentation systems. https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=7849326
+- https://www.bodet-time.com/time-servers/articles-and-resources/1595-why-is-time-synchronization-so-important.html
\ No newline at end of file