Correct known timestamp offset

[rhandberg]

Pull request fixing issue #15. Should not be merged before the final processing of Data Release 5 is done, since it could (potentially) mix things up.

[codecov[bot]]

Codecov Report

Merging #17 into devel will increase coverage by 0.48%. The diff coverage is 100.00%.

@@            Coverage Diff             @@
##            devel      #17      +/-   ##
==========================================
+ Coverage   79.92%   80.40%   +0.48%     
==========================================
  Files          25       27       +2     
  Lines        3556     3619      +63     
==========================================
+ Hits         2842     2910      +68     
+ Misses        714      709       -5     

Impacted Files	Coverage Δ
photometry/BasePhotometry.py	94.32% <100.00%> (+0.02%)	:arrow_up:
photometry/catalog.py	79.24% <100.00%> (ø)
photometry/fixes/__init__.py	100.00% <100.00%> (ø)
photometry/fixes/time_offset.py	100.00% <100.00%> (ø)
photometry/prepare.py	85.21% <100.00%> (+0.16%)	:arrow_up:
photometry/utilities.py	75.40% <100.00%> (+2.95%)	:arrow_up:
photometry/image_motion.py	94.51% <0.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 26efb7f...27f6e0c. Read the comment docs.

[rhandberg]

We still need to implement tests of:

• [x] Sector 21 FFI timestamps.
• [x] Sector <20 FFI timestamps (requires Data Release 30 to be made available).