Make the merged repository coherent: README, state, and internal links
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.
This commit is contained in:
parent
87387064c5
commit
59d6e30712
6 changed files with 160 additions and 28 deletions
|
|
@ -1,4 +1,4 @@
|
|||
# astro-pipeline
|
||||
# pipeline
|
||||
|
||||
Processing and analysis code for remote-telescope imaging sessions, starting
|
||||
with iTelescope data from the [itelescope](https://git.discworld.casa/laurence/itelescope)
|
||||
|
|
@ -11,7 +11,7 @@ done to them.
|
|||
|
||||
## What is here now
|
||||
|
||||
`session-scripts/` - the 50 scripts that processed the NGC 5128 session of
|
||||
`pipeline/` - the 50 scripts that processed the NGC 5128 session of
|
||||
2026-07-21, exactly as they were run, plus the shared `layout.py` that tells
|
||||
them where files live. This is a working record rather than a finished product:
|
||||
the scripts were written in sequence as the work went along, several of them by
|
||||
|
|
@ -19,21 +19,15 @@ parallel agents, and they show it. They are kept because they are the honest
|
|||
provenance of a set of published results, and because the productionised
|
||||
pipeline should be able to reproduce those results exactly.
|
||||
|
||||
`session-scripts/restructure.py` - reorganises a flat session directory into the
|
||||
`pipeline/restructure.py` - reorganises a flat session directory into the
|
||||
named layout below. Idempotent, dry run by default.
|
||||
|
||||
`observing/` - plans for observing sessions that are not remote-telescope runs.
|
||||
Currently the total solar eclipse of 12 August 2026, seen from Menorca. These
|
||||
live here rather than in a notes app because they are worked out from real
|
||||
numbers, they get revised as the date approaches, and the reasoning behind each
|
||||
decision is worth keeping.
|
||||
|
||||
## Pointing the scripts at a session
|
||||
|
||||
```
|
||||
set ASTRO_SESSION=D:\astro\NGC5128\20260721 # Windows
|
||||
export ASTRO_SESSION=/data/astro/NGC5128/20260721 # POSIX
|
||||
python session-scripts/layout.py # prints the resolved layout
|
||||
python pipeline/layout.py # prints the resolved layout
|
||||
```
|
||||
|
||||
`layout.py` maps a **filename** to its subdirectory, so a script asks for
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue