← 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 Tuesday, 30 December 2036 · astronomical night 18:39 → 06:07 (11.47 h) · Moon 94% (waxing gibbous) · weather: none — the schedule is astronomy only; overall conditions unknown

M42M42 19:35–19:40: quality 0.1M42 19:40–22:30: quality 0.2M42 22:30–02:40: quality 0.3M42 02:40–03:10: quality 0.2observe M42 01:15–02:15scheduleM4218:0020:0022: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
16:55–01:15 — nothing worth pointing at — 8.33
01:15–02:15 M42 1.0 0.31
02:15–07:50 — nothing worth pointing at — 5.58

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
M42 Great Orion Nebula 16 unknown 01:15–02:15 (marginal) 42.9° at 23:20 26.9° 1.0

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

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"}.