Glossary
Short definitions of the terms used across these docs. Each term links to the one page that defines it in full.
Organizations and telescopes
Section titled “Organizations and telescopes”| Term | Meaning |
|---|---|
| User | A person with a Skynet account. See People, organizations and groups. |
| Organization | A university, club or company on Skynet. It owns observatories, telescopes and observing accounts, and its members hold built-in roles. See Organizations. |
| Role | What a member may see and change in an organization. Roles are a fixed built-in set. See Roles and permissions. |
| Group | A named set of users inside an organization, used to grant access to several people at once. See Groups. |
| Site | A physical location that one or more observatories can share. See Site vs. Observatory. |
| Observatory | An organization’s facility at a site. It holds telescopes and any devices shared by them, such as a weather sensor. See Observatories and sites. |
| Telescope | The unit that takes observations: a mount with its devices, instruments, queues and access grants. See Telescopes. |
| Device | One piece of hardware: mount, enclosure, OTA, camera, focuser, filter wheel, instrument rotator, antenna, receiver, radio backend, weather sensor or IP camera. See Instruments and devices. |
| Instrument | A combination of devices that can carry out one observation type, such as an optical imager or a radio spectrometer. Observations are matched against instruments. See Instruments and devices. |
| SkyNode | The software that runs at each telescope, takes tasks from Skynet, runs them on the hardware and uploads the data. See SkyNode. |
| Control authority | A SkyNode setting: remote (SkyNode runs scheduled tasks) or manual (an operator at the telescope is in charge). See Control authority and manual control leases. |
Access and prioritization
Section titled “Access and prioritization”| Term | Meaning |
|---|---|
| Telescope access grant | Admits a user or organization to observe with a telescope, and carries their shares. See Telescope access grants. |
| Queue | A lane of a telescope’s time, such as Maintenance, TOO, Calibration or General. Queues are strictly ordered. See Observing queues. |
| Queue access grant | Gives a grantee a place in one queue on one telescope. Observing accounts reach telescopes through these. See Observing queues. |
| Prioritization mode | How a queue orders its grants: fixed, fair-share or calendar. Only fixed is live today. See Queue prioritization modes. |
| Shares | A grantee’s ownership fraction on a telescope, the input to fair-share prioritization. See Queue prioritization. |
| Contested time | Time in which two or more grantees had work they could have run. Fair-share is designed to count only this time against shares. See How usage is counted. |
| Level | A rank on a list of root accounts or of grants on an account. Every list starts as one level, so everything ties until you split it. See Priority levels. |
| Observing policy | Operating rules and constraints an organization records for its telescopes. See Observing policy and constraints. |
Observing accounts
Section titled “Observing accounts”| Term | Meaning |
|---|---|
| Observing account | What funds observations: it reaches telescopes through queue access grants and is spent through observing grants. See Observing accounts. |
| Root account | An account you set up from your own telescope access. See Root accounts. |
| Bucket | An internal subaccount for dividing your own time. See Buckets. |
| Delegated subaccount | A subaccount owned by someone else, created by a delegated observing grant from your account. See Delegated subaccounts. |
| Observing grant | Lets a user, organization or group submit through an account (owner, member, group grants) or connects accounts (internal and delegated grants). See Observing grants. |
| Quota | A cap on credits spent per period on an account or grant. See Quotas. |
| Credits | What quotas count. A completed task is charged its planned duration in seconds (for optical imaging, scaled by the imager’s efficiency factor). See Credit accounting. |
| First Light account | The delegated subaccount every new user gets at signup, with a weekly quota set by Skynet. See First-light accounts. |
| Sponsor | An observing account that funds or has paid for someone else’s observation, and gets a read-only view of it. See Sponsor observers. |
Observations
Section titled “Observations”| Term | Meaning |
|---|---|
| Observation | Everything you ask a telescope to do for one target: the target, the data requests and the observation-wide settings. See Observations. |
| Spec | The portable description of an observation that the editor builds and that you can export, import and save as a draft. See Observations. |
| Draft | A saved, unfinished spec. Nothing is scheduled or charged. See What that lets you do. |
| Target | What to point at: a name, a position and an optional pointing offset. See Targets and brightness models. |
| Brightness model | How bright the target (and the brightest thing in the field) is expected to be, set on the optical imaging configuration and used to size exposures. See Targets and brightness models. |
| Data request | One kind of measurement taken to a chosen depth, such as one filter of an optical image. See Data request types. |
| Epoch | One complete visit to the target. See How an observation breaks down. |
| Sample | One repeated measurement of one request within a visit. See Repetition: epochs and samples. |
| Segment | One request’s whole run, or one sample of every request, depending on the sample ordering. See How an observation breaks down. |
| Frame | One capture the telescope takes. The telescope decides how many frames a sample needs. See How an observation breaks down. |
| Series | An optical request kind: one contiguous run of images on one camera for a set duration. See Repetition: epochs and samples. |
| Cohesion | The largest unit that must run without interruption, shown as Keep together in the editor. See Keep together (cohesion). |
| Cadence | How far apart repeats run. See Cadence. |
| Copies | Independent datasets of the same work on several instruments. See Copies. |
| Result | One deliverable: a sample of a request in an epoch (per copy). It stays until it is fulfilled or canceled. See Results and tasks. |
| Task | One attempt to fulfill a result on a specific telescope and instrument. See Results and tasks. |
| File (asset) | A frame, calibration file or processed product attached to an observation. See Files and assets. |
| Project | A collection of observations around one science goal. See Projects. |
| Alert subscription | Rules that create observations automatically from alert streams such as NASA GCN and Fink. See Alerts. |