Processing and analysis
Every file an observation produces passes through Skynet’s pipelines. Some of what happens is yours to choose and some is not, and the split is deliberate: you choose how your data product is made, and Skynet measures every file the same way.
| Pipeline | Who sets it | What it does | Where you change it |
|---|---|---|---|
| Processing | You (anyone who can edit the observation) | Makes your data product: reduces the raw frames and plate solves them | The observation’s Processing section, or the API |
| Analysis | Skynet, fixed | Measures every file: header facts, image quality, the PSF profile and, on reduced and plate-solved products, the photometric zero point | Not configurable |
| Rendering | You | Draws the thumbnails and previews | The FITS viewer |
| Afterglow | You, fully customized | Your own photometry and calibration: targets, apertures, catalogs, light curves | Afterglow |
A rule of thumb for where something belongs: if it changes the file you download, it is a processing setting and you can set it. If it measures a file, it is analysis and Skynet sets it. If it is science you want to tune, such as aperture sizes or the calibration catalog, do it in Afterglow.
Most observations never change a setting. The platform defaults are what Skynet runs on every telescope, and they improve over time.
Processing settings
Section titled “Processing settings”Processing turns each raw optical frame into a data product in two stages, and its settings cover only what shapes that product:
- Reduction subtracts the master bias and dark and divides by the master flat.
- WCS solve plate solves the frame against a star catalog and writes the World Coordinate System (WCS) into the product’s FITS header.
Where to find them
Section titled “Where to find them”Open the observation and choose Processing in the section list on the left. Everyone signed in who can see the observation can see its processing settings, because they are part of the data’s provenance. Only people who can edit the observation can save changes or reprocess it.
Every control shows the value the pipeline will actually use. A dot marks each setting you have changed, each section’s header counts how many you have customized, and reset next to a field returns it to the platform default when you save. Skynet stores only the fields you changed, so every field you leave alone keeps following the platform default, including future improvements to it.
What you can set
Section titled “What you can set”Optical settings come in four sections. Radio processing has no settings yet.
| Section | Settings | What they decide |
|---|---|---|
| Stages | Reduction, WCS solve | Whether the product is reduced, and whether it carries a WCS. Both are on by default. |
| Source detection | Threshold (σ above the background, default 2.5), background mesh and filter size, minimum connected pixels, matched-filter kernel prior, deblending, cleaning, windowed centroids | How sensitive star detection is. These are the stars the plate solve matches against the catalog; a lower threshold finds fainter stars. |
| WCS solve | All-sky fallback; the solve’s star selection: FWHM range, maximum ellipticity, maximum number of stars, hard cap, saturation level, saturated-pixel cut, brightness percentile clips | How hard the solve searches, and which detected stars it uses. All-sky fallback is off by default: when the normal, constrained solve finds nothing, it runs a slow wide-area astrometry.net search that can rescue a frame whose pointing was far off. |
| Reduction | Master max age; prefer-complete windows for bias, dark and flat; dark exposure match factor | Which master calibration frames reduce each science frame. By default a complete master (one built from its full set of frames) within 3 days (bias and dark) or 4 days (flat) of the frame beats a nearer partial one, a master dark within a factor of 2 of the frame’s exposure ranks ahead of the others, and masters have no age limit. |
The settings do not include aperture sizes, sky annuli, photometry catalogs or zero-point fitting. Skynet’s standardized analysis measures those the same way on every product (below), and customized photometry belongs in Afterglow. Photometry and field-calibration settings were removed from processing in October 2026, and the API now rejects them.
Saving re-processes the observation
Section titled “Saving re-processes the observation”Saving queues re-processing of the observation’s raw frames, which starts moments later. Each re-run writes a new processed file that replaces the previous one as the observation’s product. Analysis then measures the new file, so its zero point is measured again too. Results built from those frames, such as stacks, rebuild on their own once the frames finish.
The re-process button (circular arrows) next to Save, or Re-process data in the observation header’s more-actions menu, re-runs processing under the current settings without changing them. Skynet does not re-process existing observations when its pipeline improves, so use it when you want an older observation to pick up the current pipeline. It also re-runs Skynet’s quality checks on the frames.
Processing settings belong to one observation. Other observations in the same project keep their own.
When to change them
Section titled “When to change them”Leave the defaults alone unless one of these applies:
- The plate solve fails. On a sparse or faint field, lower the detection threshold so more stars are found; the solve’s star selection cannot bring back a star that detection never found. With poor seeing or out-of-focus stars, raise the WCS solve’s maximum FWHM. If the telescope’s pointing may have been far off, turn on all-sky fallback.
- You need particular calibration masters. Set a master max age to keep old masters away from your frames, or change the prefer-complete windows and the dark exposure match factor.
- You want unreduced or unsolved products. Turn off the stage. Skynet measures a zero point only on products that are both reduced and plate solved, so turning off either stage means your products get no zero point.
If you want different apertures, a different calibration catalog or photometry of your own targets, processing settings are the wrong tool: use Afterglow.
Through the API
Section titled “Through the API”GET /v1/observations/{uid}/processing-settingsreturnsoverride, exactly the fields you set (null when you have set none), andeffective, the override merged onto the platform defaults, which is what the pipeline runs.PATCH /v1/observations/{uid}/processing-settingsreplaces the whole override and re-processes the observation. What you send is what is stored, so to reset a field, leave it out. Unknown fields are rejected with a 422 response that lists them.POST /v1/observations/{uid}/reprocessre-processes the observation without changing its settings.
For example, this override lowers the detection threshold and turns on all-sky fallback, leaving everything else on the platform defaults:
{ "optical": { "source_detection": { "threshold": 1.8 }, "solve": { "all_sky_fallback": true } }}The Observation API page has the full reference.
Analysis
Section titled “Analysis”Analysis measures every file Skynet stores, raw and processed, with settings Skynet defines. You cannot configure it, and that is the point: Skynet uses these measurements to judge frames and to characterize its telescopes, so they must mean the same thing on every file, whatever settings produced it. Your processing settings change which file is measured, never how it is measured.
| Measurement | Raw light frame | Processed light frame | Calibration frame (bias, dark, flat) |
|---|---|---|---|
| Header facts: capture time, exposure, filter, binning, airmass, gain, read noise, sensor temperature | yes | yes | yes |
| The WCS in the header, as found (analysis never plate solves) | yes | yes | yes |
| Image quality: FWHM, ellipticity, sky background, source count | yes | yes | yes |
| PSF profile | yes | yes | no |
| Field calibration: zero point, color term, star table | no | when reduced and plate solved | no |
PSF profile
Section titled “PSF profile”On every optical light frame, analysis measures how a star’s light spreads out. It picks up to 40 bright, isolated, unsaturated stars, measures how much of each star’s light falls inside circles of growing radius, and takes the median across stars. A Moffat fit to that curve gives the PSF’s FWHM and the shape of its wings, and the half-flux diameter is stored for comparison with the focus measurements SkyNode makes. The profile is what converts an aperture zero point to total light, and it tracks seeing and focus through a night. A frame without five suitable stars, such as a very crowded field, records that instead of a profile.
Field calibration
Section titled “Field calibration”On reduced, plate-solved optical frames and stacks, analysis measures the photometric zero point against catalog stars:
- Catalog. APASS stars in the field are matched to the detected stars, and known variable stars are rejected. The catalog band follows the frame’s filter. Narrowband filters use the nearest broadband (H-alpha calibrates against R). Filters APASS cannot calibrate, such as U, u′, z′ and the neutral-density filters, record that no catalog band applies instead of a zero point.
- Aperture. The aperture radius is 1.5 times the frame’s PSF FWHM (between 3 and 30 pixels), with the sky measured in an annulus from 4 to 6 FWHM. Because the aperture follows the seeing, the correction to total light stays small and steady from frame to frame.
- Zero point. Stored both in the aperture and as total light (corrected with the PSF profile), each with its error, plus the extra star-to-star scatter the fit needed, which patchy cloud raises. Zero points are in electrons per second when the gain is known, and the result records which gain was used and where it came from.
- Color term. When at least 10 calibration stars have catalog colors with a spread (standard deviation) of at least 0.05 mag, analysis also fits how the zero point changes with star color, using a color index chosen for the filter (B−V for B and V, r′−i′ for R and I, and so on), and gives the zero point for an A0V (Vega-like) star.
- Depth and sky. The 5σ limiting magnitude and the sky brightness in magnitudes per square arcsecond.
- Star table. Every calibration star, with its catalog magnitudes, its measured flux and whether the fit kept it.
Not field calibrated: raw frames (their pixels are not flat fielded), products with reduction turned off even when they are plate solved, products without an accepted plate solution, and mosaics. A product that calibrates successfully gets the field_calibrated flag, which the observation’s data filters use.
Each file’s detail page shows the zero point, the PSF FWHM and the calibration stars. A raw frame shows the zero point of the processed product made from it.
An observation processed before October 2026 may show no zero point; reprocess it to get one. Processed FITS files don’t carry the zero point in their headers, so read it from the analysis result.
Rendering
Section titled “Rendering”Rendering draws the thumbnails and previews you see on the website. It never changes your FITS data or what analysis measures.
You set it in the FITS viewer: open an image, adjust the display, and choose Save to this image or Save to whole observation…. The thumbnails refresh shortly afterward, and a setting saved to one image takes precedence over the observation’s. The settings are:
- Stretch: midtone (the default), asinh, log, square root, gamma and others.
- Levels: the background, midtone and saturation percentiles (by default 1, 97.5 and 99.8).
- Colormap, invert, and the color drawn for pixels with no data.
Customized photometry and calibration
Section titled “Customized photometry and calibration”Skynet’s zero point is one standardized measurement per product. For anything you want to tune yourself, such as photometry of your targets, aperture and annulus sizes, the calibration catalog, your own reduction or light curves, open the observation in Afterglow. Afterglow works on copies of your files, so nothing you do there changes Skynet’s standard results. Its Sources panel finds sources, measures them and fits a zero point against the catalog you choose, and the photometry exports as CSV.
Reference
Section titled “Reference”ObservationAssetProcessingRun: one processing run, with the settings it ran under, its inputs, outputs and timing.ObservationAssetProcessingOutput: a file a processing run produced.ObservationAssetReductionInfo: the master calibration frames that reduced a product.ObservationTaskAssetProcessingRunImageReductionInfo: the masters a processing run selected.ObservationTaskAssetProcessingRunWcsSolution: the plate solution a processing run found.ObservationAssetAnalysisRun: one analysis run. Its field calibration (ObservationAssetAnalysisRunFieldCalibration) and PSF profile (ObservationAssetAnalysisRunPsfProfile) records belong to it.ObservationAssetAnalysisRunHeaderCore: the header facts.ObservationAssetAnalysisRunImageQualityMetrics: the image-quality metrics.ObservationAssetRenderRun: one rendering run and the thumbnail it produced.- Observation API: the processing-settings and reprocess endpoints.