docs and landing: photometry runs, and how to use the differential curve
The landing page still listed photometry as being built and the setup guide stopped at the raw curve. Both were true this morning. The landing copy now says astrometry is the one unbuilt stage, that photometry does not wait on it because most acquisition software plate-solves at capture, and that the magnitudes are instrumental. De-slopped per the standing rule: clean on the pattern catalog, no em dashes, no tier words. The guide gains a section on choosing comparison stars, which is the part that decides whether a differential curve means anything. It says what the scatter test is for in the terms that matter to an observer: a variable comparison puts its own variation into every point with the sign flipped, so the target appears to vary in antiphase with a star nobody was looking at. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
fa25043da7
commit
def8e518e2
@@ -51,16 +51,16 @@ const NIGHT_STAGES = [
|
||||
},
|
||||
];
|
||||
|
||||
// The reduction pipeline, and which parts of it run today. Listing the two
|
||||
// unbuilt stages here is deliberate: someone who uploads a night and finds no
|
||||
// plate solve should have read about it on this page first.
|
||||
// The reduction pipeline, and which parts of it run today. Naming the unbuilt
|
||||
// stage here is deliberate: someone who uploads a night and finds no plate
|
||||
// solve should have read about it on this page first.
|
||||
const PIPELINE = [
|
||||
{ stage: 'Header', what: 'Reads the FITS and fills in what the camera recorded', state: 'runs' },
|
||||
{ stage: 'Calibrate', what: 'Builds and applies master bias, dark and flat frames', state: 'runs' },
|
||||
{ stage: 'Extract', what: 'Finds the sources, and measures the frame they sit in', state: 'runs' },
|
||||
{ stage: 'Timing', what: 'Mid-exposure UTC to BJD_TDB at the barycentre', state: 'runs' },
|
||||
{ stage: 'Astrometry', what: 'Plate solve to a stored WCS', state: 'building' },
|
||||
{ stage: 'Photometry', what: 'Aperture and differential magnitudes', state: 'building' },
|
||||
{ stage: 'Photometry', what: 'Aperture magnitudes with error bars, and differential light curves', state: 'runs' },
|
||||
];
|
||||
|
||||
const FEATURES = [
|
||||
@@ -314,9 +314,15 @@ function goToNox() {
|
||||
</li>
|
||||
</ul>
|
||||
<p class="lp-pipeline-note">
|
||||
Astrometry and photometry are the two stages still being built. Until they land the
|
||||
pipeline marks them unbuilt on the frame, rather than leaving you to work out why a
|
||||
number never appeared.
|
||||
Astrometry is the one stage still being built. Until it lands the pipeline marks it
|
||||
unbuilt on the frame, rather than leaving you to work out why a number never
|
||||
appeared. Photometry does not wait on it: most acquisition software plate-solves at
|
||||
capture and writes the solution into the header, and the pipeline keeps that.
|
||||
</p>
|
||||
<p class="lp-pipeline-note">
|
||||
The magnitudes are instrumental. They compare your own frames in one filter to each
|
||||
other, which is what a variable star or a transit needs; comparing them to a
|
||||
catalogue waits on photometric standardisation.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@@ -206,6 +206,30 @@ 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.
|
||||
|
||||
### Differential photometry
|
||||
|
||||
The raw curve still carries the sky. Extinction, thin cloud and changes in
|
||||
transparency move every star in the frame together, and on most nights that
|
||||
motion is larger than anything you are trying to measure.
|
||||
|
||||
Open **Comparison stars** under the chart and press **Suggest comparison
|
||||
stars**. Each candidate is scored on how much its own magnitude moves across
|
||||
the very frames your curve is built from, compared with how much its error bars
|
||||
say it should. A star that moves more than three times its own errors is
|
||||
variable, and the list says so and does not offer it: a variable comparison
|
||||
puts its own variation into every point of your curve with the sign flipped, so
|
||||
your target appears to vary in antiphase with a star nobody was looking at.
|
||||
|
||||
Candidates are also rejected for being absent from some frames, for saturating
|
||||
in any of them, and for sitting more than two magnitudes from the target. Each
|
||||
rejection says which, so you can see why the obvious bright star nearby was
|
||||
passed over.
|
||||
|
||||
Add two or three, tick **Show the differential curve**, and the atmosphere
|
||||
divides out. Frames missing any comparison are dropped from the differential
|
||||
series rather than measured against a smaller ensemble, and the count of what
|
||||
was dropped sits under the chart.
|
||||
|
||||
## The scheduler
|
||||
|
||||
Nothing to run. Open **Observe** and it ranks candidate targets for the
|
||||
|
||||
Reference in New Issue
Block a user