docs: photometry has a worker now
The doc said two stages had none and nothing carried a magnitude. Both were true when written this morning and are not now, and a setup guide that understates what exists sends an operator looking for something they already have. Adds what photometry needs before it will run — gain in electrons per ADU, read noise, full well — and why the header's GAIN is deliberately not a fallback for the first of those. Astrometry is still unbuilt, and the entry now says why that does not block photometry. Compose picks up the photometry stage. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
ec9f5c3500
commit
e998adfba9
+1
-1
@@ -105,7 +105,7 @@ services:
|
||||
# Only the stages this build implements. Leaving it unset would have the
|
||||
# worker claim astrometry and photometry too, and fail every one of them
|
||||
# as unimplemented, which looks like a broken queue.
|
||||
CAELUM_WORKER_STAGES: ${CAELUM_WORKER_STAGES:-timing,calibrate,extract}
|
||||
CAELUM_WORKER_STAGES: ${CAELUM_WORKER_STAGES:-timing,calibrate,extract,photometry}
|
||||
# Cross-check solved frames against Gaia after extraction. Off by
|
||||
# default: it reaches the network on every frame and leans on a public
|
||||
# catalogue service.
|
||||
|
||||
@@ -83,7 +83,7 @@ CAELUM_WORKER_TOKEN=cae_... docker compose --profile reduction up -d
|
||||
| `CAELUM_API_URL` | required | No trailing slash needed |
|
||||
| `CAELUM_WORKER_TOKEN` | required | Must start with `cae_` |
|
||||
| `CAELUM_WORKER_ID` | hostname | Appears on claims and in logs |
|
||||
| `CAELUM_WORKER_STAGES` | all implemented | `timing,calibrate,extract` |
|
||||
| `CAELUM_WORKER_STAGES` | all implemented | `timing,calibrate,extract,photometry` |
|
||||
| `CAELUM_POLL_INTERVAL` | 5 | Seconds between empty claims |
|
||||
| `CAELUM_MIN_MASTER_FRAMES` | 5 | Floor for combining a master |
|
||||
| `CAELUM_ASTROMETRY_CHECK` | off | Cross-check solved frames against Gaia |
|
||||
@@ -179,6 +179,33 @@ The last two are what you want to see. "Has not polled recently" is the state
|
||||
worth watching for: a bridge that stops polling writes no error anywhere, and
|
||||
that page is the only place it shows.
|
||||
|
||||
### Measuring something
|
||||
|
||||
Photometry needs two things the archive cannot work out for itself, so it
|
||||
declines to run until you supply them. Set them on the camera in Settings:
|
||||
|
||||
| Field | What it is |
|
||||
| --- | --- |
|
||||
| `gain_e_per_adu` | Electrons per ADU, the FITS `EGAIN` |
|
||||
| `read_noise_e` | Read noise in electrons, at the gain you observe at |
|
||||
| `saturation_adu` | Full well in ADU, above which the sensor stops being linear |
|
||||
|
||||
`gain_e_per_adu` is not the CMOS `GAIN` setting. That one is a camera menu
|
||||
number, commonly 0 or 100 or 120, and is not a conversion factor at all. Using
|
||||
it would scale every uncertainty by about a hundred, in the direction that
|
||||
makes the data look better. That is why the header's `GAIN` is deliberately
|
||||
not a fallback here.
|
||||
|
||||
Without the gain and the read noise there is no uncertainty, and a magnitude
|
||||
without an error bar is refused, not stored. The stage names the missing field
|
||||
and stops there.
|
||||
|
||||
Then open **Analysis**, search a target, and the light curve is at the bottom.
|
||||
Under it are four counts: how many frames exist, how many are solved, how many
|
||||
are measured, how many landed on the target. A curve of nine points drawn from
|
||||
two hundred frames is a different claim from nine drawn from nine, and the plot
|
||||
alone does not distinguish them.
|
||||
|
||||
## The scheduler
|
||||
|
||||
Nothing to run. Open **Observe** and it ranks candidate targets for the
|
||||
@@ -240,14 +267,21 @@ behaviour, correct error reporting. That covers the adapter's logic. A mount is
|
||||
a separate question, so before pointing this at equipment, run it against
|
||||
ASCOM's own Alpaca simulator drivers: a real server, not our idea of one.
|
||||
|
||||
**Two of the six pipeline stages have no worker.** Astrometry needs a solver
|
||||
and Gaia index files running to tens of gigabytes. Photometry needs the source
|
||||
catalogues, which now exist, and cross-telescope comparison additionally needs
|
||||
photometric standardisation. Frames sit at `reducing` until those land, and the
|
||||
**Astrometry has no worker.** It needs a solver and Gaia index files running
|
||||
to tens of gigabytes. Frames sit at `reducing` until that lands, and the
|
||||
reduction panel labels each unbuilt stage.
|
||||
|
||||
**Nothing carries a magnitude.** The Analysis page says so where a light curve
|
||||
would go, and says what unblocks it.
|
||||
That does not block photometry, which measures sky positions from a WCS the
|
||||
frame already carries. Most acquisition software plate-solves at capture time
|
||||
and writes the solution into the header. A frame that arrives unsolved stays
|
||||
unsolved, and the light curve counts it as excluded rather than leaving it out
|
||||
of the total.
|
||||
|
||||
**The magnitudes are instrumental.** `-2.5 log10(flux per second)`, no zero
|
||||
point. Two frames from the same telescope and filter compare to each other,
|
||||
which is what a variable star or a transit needs. Comparing them to a catalogue
|
||||
magnitude, or to another telescope, needs photometric standardisation. That is
|
||||
not built.
|
||||
|
||||
`docs/verifying-accuracy.md` records what each measurement is checked against,
|
||||
how good that reference is, and what each check has caught.
|
||||
|
||||
Reference in New Issue
Block a user