Astronomy · Observations as evidence
Keeping an observation record
Make a sky record that another person—and your future self—can interpret. Preserve what happened, how you observed it and which parts remain uncertain.
Continue in the approved chapter order. Necessary vocabulary, quantities and assumptions are explained in the lesson.
Back to the chapterAfter reading, you can
- Construct a record that identifies the target, time, location, method and observing conditions.
- Keep direct observations, processing choices and interpretations distinguishable.
- Correct a record without losing the original evidence.
A useful record lets someone return to your question
Imagine finding this note a month later: “The bright one was fainter tonight.” Which object was bright? Fainter than what? At what time, through which instrument and under what conditions? The note preserves an impression, but it leaves several investigations impossible. A useful observation record supplies enough context to understand the comparison.
You do not need a complicated database to begin. A notebook, an accessible text document or a simple table can work. Choose a method you can use while observing and preserve the original entries. The purpose is not to make the page look scientific. It is to make the route from the sky to the claim recoverable.
Record your question too. A sketch intended to compare a pattern's orientation may not have the detail needed to measure brightness. An image taken for a colour illustration may have processing that prevents quantitative comparison. Identifying the purpose helps another reader understand both the value and limits of the record.
Identify the observation before interpreting it
Begin with the target or field, date and time with its stated time system, observing location and method. A target name should lead back to an identifiable object or chart. If you are unsure of the identity, say so and include enough field detail for someone else to check it. Guessing a confident name makes a record less useful.
Describe what you used: unaided eyes, binoculars, a telescope, or an archived image. For an image include the original filename, exposure information and relevant filter or band if available. A filter selects a range of wavelengths; measurements in different bands do not necessarily describe the same part of a source's emission. For a sketch record its orientation, field reference and whether the drawing's scale is measured or approximate.
Describe conditions that could affect the result: cloud or haze, background light, obstructions, interruptions and any difficulty identifying the field. “Uncertain because thin cloud crossed the target” conveys useful information. Do not replace it with an unexplained extra decimal place. You can improve the numerical analysis later only if the conditions remain available.
| Field | Example entry | Why it matters |
|---|---|---|
| Question | Does point X move relative to the three reference stars? | Defines the comparison |
| Target and field | X is an unidentified point; attached labelled field sketch | Keeps an uncertain identification explicit |
| Time | 2026-10-18, 20:10–20:20 UTC; clock checked before the session | Preserves date, interval and stated clock context |
| Place and method | Same fixed observing position; unaided sketches every two minutes | Explains viewpoint and method |
| Conditions | Thin cloud from 20:14; reference star C no longer visible | Identifies a possible loss of sensitivity |
| Result | No change confidently resolved before cloud; later position uncertain | Separates limited evidence from absence of motion |
A time needs its date and convention
An entry reading “10:15” is incomplete. It could mean morning or evening, local civil time or another time system, and one of two dates during a session crossing midnight. Use an unambiguous date and a stated convention. UTC means Coordinated Universal Time. Preserve the original local timestamp and its recorded UTC offset if you convert it later.
In a simple arithmetic example, a recorded local time of 01:10 on 19 October at a declared fixed offset UTC+03:00 corresponds to 22:10 UTC on 18 October. Subtracting three hours crosses midnight, so the date changes too. The offset here is supplied by the example; it is not a rule for every observing location or season.
For ordinary introductory logging, a clearly stated UTC time and an honest clock-accuracy note make comparisons much easier. Precise astronomical timing can require additional time standards, exposure-midpoint definitions and corrections for the observer's changing position. Do not silently label an ordinary wall-clock time as one of those corrected quantities. The later timing lessons develop those distinctions.
Keep record, processing and explanation in separate layers
The original layer contains the sketch, file or instrument output and the conditions noted at the time. A processing layer describes operations such as background subtraction, orientation changes or combining exposures. An interpretation layer proposes what caused the result. You may keep all three together in a notebook, but label them so they do not merge into one story.
Suppose you rotate a photograph to place north at the top. That may improve comparison, but keep the original file and record the transformation. Suppose you subtract a background estimate before measuring a star. Save the choice of aperture and the background region. A later reader should be able to distinguish what the instrument recorded from what the analysis changed.
Do not add detail to a sketch because a reference image shows that it should have been there. You can annotate “identified later using chart Y”, but preserve the original uncertain mark. A prediction and an observation can agree; they still need to remain separate enough that a disagreement could be recognised.
Correct errors without erasing their history
Mistakes are normal. You may discover that a clock was offset or a target was misidentified. Add a dated correction explaining what changed and why; retain the original entry. In a digital record, keep a version history or a separate correction note. An unexplained replacement hides information about how the conclusion developed.
For example: “Correction added 20 October: the original file timestamp used local time at the recorded UTC+03:00 offset; converted time is 22:10 UTC on 18 October. Original filename and timestamp retained.” This makes the correction understandable without suggesting that the corrected time was what you wrote at the telescope.
A record with a transparent correction can be more trustworthy than a polished page with no recoverable history. The standard is not that an observer never errs. It is that evidence and corrections remain available for checking.
An unsuccessful attempt can still explain the evidence
A target obscured by cloud is not a measured zero signal. A field you could not identify is not a secure non-detection of its star. Note what prevented the intended observation and whether reference objects remained visible. The resulting limit may be weak, but it can explain why a gap appears in a sequence.
Before closing the record, ask whether another person could identify the field, place the event in time, understand the method and separate what you saw from what you inferred. You can test your own answer tomorrow by reading the entry without relying on memory. Fill a missing contextual detail only when you can recover it honestly; otherwise keep the gap marked as unknown.
Worked example
Repair a note without inventing its missing evidence
An old note reads “X dim at 10:15, cloudy”. The original photograph survives with a date, camera metadata and a chart label. What can you improve?
- Link the note to the original file and chart without replacing either.
- Recover the date and recorded camera settings from the original metadata, noting their source.
- Check whether the camera's time convention is actually known. If it is unknown, retain that uncertainty rather than guessing an offset.
- Keep “cloudy” and any doubt about the visual comparison. A better filename does not retroactively create a calibrated brightness measurement.
You can recover documented context and label its origin. You cannot reconstruct a precise brightness or time convention that the surviving evidence does not contain.
Try the reasoning
At a declared fixed offset UTC+02:00, a recorded local timestamp is 00:30 on 5 May. What is its UTC timestamp?
Show the answer and reasoning
22:30 UTC on 4 May.
Subtract two hours and carry the date backwards across midnight. The fixed offset is part of the question, not an assumption about a country.
You discover a target was misidentified. Should you overwrite its name without comment?
Show the answer and reasoning
No. Retain the original identification and add a dated correction with its supporting evidence.
The correction changes how the original record is interpreted. Keeping that history makes the change reviewable.
Cloud hides the target and two nearby reference stars. What is a defensible record?
Show the answer and reasoning
The intended observation was limited by cloud; the target was not reliably detected under those conditions.
The record documents loss of visibility. It does not establish the target emitted no light or vanished.
What to carry forward
- A useful record carries identity, time, place, method, conditions and uncertainty.
- Preserve original data separately from processing and physical interpretation.
- Make corrections explicit and keep failed attempts interpretable.
References
Teaching resources and research supporting this lesson’s explanations and examples.
- Manual for Visual Observing of Variable StarsAAVSO · edited by Sara J. BeckCourse notes · PDF
- Definition of the Flexible Image Transport System (FITS), Version 4.0International Astronomical Union FITS Working Group; NASA FITS Support Office hostingReference guide · PDF
- barycorr — Generalized multi-mission barycenter correction toolNASA HEASARC / HEASoftReference guide