When Clocks Are Not Working: OBS Time Correction
Abstract Ocean-bottom seismographs (OBSs) are used to obtain seismic recordings offshore and are an increasingly important tool for investigating the globe. However, because OBS data cannot be time stamped using Global Positioning System (GPS) during deployment, correction for drift of the internal clock is required. This time drift is typically derived by synchronizing the clock before and after deployment. Linear correction is then applied using the timing deviation between GPS and the instrument’s internal clock at recovery, that is, the skew measurement. If synchronization measurements are missing, ambient noise cross-correlation functions (CCFs) are commonly used for time correction. When investigating recordings from a small-scale OBS network located on the Mohn’s mid-ocean ridge, we observed a remaining drift on the skew-corrected data. After recalculating the drift of the raw data using CCFs, we found that the skew-based time correction was incorrect. This was also verified with the observation of teleseismic P-wave arrivals. We describe a method to obtain properly time-corrected data and discuss the OBS timing issues in detail. The results shown were obtained using a software package that we developed for this specific purpose and made available as open-source software. Although we cannot explain the technical reason for the failure of skew correction, this study shows that skew corrections should not be trusted alone, and OBS timing should always be verified by either ambient noise correlations or P-wave arrival times.