{'fraction_non_alphanumeric': 0.023709902370990237, 'fraction_numerical': 0.0, 'mean_word_length': 5.587155963302752, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Analysis of Timekeeping in Experimentation

Real-time experimentation in multiple areas relies on time synchronization across devices. Protocols are used to sync time between nodes, but the accuracy of synchronization achieved by those different protocols is sometimes overlooked and not taken into account. This is a major issue, especially in less reliable hardware commonly used in research like the Raspberry Pi (RPi).We compare the synchronization achieved between RPi using the commonly available clock sources (Global Positioning Systems (GPSs) and time-servers), synchronization procedures and software. Across all sources the software Chrony achieves the best result, and GPS is not always the best solution.