IT Consulting

← 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 Wednesday, 31 January 2029 · astronomical night 19:10 → 05:57 (10.78 h) · Moon 96% (waning gibbous) · weather: none — the schedule is astronomy only; overall conditions unknown

V1057 CygV1057 Cyg 18:05–18:40: quality 0.1V1057 Cyg 18:40–19:15: quality 0.3V1057 Cyg 19:15–19:25: quality 0.5V1057 Cyg 19:25–19:30: quality 0.4V1057 Cyg 05:45–06:00: quality 0.4V1057 Cyg 06:00–06:10: quality 0.2V1057 Cyg 06:10–06:35: quality 0.3V1057 Cyg 06:35–07:05: quality 0.1observe V1057 Cyg 18:40–18:55observe V1057 Cyg 19:15–19:30observe V1057 Cyg 05:45–06:00observe V1057 Cyg 06:30–06:35schedule18: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
17:35–18:40 — nothing worth pointing at — 1.08
18:40–18:55 V1057 Cyg 0.25 0.33
18:55–19:15 — nothing worth pointing at — 0.33
19:15–19:30 V1057 Cyg 0.25 0.45
19:30–05:45 — nothing worth pointing at — 10.25
05:45–06:00 V1057 Cyg 0.25 0.4
06:00–06:30 — nothing worth pointing at — 0.5
06:30–06:35 V1057 Cyg 0.08 0.31
06:35–07:35 — nothing worth pointing at — 1.0

Targets

targetastronomyoverallbest windowhighestMoon sep.scheduled h
V1057 Cyg 8 unknown 19:15–19:30 (marginal) 87.3° at 12:35 126.6° 0.83
💡 API 
curl -sS "https://devops.majbase.com/rozhen-planner/plan-api?targets=M31,M42,M45,NGC%207000&date=2029-01-31"

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