Skip to content

Targets and brightness models

Every observation has one target: what the telescope points at. A target is a name, a position that tells Skynet where the object is at any moment, and an optional pointing offset. How bright the target is lives next to it in a brightness model, which Skynet uses to size exposures.

This page defines those pieces. To set them in the website, see 2. Target (position and offset) and the Brightness tab described in 3. Data requests. To send them through the API, see Creating observations.


A position has one of four kinds, named by its positionType:

Kind What it carries Use it for
fixed Coordinates in one frame Stars, galaxies, nebulae, any point that doesn’t move against the stars, or a fixed horizon position
catalog A reference to an object in Skynet’s moving-object catalog Planets, the Moon and Sun, comets, asteroids, Earth satellites
orbital Orbital elements you supply A moving object that isn’t in the catalog, or a newer orbit than the catalog has
ephemeral A time-stamped list of coordinates that Skynet interpolates Not available for new targets (see below)

A fixed position is one set of coordinates. Five frames are accepted:

Frame (coordinateType) Angles Optional extras
equatorial ICRS right ascension and declination (raDeg, decDeg) Proper motion, distance (pc), radial velocity
ecliptic Ecliptic longitude and latitude Ecliptic type (default geocentric true), equinox (default J2000), proper motion, distance (AU), radial velocity
galactic Galactic longitude and latitude Proper motion, distance (pc), radial velocity
horizontal Azimuth and altitude Rates of motion in az/alt
topocentric Hour angle and declination Rates of motion, and whether the values are observed (refraction-corrected) or topocentric

Coordinates can also carry an epoch for proper motion. The editor offers the equatorial, horizontal and galactic frames; the API accepts all five. A SIMBAD result picked in the editor’s search becomes a fixed equatorial position.

A catalog position names an entry in Skynet’s moving-object catalog, and Skynet computes the object’s position for each moment it needs one (when planning, when the telescope points, and while it tracks). Because the target points at the shared catalog entry rather than a copy, refreshed data (a new satellite element set, an updated asteroid orbit) applies to work that hasn’t run yet. See Catalog objects for what the catalog holds.

An orbital position carries Keplerian elements you supply:

Field Meaning
orbitType barycentric (orbit around the Sun) or geocentric (orbit around the Earth)
epochJyear Epoch of the elements, in Julian years
semilatusRectumAu Semilatus rectum in AU, a(1 − e²) for an ellipse; it stays finite for parabolic and hyperbolic orbits
eccentricity Eccentricity
inclinationDeg, longitudeOfAscendingNodeDeg, argumentOfPerihelionDeg Orientation angles, in degrees
meanAnomalyDeg Mean anomaly at the epoch, in degrees

Orbital targets are created through the API. The editor keeps an orbital target (for example on a resubmitted observation) but shows a notice instead of editing it.

An ephemeral position is a list of coordinates at given times, which Skynet interpolates between. The create shape for this kind carries no coordinates today, so you can’t create a usable ephemeral target; use a catalog object or orbital elements for a moving target instead.


Skynet keeps its own copy of several moving-object catalogs and refreshes them on a regular cycle. Each entry has a kind:

Kind What it is Source How you pick one
Major body (major) The Sun, Mercury, Venus, Earth, Moon, Mars, Jupiter, Saturn, Uranus, Neptune, Pluto Built in Editor search or API
Planetary satellite (planetary_satellite) Moons of Mars, Jupiter, Saturn, Uranus, Neptune and Pluto JPL satellite ephemerides API only, by listing the catalog; the editor’s search doesn’t return them
MPC comet (mpc_comet) Comets, by perihelion elements Minor Planet Center Editor search or API
MPC orbit (mpc_orbit) Asteroids and other minor planets, with size and orbit-quality data where known Minor Planet Center, with JPL’s small-body database Editor search or API
NORAD satellite (norad_satellite) Earth satellites, by name or catalog number NORAD element sets Editor search or API
NEOCP object (neocp) Unconfirmed near-Earth-object candidates, positioned from a stored JPL Scout ephemeris JPL Scout Not selectable; Skynet creates these itself for alert-driven observations, and that alert source is not active yet

The editor’s search and GET /v1/catalog-objects/search?q= look up the same sources (plus SIMBAD for fixed objects) and return a ready-to-use position. GET /v1/catalog-objects lists entries filtered by kind.

For a target that moves against the stars, set the optical imaging configuration’s Tracking Mode to Target so the mount follows the object rather than the stars.


A target can shift where the telescope points by a fixed amount from the target position. Skynet applies the offset while it tracks, so a moving target keeps its offset as it moves. Tiling and dithering offsets add on top of it.

Field Meaning
positionOffsetXDeg Offset toward the east, in degrees
positionOffsetYDeg Offset toward the north, in degrees
positionOffsetFrame The frame the offset is measured in (see below); default icrs_tangent
positionOffsetReferenceTime Optional UTC time that fixes the offset’s axes for the time-dependent frames, so they don’t rotate as the night goes on; without it, the axes follow the current time
Frame Offset measured on
icrs_tangent The sky, in ICRS (the default)
gcrs_tangent The apparent (geocentric) sky
altaz_tangent The local horizon frame
body_fixed The body’s own surface, so the offset stays on one surface feature; only for a target that is the Moon

Both offsets default to 0, which means no offset.


A brightness model describes how bright something is, so Skynet can work out how long to expose. Brightness models are part of the optical imaging configuration, not the target: one configuration, and so one set of models, covers all optical imaging requests in the observation. It has two slots:

  • Brightness model (brightnessModel) — the target. Skynet sizes each exposure from it when a request asks for a target signal-to-noise or a fraction of full well (see Exposure sizing).
  • Saturation model (saturationModel) — the brightest thing you expect in the frame, which may be the target or a bright neighbor. Skynet caps each frame’s exposure so that this source stays below 90% of the camera’s full well, and takes more, shorter frames to reach the requested depth.

Both are used only to size exposures. A request with a fixed exposure time ignores them: each exposure is the time you set. Neither changes where the telescope points or how your data is processed.

Type (modelType) Meaning Parameters
source A point source with a magnitude, or an extended source with a surface brightness See below
sky The target is as bright as the local night sky, which Skynet computes for each telescope, filter, time and pointing, including twilight and moonlight None
catalog_ephemeris The magnitude comes from the target’s stored ephemeris (V at each time); Skynet attaches this itself for NEOCP alert targets, and you can’t create one None
Field Meaning Default
isPointSource Point source (true) or extended source (false) true
magnitudeMag Magnitude for a point source, or surface brightness (per square arcsecond) for an extended source, in the reference filter Required
filterId The reference filter the magnitude is quoted in; needed for a spectral component to take effect None
avMag Dust extinction A_V in magnitudes 0
rv Ratio of total to selective extinction R_V 3.1
spectralComponent Optional: how brightness changes with wavelength None
temporalComponent Optional: how brightness changes with time None

To get the magnitude in a given filter at a given time, Skynet starts from magnitudeMag, adds dust extinction at the filter’s central wavelength (from A_V and R_V) and atmospheric extinction at the target’s airmass for that telescope, then applies the temporal and spectral components. A filter with no central wavelength on record is treated as 600 nm.

The editor starts a new optical configuration with a magnitude-19 point-source model and no components.

A spectral component scales brightness from the reference filter to another filter. It has no effect unless the model names a reference filter.

Type Parameter Effect
power_law index Flux scales as (λ / λ_ref)^index, using the filters’ central wavelengths
black_body temperatureK Flux scales as a black body of that temperature, evaluated at the two central wavelengths

With no spectral component, the source has the same magnitude in every filter.

A temporal component makes brightness change with time from an eventTime (UTC):

Type Parameters Brightness at time t after the event
power_law referenceTimeSec, index Flux scales as (t / referenceTimeSec)^(−index), so magnitudeMag is the brightness at referenceTimeSec after the event
exponential referenceTimeSec, index Flux scales as exp(−index · t / referenceTimeSec), so magnitudeMag is the brightness at the event
tabulated lightCurve, optional filterLightCurves Read from a table (see below)

Before the event time, the power-law and exponential components leave the source at magnitudeMag.

A tabulated temporal component describes any light curve, such as the rise, peak and decline of a supernova, as a table:

  • lightCurve is a list of points, each a time offset from eventTime (timeOffsetSec, negative for before the event) and a magnitude offset from magnitudeMag (deltaMag, positive is fainter), for the reference filter. Up to 1,000 points; two points can’t share a time.
  • Between points, Skynet interpolates linearly in magnitude. Outside the table it holds the first or last value, so the table should cover the whole time you expect to observe.
  • filterLightCurves optionally adds up to 32 tables of the same shape, one per filter. A filter with its own table uses it instead of the reference curve and the spectral component, since the table already carries that filter’s color. Other filters, and combinations of several filters, use the reference curve plus the spectral component.
  • Dust and atmospheric extinction apply in every case. referenceTimeSec is not used.

In the editor, light-curve tables are entered on the Brightness tab as days from the event and Δmag, one row per line; the API takes seconds.

The editor offers these components on the brightness model only; the API accepts them on the saturation model too.


← Observations · Data request types →