v0.3

What's Changed

• High resolution and fix recent by @matteobachetti in #20
• Do not plot and other fixes by @matteobachetti in #25
• Updated bad samples for November 20, 2020 release by @bwgref in #27
• Updated bad samples for Jan 4, 2021 release by @bwgref in #29
• Updated bad points database by @hpearnshaw in #30
• Updated bad points database by @hpearnshaw in #31
• Flagged some additional bad points in early Feb by @bwgref in #35
• Updated bad points database by @hpearnshaw in #36
• Lots of bad data points on days 2021:065 through 2021:068 by @bwgref in #37
• Updated bad samples for April 2021 intermediate udpate by @bwgref in #38
• May2021 outage by @bwgref in #39
• Final update of bad samples for May 24, 2021 release by @bwgref in #40
• Updated bad points database by @hpearnshaw in #41
• Updated for July 2021 by @bwgref in #44
• Update dependencies to latest versions by @matteobachetti in #46
• Updated bad data points for the early August 2021 Malindi issue by @bwgref in #45
• Mid September 2021 bad points update by @bwgref in #48
• Added 1 bad data point by @hpearnshaw in #49
• Added bad data points by @hpearnshaw in #50
• Added bad data points by @hpearnshaw in #51
• Added bad data points by @hpearnshaw in #52
• Bad points updated for early Jan by @bwgref in #53
• Added 2 bad data points by @hpearnshaw in #54
• Added 2 bad data points by @hpearnshaw in #55
• Added 3 bad data points by @hpearnshaw in #56
• End of Feb bad points by @bwgref in #57
• Bad data points for mid-March by @hpearnshaw in #58
• One more bad point by @hpearnshaw in #59
• Added 3 bad data points by @hpearnshaw in #60
• Added 1 bad data point by @hpearnshaw in #61
• Added 3 bad data points by @hpearnshaw in #62
• Late May update, added multiple bad samples by @bwgref in #63
• Bad data points up to beginning of June by @hpearnshaw in #64
• June clock issue update by @bwgref in #65
• Added clock jumps and some bad points in July by @bwgref in #66
• Post-glitch bad samples by @bwgref in #67
• Bad data points for mid-August by @hpearnshaw in #68
• Bad data points for end of August by @hpearnshaw in #69
• Bad data points for mid-September by @hpearnshaw in #70
• Bad points for mid-September by @bwgref in #71
• mid-October update by @bwgref in #72
• Mid-November update by @hpearnshaw in #73
• Late November update by @hpearnshaw in #74
• December card reset update by @bwgref in #75
• Mid-January update by @hpearnshaw in #77
• Early Feb update by @hpearnshaw in #78
• Bad data points for late Feb by @hpearnshaw in #79
• Bad data points for early March by @hpearnshaw in #80
• Bad data points for late March by @hpearnshaw in #81
• Bad data points for early April by @hpearnshaw in #82
• Bad data points for mid-April by @hpearnshaw in #83
• Bad data points for early May by @hpearnshaw in #84
• Bad data points for mid-May by @hpearnshaw in #85
• Bad data points for end of May by @hpearnshaw in #86
• Bad data points for mid-June by @hpearnshaw in #87
• Early July Update by @bwgref in #88
• Bad data points for mid-July by @hpearnshaw in #89
• Bad data points for end of July by @hpearnshaw in #90
• Bad data points for mid-August by @hpearnshaw in #91
• Bad data points for end of August by @hpearnshaw in #92
• Bad data points for mid-September by @hpearnshaw in #94
• Bad data points for end of September by @hpearnshaw in #95
• Bad data points for mid-October by @hpearnshaw in #96
• Early November by @bwgref in #97
• Bad data points for end of November by @hpearnshaw in #98
• Bad data points for early December by @hpearnshaw in #99
• Bad data points for mid-December by @hpearnshaw in #100
• Handle low-data GTI by @hpearnshaw in #101
• Bad data points for early January by @hpearnshaw in #102
• Bad data points for mid-January by @hpearnshaw in #103
• Bad points for end of January by @hpearnshaw in #104
• Bad data points for mid-February by @hpearnshaw in #105
• Bad points for end of February by @hpearnshaw in #106
• Bad points for early March by @hpearnshaw in #107
• Bad points for late March by @hpearnshaw in #108
• Bad points for early April by @hpearnshaw in #109
• Bad points for mid-April by @hpearnshaw in #110
• Bad points for mid-May by @hpearnshaw in #111
• Bad points for mid-June by @hpearnshaw in #112
• Bad points for beginning of July by @hpearnshaw in #113
• Bad points for mid-July by @hpearnshaw in #114
• Bad points for end of July by @hpearnshaw in #115
• Bad points for end of August by @hpearnshaw in #116
• Bad points for mid-September by @hpearnshaw in #117
• Bad points for end of September by @hpearnshaw in #118
• Bad points for mid-October by @hpearnshaw in #119
• Bad points for early November by @hpearnshaw in #120
• Bad points for end of November by @hpearnshaw in #123
• Bad points for mid-December by @hpearnshaw in #124
• Bad points for early January by @hpearnshaw in #125
• Bad points for mid-January by @hpearnshaw in #126
• Bad points for early February by @hpearnshaw in #127
• Bad points for mid-February by @hpearnshaw in #129
• Bad points for early March by @hpearnshaw in #130
• Bad points for mid-March by @hpearnshaw in #131
• Bad points for end of March by @hpearnshaw in #132
• New temperature model; testing with Git...

Use 4.9ms shift; better detrending

This version introduces

• an interactive clock offset cleaner, to eliminate bad ground station clock offset measurements "by eye" and check that the current model adequately models the clock offsets (#9)
• a shift of 4.9ms in the clock correction, based on the best-fit value measured with millisecond pulsars (#9, #15)
• a better detrending of the clock offset residuals, that leads to a more stable solution and better treatments of pulsars (#17)

v0.1

Release version before absolute timing shift.