StellarPix
← Back to Learn
ProcessingPublic tutorial · No membership required12 min read · measurement takes extra time

Inspect and Select Light Frames with Blink and SubframeSelector

Catch obvious exposure problems visually, compare star-quality measurements, and build an approved light-frame list for WBPP. Learn why calibrated review copies matter and why one rejection threshold cannot suit every dataset.

Sources reviewed October 25, 2026

A visual check and a measurement check

Blink lets you step through exposures and spot clouds, tracking failures, focus changes, or framing problems. SubframeSelector measures properties such as star size and shape so you can identify frames worth a closer look. Use the measurements alongside the images rather than letting one number make every decision.

Before the full WBPP run, use Blink for an initial check of the raw lights. For reliable SubframeSelector measurements, use correctly calibrated linear review copies; for a color camera, use the corresponding debayered copies. PixInsight staff explain that uncorrected hot pixels can be misidentified as stars in raw images.

That means the measured review stage comes after calibration, even though selection happens before the final registration and stacking run. This lesson uses a preliminary WBPP calibration pass, then carries the decisions back to an approved list of original raw lights. Keep those two file sets clearly separate.

1. Preserve originals and define a comparison group

Keep all original exposures unchanged. Make a small selection log with source path, filename, filter, exposure, decision, and reason. Use full paths if different sessions contain repeated filenames.

Start with one target, camera configuration, filter, exposure time, and binning. Repeat the review for other groups. A narrowband exposure and a broadband exposure can have very different star counts and backgrounds without either being defective.

Note changes of session, image scale, gain, or readout mode. These can affect measurements. Do not rank unlike groups together and automatically discard the faintest filter or the shorter exposures.

For practice, choose a manageable representative group. Include several normal exposures and any suspected failures so you can learn what their measurements look like.

2. Inspect raw lights with Blink

Find Blink through All Processes, usually under ImageInspection. Load the raw light files and verify their names and counts. CFA color-camera data may show a mosaic pattern during this initial check; do not modify the raw files just to make the preview prettier.

  1. Use Blink’s display-stretch controls to reveal stars and the field. A display stretch leaves the raw pixel data unchanged. Compare frames at the same zoom and inspect both the full field and stars near the center and corners.
  2. Play the sequence slowly, then pause and step through changes. Review the relevant filename whenever a frame looks different, and record clear failures in the selection log.
  3. Try a consistent stretch for comparing sky brightness. A separate auto-stretch for every frame can conceal changes in transparency or background level. Use per-frame display adjustments only when needed to inspect detail, and remember that the resulting brightness is not a direct comparison.
  4. Look for severe trails, double stars, major focus loss, clouds, light leaks, obstructions, or a badly misplaced target. Compare suspected defects with neighboring frames rather than rejecting an exposure on a fleeting impression.
  5. Remove obvious failures from the working candidate list, not from the original archive. Avoid Blink’s file-deletion actions. Keep uncertain frames marked for a second look after calibration.

3. Separate normal changes from damaged exposures

Dithering shifts stars between exposures, and a meridian flip changes orientation. These do not automatically make a frame unusable; later registration handles compatible shifts and rotations when enough field overlap remains. Blink on unregistered data is not a registration test.

A single satellite trail may be handled by integration rejection when enough suitable frames are available. Severe aircraft flashes, large contaminated areas, or a tiny dataset need more care. Review the eventual stack and rejection maps rather than promising that every trail will disappear.

Keep mild seeing and transparency variations for measurement unless they clearly ruin the exposure. Selecting only the sharpest handful can discard useful total exposure time. The right balance depends on the desired detail, noise, and amount of data available.

4. Create calibrated review copies

Follow the WBPP lesson to load the candidate raw lights and correct calibration frames into a separate review output directory. Inspect the calibration assignments first. Configure the run to stop after calibration and, for raw color-camera data, debayering; disable later registration and integration stages using your version’s pipeline controls.

Open a representative output and verify that calibration and the intended color-camera conversion succeeded. Keep these copies linear and at their original geometry. Do not stretch, sharpen, denoise, resize, or register them before the measurements in this exercise.

Keep a traceable correspondence between each review copy and its original raw file. WBPP may add suffixes or use grouped output folders. Check the report and paths; do not rely on stripping a guessed suffix when filenames repeat.

These products are for inspection. The final workflow below returns to selected raw files for a complete WBPP run, trading some repeated processing for a clear beginner handoff. Do not put calibrated review copies into WBPP as raw lights with calibration enabled.

5. Measure a comparable set in SubframeSelector

Find SubframeSelector through All Processes, usually under ImageInspection. Older references may describe a script with different controls. Use the installed process documentation for the current interface.

  1. Reset a reused instance and add the calibrated review copies for one comparison group. Confirm that every file is a single exposure, not an integrated master or a different processing stage.
  2. Select the Measure Subframes routine. For a first comparison, choose pixel scale units for FWHM where available. Arcsecond values require a correct image scale; a guessed scale gives misleading units.
  3. Review system parameters and star-detection settings. Keep a consistent baseline within the group. Do not copy a camera gain value into a field with different units without checking its documented meaning.
  4. Use Star Detection Preview, where available, on a representative frame and a suspected outlier. Check that detections follow real, unsaturated stars rather than hot pixels, noise, or nebular knots. If detection is poor, inspect calibration and input state before adjusting detection thresholds.
  5. Run measurement, open the Measurements table and graph, and confirm that all intended frames were measured. Investigate errors or missing measurements rather than automatically classifying those files as the worst images.

6. Read the metrics together

Compare the distribution within your group. A metric is a clue to inspect, not a complete diagnosis. Measurements depend on detected stars, sampling, and the selected model and settings.

MeasurementWhat it helps revealWhat to watch for
FWHMTypical fitted star width; high outliers may indicate soft focus or poor seeingCompare the same units and image scale; a tiny value can also reflect bad detections
EccentricityStar elongation; lower values indicate rounder fitted profilesInspect actual stars and corners; no single cutoff suits all optics and sampling
Stars / star countChanges in detectable stars, sometimes associated with clouds or focusFilter, exposure, and detection settings also affect the count
Median / background levelChanges in sky level or illuminationMoonlight, twilight, and gradients can raise it; higher does not mean better signal
Noise and PSF-based signal metricsAdditional context for background and useful stellar signalConfirm the exact metric definition; do not treat every quantity labeled weight as interchangeable

7. Review outliers and approve deliberately

Plot or sort by FWHM, then eccentricity, and inspect isolated outliers in Blink using the same calibrated copies. Look at star count and background changes too. Record the visible reason for each rejection, such as sustained trailing or cloud-obscured stars.

For example, if most comparable frames cluster near 3 pixels FWHM and a few measure near 7 pixels, inspect those few for focus or tracking problems. Those numbers illustrate an outlier pattern; they are not approval thresholds for your equipment.

For a first pass, use the Measurements approval controls to approve or reject individually. If adding an Approval expression later, base it on the measured group and inspect every borderline result. Check its syntax and evaluation in the installed help. Reapplying an expression can change earlier decisions unless they are protected by the version’s lock controls.

Approval decides whether to keep a frame; weighting decides how strongly an included frame contributes. This tutorial uses SubframeSelector for selection and lets WBPP calculate its own integration weights later. Leave custom weighting formulas and output weight keywords out of this first workflow.

Count the accepted frames and their total exposure time. Keep uncertainty visible in the log. If a large fraction is rejected, recheck the grouping, units, calibration, and detection settings before concluding the whole session is poor.

8. Pass the approved raw list to WBPP

Save the measurements, configuration, and decision log using the available export options. Match each approved calibrated review file to its original raw light. You can also use Output Subframes to produce approved review copies in a new directory, but those remain calibrated copies, not raw WBPP inputs.

Create an Approved_raw folder containing copies of only the accepted original raw lights, preserving session and filter subfolders where needed. Alternatively, add the approved original paths directly to WBPP. Check the counts against the selection log and ensure that no frame appears twice.

Start the final WBPP configuration with that approved raw list and its matching calibration frames. Use a clearly named final output directory, verify calibration and CFA settings again, and enable the intended registration and integration stages. Do not accidentally reuse the unfiltered original light list.

If WBPP’s own Frame Selection stage is also enabled, review how its additional exclusions affect the accepted list. Keep interactive stages intentional. After completion, compare the report’s used-frame counts with your selection log and investigate unexpected losses.

Quick troubleshooting and next steps

FWHM is implausibly small or many tiny objects are detected: inspect Star Detection Preview and the calibration state. Hot pixels are not a sharp star field. Do not solve this by adopting a stricter FWHM cutoff.

Measurements differ dramatically between filters or sessions: separate comparable groups and check exposure, scale, and processing stage. Avoid a universal ranking across unrelated data.

The lowest-noise exposure is cloudy or lacks stars: inspect the image and other metrics. Smoothness alone is not a measure of useful target information.

Frames look equally bright despite changing sky conditions: review whether individual auto-stretches are masking those differences. Compare a consistent display stretch and the measurements.

Rejected frames return to the run: compare actual input paths and counts in WBPP. A decision in one process does not automatically remove a file from another process’s list.

The final stack still has poor stars: inspect registered lights, reference choice, rejection maps, and acquisition limitations. Frame selection cannot repair systematic optical or tracking problems present in every exposure.

Continue with the WBPP lesson, keeping the final integration linear until the appropriate calibration and processing steps are complete. This is an original practice sequence using the linked guidance. Older sources explain the concepts; current installed help governs controls and metric definitions.