Windows are coarse scheduling bounds. t0 is usually BJD_TDB; when the target's coordinates are known, transit centers are corrected to true UTC before scheduling. Without coordinates, the ≤9 min BJD_TDB/UTC offset falls back to being absorbed by the padding above.
Window boundaries are always rounded to 5-minute intervals. When padding is 0 the rounded window may be slightly shorter than the transit visibility (floor for start, ceil for end). Verify for critical observations.
These scheduling inputs are separate from the archive page.
One LCO request per ticked transit, following the plan chosen in its row (a relay is two requests). Each request is drafted, checked with LCO and submitted on its own; set each one's instrument and name here, and the shared settings under Imaging Request.
Tick transits in the windows table to list their requests here.
Requests are independent bookings: if one fails after others are booked, the booked ones stay booked (a relay can end up with one leg). There is no automatic cancellation.
Accepted requests are checked after their observing window. Final BANZAI products are downloaded incrementally; scan and database ingestion start after every raw frame has a level-91 counterpart.
| Request | Target | Instrument | LCO state | Pipeline | Frames | Last update | Detail | Action |
|---|---|---|---|---|---|---|---|---|
| Loading… | ||||||||