Updating the launch scripts so that they always reset the current R session's time zone to the match the current system's time zone. If you were using a time zone different from the system's zone, the clock value uploaded to the ibutton would be offset from the system's time zone. This did not affect the starting time of the mission, since that is simply set by the start delay value (in minutes) from the time of the mission upload, but it did mean that all of the time stamps in the output file could be off by the number of hours between your R session time and the OS time.