AI-generated illustration for Galileo Whispers of a generic visual-observing setup. It shows no actual variable-star field, comparison sequence or measured brightness limit; a non-detection requires secure identification and a usable comparison star.
When a variable star is too faint to see in a securely identified field, record a fainter-than limit based on a usable comparison star, rather than assigning the unseen target an exact magnitude. The record says how deep that observation reached under those conditions. It does not say that the star vanished or that its magnitude equals the limit.
The AAVSO’s March 2013 visual-observing manual gives a specific example: if the faintest visible comparison is magnitude 11.5 and the variable is not visible, the report is written as <11.5. In this observing convention the bracket means “fainter than,” despite the direction in which the numerical magnitude scale runs.
First establish that you are looking in the right place
A missing target only becomes informative after identification. Use an appropriate chart, confirm its orientation and match several surrounding stars. Check the variable’s position rather than assuming the brightest nearby point must be the target.
The British Astronomical Association’s 2019 observing introduction stresses correct field identification and the use of a recognized comparison sequence. A field that cannot be matched to the chart is an identification problem. It cannot supply a reliable brightness limit for a particular star.
Next identify which labeled comparisons are actually visible, using the same setup and conditions as the target search. A telescope’s advertised limiting magnitude is not a measurement of tonight’s field. Moonlight, haze, local glare and the observer’s visual state can change what is detectable.
Preserve the difference between absence and a measured brightness
A positive estimate compares light that you judge to be the variable with comparison stars. A non-detection supplies a boundary: the target was not detected while a specified comparison was seen. It leaves a range of possible fainter values.
If the field is secure and comparison 11.5 is usable, a target at 12.0 or 14.0 could both be consistent with the same <11.5 visual report. Those possible magnitudes are examples, not an inference that the target had either value. The observation alone does not choose between them.
Conversely, if clouds obscure the target’s location while leaving a comparison in another part of the field visible, their conditions are not comparable. Merely finding one faint star somewhere in the eyepiece is insufficient. Record the obstruction or failed attempt instead of presenting it as a calibrated non-detection.
Why the bracket appears to run backward
Larger magnitude numbers mean fainter objects. A star fainter than magnitude 11.5 would therefore have a numerical magnitude greater than 11.5, if an appropriate magnitude could be measured. Yet the AAVSO convention uses the left-pointing bracket for a fainter-than report.
Read <11.5 as an observing flag with its stated meaning. It is not a request to solve the mathematical inequality “magnitude less than 11.5.” In flux language, the observation places an upper boundary on the detectable light from the target; in magnitude language, the permitted values run toward larger numbers.
This is why omitting the bracket is consequential. The AAVSO’s September 2024 account of vetting T CrB observations describes how a missing fainter-than symbol can turn a non-detection into an apparent positive measurement. An unseen target reported as 11.5 would falsely appear to have been measured at that magnitude.
Build a record someone else can interpret
For a hypothetical observation, a useful notebook entry might say: target field confirmed; variable not seen; comparison labeled 115 visible; fainter-than limit 11.5; chart identifier recorded; telescope and eyepiece recorded; observation time and time convention recorded; thin haze noted. These are illustrative fields, not an observation made by Galileo Whispers.
The comparison label 115 denotes magnitude 11.5 on the manual’s decimal-omitted chart convention. Preserve the chart and comparison identity so the basis of the limit can be checked. If submitting the record, retain the fainter-than designation in the reporting system rather than placing the number alone in a magnitude field.
The manual also recommends retaining original records and marking doubtful estimates with the reasons for doubt. A later correction should preserve what changed. Replacing an inconvenient limit with the star’s expected brightness would destroy information about what was actually established.
A visual limit has its own uncertainty
A threshold judged by eye is not automatically a formal three-sigma or five-sigma detection boundary. Those statistical statements require a defined noise model and measurement procedure. Do not attach them to a visual estimate merely because they sound more precise.
An earlier AAVSO discussion of reporting errors, in the July 2010 newsletter, also emphasizes that identity errors and omitted brackets can completely change the scientific meaning of a record. Accurate labeling matters as much as writing another decimal place.
A non-detection can constrain whether a bright outburst had occurred by a particular time, or show that a target remained below an observer’s reach. Its value comes from the honest boundary and its context. The useful result is “not detected to this limit under these conditions,” with enough detail to understand what the observation could and could not have seen.
