Following #375 and #376, when a planet scan is delayed by a gap move, it gets cut and there is an empty spot in the schedule. Since CMB scans are filtered out before this happens, there is nothing to fill the gap. Example SATp2 config where this happens:
t0: 2026-05-19T17:14:00+00:00
t1: 2026-05-20T17:14:00+00:00
make_table: True
make_plots: True
state_mode: False
platform_cfg_path: ${PLATFORM_CFG_DIR}/satp2_cfg.yaml
cmb_plan: ${SAT_SCHED_IN_DIR}/20260417_SATp2_j2026-04-01T00:00:00+00:00_n365_e60_d-40,-10_a45_w50.txt
cal_plan: ${SAT_SCHED_IN_DIR}/20260427_satp2_dense_calibration_plan.txt
wiregrid_plan: NULL # ${SAT_SCHED_IN_DIR}/20260417_SATp2_j2026-04-01T00:00:00+00:00_n365_e60_d-40,-10_a45_w50_wiregrid.txt
Following #375 and #376, when a planet scan is delayed by a gap move, it gets cut and there is an empty spot in the schedule. Since CMB scans are filtered out before this happens, there is nothing to fill the gap. Example SATp2 config where this happens: