| | 23 | When the UnixTime object is constructed, it will get system time and set the reference point to the 12am of "today". |
| | 24 | Therfore, packet tx_timestamp and rx_timestamp are reporting the milliseconds passed since the 12am of the experiment day. |
| | 25 | As long as the nodes are NTP synced, the comparison of stamps to calculate delay would be no problem. |
| | 26 | |
| | 27 | For experiments around 12am, this is still an incomplete solution. |
| | 28 | So --clockref parameters are added in both OTG/OTR. The nodehandler could give an integer number to this option when starting otr/otg, to caliberating |
| | 29 | the timestamp-clock reference. |
| | 30 | This integer is the # of hours passed since 01/01/1970, for example, 313171 will shift the clock reference to 3pm 09/22/2005. I suggest nodehandler add |
| | 31 | a routine to calculate this number and passed it to otg/otr along with oml-name, oml-config... |
| | 32 | |
