The problem in #267 (in sector 65, camera 4, ccd 4) happens in other cases as well, including sector 78, camera 4, ccd 4 (e.g., TIC 468524320).
This PR provides a general fix, a general version of the sector 65 fix at 05e8e8db9eab865dcfa632406cc1eab3cc3b756b.
When there is a cadence mismatch, the PR:
re-calculates quality flag
re-calculates ffi index
re-calculates CBV, and saves the updated version in ~/.eleanor/metadata for future use (for the specific sector-camera-ccd)
The re-calculation is based on the similar logic in update.py. The codes should probably be re-factorized so that the logic is centralized in one place (rather than having multiple functionally identical copies, especially in light of the tweaks going to be needed to accommodate sectors 83+ data).
The problem in #267 (in sector 65, camera 4, ccd 4) happens in other cases as well, including sector 78, camera 4, ccd 4 (e.g., TIC 468524320).
This PR provides a general fix, a general version of the sector 65 fix at 05e8e8db9eab865dcfa632406cc1eab3cc3b756b.
When there is a cadence mismatch, the PR:
~/.eleanor/metadata
for future use (for the specific sector-camera-ccd)The re-calculation is based on the similar logic in
update.py
. The codes should probably be re-factorized so that the logic is centralized in one place (rather than having multiple functionally identical copies, especially in light of the tweaks going to be needed to accommodate sectors 83+ data).cc @vbkostov