← single target

Rozhen Night Plan

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 Thursday, 04 May 2034 · astronomical night 22:11 → 04:23 (6.19 h) · Moon 98% (full moon) · weather: none — the schedule is astronomy only; overall conditions unknown

3C 2733C 273 20:55–21:35: quality 0.13C 273 21:35–22:15: quality 0.33C 273 22:15–23:30: quality 0.63C 273 23:30–01:40: quality 0.53C 273 01:40–02:45: quality 0.43C 273 02:45–03:10: quality 0.33C 273 03:10–03:20: quality 0.2observe 3C 273 21:35–22:10observe 3C 273 22:15–03:00schedule3C 2733C 27322:0000:0002:0004:0006:00

Each row is the target's quality through the night, white → amber → green for 0 → 0.3 → 0.6 → 1 (the same thresholds as poor / marginal / good). Dark blue: the schedule. Grey columns: twilight.  Download: schedule CSV · targets CSV · JSON

Schedule

localtargethoursmean quality
20:20–21:35 — nothing worth pointing at — 1.25
21:35–22:10 3C 273 0.58 0.3
22:10–22:15 — nothing worth pointing at — 0.08
22:15–03:00 3C 273 4.75 0.49
03:00–06:15 — nothing worth pointing at — 3.25

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
3C 273 40 unknown 22:15–03:00 (marginal) 50.2° at 23:00 53.9° 5.33

💡 API
curl -sS "https://devops.majbase.com/rozhen-planner/plan-api?targets=M31,M42,M45,NGC%207000&date=2034-05-04"

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"}; an unreadable date → 400 {"error", "code": "invalid_date"}.