4. Configuration
The configuration step covers the observation-wide settings — identity, scheduling, how instruments are picked, and (for a new observation) which project it joins. Anything that applies to the observation as a whole (rather than to a specific request) lives here. Per-request-type settings (field of view, radio sweep parameters, brightness) are on the Data Requests step.
Identity
Section titled “Identity”| Field | What it does |
|---|---|
| Name | Display name. Required before you publish the observation — the checklist verifies it. Filled in from the target’s name until you type your own |
| Public | When checked, anyone can view the observation, signed in or not (the editor describes it as visible to anyone with the link). When unchecked, only the owner, members of the owning organization with observation permissions, and people it has been shared with can see it |
Scheduling
Section titled “Scheduling”These settings control how your observation repeats, how its measurements are grouped in time, and when it runs. For what each one means and exactly how Skynet schedules it, see Scheduling & repetition.
| Field | What it does |
|---|---|
| Epochs (visits) | How many times to revisit the whole target. 0 repeats indefinitely until you cancel. |
| Keep together (cohesion) | The largest unit that must run without interruption — Frame (one capture), Sample (one measurement), Segment (all samples of one request, or one sample of every request, depending on the sample ordering), Epoch (the whole visit), or Observation (every visit, contiguous). |
| Sample ordering | Finish each request before the next, or take one of each request, then repeat. Also sets the shape of a segment. |
| Cadence | How far apart repeats run: as soon as possible, once per calendar night or day, a minimum gap between units, or a fixed period between units. The last three add a Cadence level (which unit the cadence spaces out) and the gap, period (in seconds) or calendar unit. The scheduler enforces a gap or period between visits (cadence level Epoch); at finer levels it is recorded only. The scheduler cannot place a calendar cadence yet, so an observation that uses one does not get scheduled. |
| Start after (UTC) | The observation isn’t eligible to schedule before this time. |
| Cancel on (UTC) | The observation is auto-canceled if not started by this time — useful for time-sensitive triggers. The editor warns when the date has already passed. |
Four scheduling settings are not shown because the scheduler does not act on them yet: interrupting lower-priority observations, what happens on interruption, synchronized start for copies, and the handoff timeout. An observation that already has them set keeps its values when you edit it. See Scheduling and repetition.
The default keeps each whole visit together while allowing gaps between visits — choose a coarser unit when the science needs an unbroken run, or a finer one for more scheduling flexibility. The editor keeps your choices consistent and won’t let you build a contradiction: the cadence level and the “instrument may change” unit can’t be finer than the keep-together unit.
Instruments
Section titled “Instruments”These fields decide which instruments are eligible to fulfill the observation and how copies are produced.
| Field | What it does |
|---|---|
| Copies | Single dataset, all eligible instruments (mirror), or a fixed number of instruments (Number of copies). |
| Instrument may change | One instrument for the whole observation, or allow it to differ per visit, segment, sample or frame. |
| Instrument access | Any (no restriction), Include only listed, or Exclude listed. |
| Allowed / Disallowed instruments | Shown when access is include or exclude: pick from the instruments the owner’s grants reach. You can’t move to the next step with an empty list in these modes. |
The default — single dataset, one instrument for the whole observation, access Any — lets the scheduler pick one best-fit instrument from whatever your grants reach. Restrict only when you have a specific reason (a camera you trust for high-precision photometry, an instrument with a filter set the others don’t have).
Project
Section titled “Project”Shown only when you’re creating a new observation. Add to a project searches your projects and picks one; Or create a new project names a new project that is created and linked when you publish. Both are optional, but choose now if you want one: the editor can’t change an observation’s project after it’s published.
Where this maps in the schema
Section titled “Where this maps in the schema”Most of these fields are part of the observation spec — name, epochCount, cohesionLevel, sampleOrdering, cadenceKind (+ cadenceLevel / cadenceGapSec / cadencePeriodSec / cadenceCalendarUnit), startAfter, cancelOn, interruptLowerPriority, interruptRecovery, copiesMode (+ copiesCount), coordinationKind (+ coordinationStartToleranceSec), affinityMigrateAt (+ affinityHandoffAfterSec), instrumentMode (+ instrumentUids). Public is set on the observation itself rather than in the spec. The per-request sample count (sampleCount) lives on each request.
The per-request-type configurations (opticalImagingConfiguration, radioTrackingConfiguration, radioMappingConfiguration) are also part of the spec, one per type. They’re edited on step 3 with Configure in the Per-type configuration card rather than here.