laurence
59d6e30712
The mechanical merge preserved both histories but left two repositories sitting side by side rather than one repository. This is the part that makes it whole. A top-level README explains the three strands - the telescope network and campaign, the processing code, and in-person observing plans - and says plainly that image data does not live here, because that is the first question anyone will have when they find a pipeline with no pixels. state/PROJECT.md was still describing a markdown-only reference project whose scope explicitly EXCLUDED automating bookings and image processing. Both of those are now most of what the project does, so the objective, scope and key facts are rewritten to match reality. state/DECISIONS.md records why the merge happened - the two repos were split by chronology rather than design, and the seam was already leaking, with the campaign's TODO citing results held in the other repo and the pipeline's README explaining a campaign it did not contain. It also records that the image data deliberately stays out of the repository. state/TODO.md gains the pipeline and observing work that previously had nowhere to live, including the measurement that changes the pipeline plan: per-frame processing is 2.9 seconds and the whole 24-frame session is 1.1 minutes single-threaded, so a scheduler earns nothing on stacking and should be pointed at the Monte Carlo stages instead. Internal links fixed for the new paths: pipeline/README.md referred to session-scripts/ throughout, and itelescope/README.md pointed at a state/ directory that is now one level up. The .gitignore conflict between the two repositories is resolved by combining them, with image formats ignored globally except under docs/, where documentation figures are committed deliberately. |
||
|---|---|---|
| .. | ||
| data | ||
| plans | ||
| CAMPAIGN.md | ||
| README.md | ||
| TARGETS.md | ||
| TELESCOPES.md | ||
itelescope
Reference and review of the iTelescope.net remote telescope network: every telescope, its specs, what it is good at, and which one to book for a given target.
- TELESCOPES.md: the full review, grouped by observatory, with a "choosing a telescope" guide at the end.
- TARGETS.md: southern-sky targets invisible from the UK, matched to scopes and to the time of year to book them.
- data/itelescope-telescopes.csv: snapshot of the network's maintained specs sheet (source of truth for the numbers).
- ../state/: project state under the Default Workflow, covering this repository as a whole.
Sources: the iTelescope support article (telescope summary) and the network's maintained Google Sheet. The launchpad at go.itelescope.net is login-only.