Up to ten targets, one night: each gets its good/marginal/poor windows (darkness × altitude × Moon × clouds, as on the single-target page), then the night is handed out five minutes at a time to whichever target is best — with hysteresis, so you get a few solid blocks of at least 30 minutes, not a flicker. Targets that never win a block are listed with the reason.
Try: an autumn deep-sky night · ← previous night · next night →
Night of Wednesday, 23 September 2026 · astronomical night 20:49 → 05:37 (8.78 h) · Moon 92% (waxing gibbous) · weather: ERA5 history
Faded bands: each target's own windows (green good, amber marginal, pink poor). Dark blue: the schedule. Grey columns: twilight.
| local | target | hours | mean quality |
|---|---|---|---|
| 19:15–20:50 | — nothing worth pointing at — | 1.58 | |
| 20:50–05:05 | V1057 Cyg | 8.25 | 0.51 |
| 05:05–07:15 | — nothing worth pointing at — | 2.17 |
| target | astronomy | overall | best window | highest | Moon sep. | scheduled h |
|---|---|---|---|---|---|---|
| V1057 Cyg | 61 | 54 | 20:50–05:05 (marginal) | 87.3° at 22:10 | 58.5° | 8.25 |
curl -sS "https://devops.majbase.com/rozhen-planner/plan-api?targets=M31,M42,M45,NGC%207000&date=2026-09-23"targets: names or RA Dec, separated by commas, semicolons or newlines, at most ten. The response carries targets[] (score, verdict, best_window, windows, transit, moon_separation), schedule[] (blocks with target, start/end in UTC and local, hours, mean_quality; target: null is idle time), unscheduled[] with a why, forecast_source, warnings[]. Missing targets → 400 {"error", "code": "targets_missing"}.