Note: clockfile code is not successfully running on ran at the moment. I did, however, discover that the data files tcxo_tmp_archive.csv, latest_freq.dat and latest_clock.dat are all successfully updated before the network connection closes, which allowed me to download them and perform the local side of the clockfile procedure.
With the addition of two new data points, the fit seems to be behaving well. There is a slight discontinuity at Jan 24 - Jan 25, during the large gap in regular Malindi contacts. There is also a gap between Feb 7 and Feb 10, though it appears that we made successful Malindi contacts during that time so it is unclear why they haven't made it into the clockfile data.
I'd like to see whether pulling in some new bad data points makes a difference in the clockfile code successfully running on ran, and I don't think it would hurt to keep the bad data points up to date while we work on figuring out what's breaking on ran.
Added two bad points.
Note: clockfile code is not successfully running on ran at the moment. I did, however, discover that the data files tcxo_tmp_archive.csv, latest_freq.dat and latest_clock.dat are all successfully updated before the network connection closes, which allowed me to download them and perform the local side of the clockfile procedure.
With the addition of two new data points, the fit seems to be behaving well. There is a slight discontinuity at Jan 24 - Jan 25, during the large gap in regular Malindi contacts. There is also a gap between Feb 7 and Feb 10, though it appears that we made successful Malindi contacts during that time so it is unclear why they haven't made it into the clockfile data.
I'd like to see whether pulling in some new bad data points makes a difference in the clockfile code successfully running on ran, and I don't think it would hurt to keep the bad data points up to date while we work on figuring out what's breaking on ran.
Before:
After:
Summary: