It was discovered in July 2022 that the "timelen" column of emolt.dat 2015-2017 was in error. When JiM tried to restore an emolt.dat file from July 2021, he found this issue existed then but it wasn't noticed until about a year later. One solution would be to start from scratch and process the raw JSON files coming from AP3's (assuming this datastream had the correct timelen value). The "getfix.py" which reads the json files and outputs the emolt.dat file may have been converting this data incorrectly. We will need to decide units (minutes, hours, or days).
It was discovered in July 2022 that the "timelen" column of emolt.dat 2015-2017 was in error. When JiM tried to restore an emolt.dat file from July 2021, he found this issue existed then but it wasn't noticed until about a year later. One solution would be to start from scratch and process the raw JSON files coming from AP3's (assuming this datastream had the correct timelen value). The "getfix.py" which reads the json files and outputs the emolt.dat file may have been converting this data incorrectly. We will need to decide units (minutes, hours, or days).