The observation editor
The observation editor is the 5-step form you walk through to build an observation. You reach it from Observe (/observe) in the web app.
/observe opens the hub, titled “What do you want to do?”. Pick who the observation is for in the Observing as menu (yourself or one of your organizations); it shows how many telescopes that owner can reach. The hub then offers two paths:
- Create an observation. Click Create a new observation and you’re in step 1 with a blank observation. The button is disabled when the selected owner has no observing grants.
- Guided projects. Pick a ready-made project from the catalog — see Catalog projects. Starting from the catalog creates the project’s observations for you, already configured, so you don’t go through the editor step by step.
The same column also lets you pick up earlier work: Resume in-progress observation (the unfinished observation kept in this browser), Saved specs (drafts you saved with Save as draft), and Import from spec (paste an exported observation spec as JSON). Resubmit as new observation (in an observation’s actions menu) also opens the editor, pre-filled with a copy of that observation, and Edit on an observation you can change opens the same steps on the live observation.
This page is about the from-scratch flow.
The five steps
Section titled “The five steps”1. Observing Accounts → 2. Target → 3. Data Requests │ ▼ 5. Review ← 4. ConfigurationYou build the observation as you move through the steps; the editor holds your work as you go. Each step is its own page: jump to any step from the stepper at the top, or use the Previous / Next buttons at the bottom. Below every step an instrument bar lets you pick one of the owner’s instruments to preview how it would handle what you’ve set, with a count of how many instruments are compatible.
Everything you set across the steps adds up to a single portable description of the observation — the observation spec. You don’t need to think about it to use the editor, but it’s what makes duplicating, exporting, and starting from a catalog project work. See Observations.
| Step | What you do | Page |
|---|---|---|
| 1 | Pick the observing grants that will fund the observation | Observing Accounts |
| 2 | Pick the target — what to observe | Target |
| 3 | Add one or more data requests describing what data to collect, and tune each request type’s configuration | Data Requests |
| 4 | Set observation-wide identity, scheduling, instrument-selection rules, and (for a new observation) a project | Configuration |
| 5 | Review everything and publish the observation | Review |
What stays consistent across steps
Section titled “What stays consistent across steps”A few things are always present:
- Owner — set on the hub before you enter the editor (the Observing as menu); the editor’s breadcrumb shows it as “Create as …”. The owner is who funds the observation. All grants shown in step 1 are filtered to grants the owner can use.
- Your work in progress — the observation you’re assembling. The editor keeps it as you move between steps, and a new observation is also kept in this browser until you publish it, so Save & exit (top right) or closing the tab doesn’t lose it; resume it from the hub. When you’re editing an existing observation, nothing is saved to it until you click Save changes on the last step, and Exit warns you if you have unsaved changes.
When can I publish the observation?
Section titled “When can I publish the observation?”The final step runs a checklist:
- At least one observing grant selected (step 1).
- Target has a name and position (step 2).
- At least one data request (step 3).
- Observation has a name (step 4 — Identity section). Picking a target fills the name in from the target’s name until you type your own.
When all four are green, the Publish button is enabled. See Review for what happens when you publish it.