Skip to content

Telescope runs calendar (issue #37) - #43

Draft
talister wants to merge 3 commits into
mainfrom
issue37-code-only
Draft

Telescope runs calendar (issue #37)#43
talister wants to merge 3 commits into
mainfrom
issue37-code-only

Conversation

@talister

Copy link
Copy Markdown
Collaborator

Change Description

  • My PR includes a link to the issue that I am addressing

Implements the telescope runs calendar feature (Stage 1 site/ephemeris
helper through classical-run ingest, LCO/Gemini observation-calendar sync,
campaign approval queue, and weather/storm cancellation handling).

Related to #37.

Replaces #41 (closed): that PR's diff had grown to 514 files / ~103k
insertions because it also carried the full .planning/ GSD workflow
history (428 files / ~82k insertions), which exceeded GitHub's diff
rendering limit and broke several review tools. This PR carries only the
86 files of actual code/template/docs/migration changes (~21k insertions).
The squashed .planning/ history is preserved on the issue37-planning-docs
branch for reference.

Solution Description

See docs/design/telescope_runs_calendar.rst for the design writeup.

Code Quality

  • I have read the Contribution Guide
  • My code follows the code style of this project
  • My code builds (or compiles) cleanly without any errors or warnings
  • My code contains relevant comments and necessary documentation

New Feature Checklist

  • I have added or updated the docstrings associated with my feature
  • I have added unit/End-to-End (E2E) test cases to cover my new feature

Squashed from issue37-telescope-runs-calendar (809 commits) to split the
GSD .planning/ documentation out of PR #41 for reviewable diff size. See
the issue37-planning-docs branch for the accompanying planning artifacts.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@talister talister mentioned this pull request Jul 17, 2026
21 tasks
talister added a commit that referenced this pull request Jul 18, 2026
Raised while splitting PR #41/#43: design docs and demo notebooks existed
for the telescope-runs-calendar management commands, but no general,
discoverable how-to-run documentation did. Tracked as a phase so it's
scoped and planned before v2.1 milestone close, not left as an afterthought
again (see CLAUDE.md's paired-notebook incident history for the pattern
this is meant to avoid repeating).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
talister and others added 2 commits July 19, 2026 00:31
Folds in code/template/docs changes made on issue37-telescope-runs-calendar
since the original squash point (47dcfb9): the operator/usage runbook
(docs/installation.rst, docs/notebooks.rst, docs/runbooks/), the
backfill_range_calendar_events management command (Phase 25's fix for
range-window CalendarEvent projection), and the PR-review fixes from quick
task 260718-dih (guarded calendar-sync loop in _set_run_status, fail-fast
cross-month rejection, anchored partial-night token matching).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Backfills FOMO ObservationRecords for LCO RequestGroups submitted directly
at the LCO observing portal (outside the TOM), by proposal and RequestGroup
name prefix, matching each request's target against a chosen campaign
TargetList's members.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant