# Getting started with NextAstro Hub

NextAstro Hub brings observatory status, observing plans and telescope controls
together. You can read these guides without signing in. Operating an observatory
uses your account's existing permissions and any applicable reservation.

## Open an observatory

Open the [Hub](https://hub.nextastro.org/) and choose an observatory. Its pages
show the telescope's current status and the observing tools available to you.
Sign in when you want to create plans or use controls that require an account.

## Choose an observing workflow

- **Python scripting** controls OBS from a local script or notebook, using loops,
  functions and image measurements. Start with [Python scripting](python-scripting.md)
  for setup, the API reference and 13 complete worked examples.
- **Projects** describe your targets and the observations you want. For
  coordinate units and saved positions, see [Project coordinates](project-target-coordinates.md).
- **Sequences** organise observing instructions that can be reused and scheduled.
- **Linear Script** runs a list of telescope commands in order. It is useful
  when you want explicit slews, tracking, filters, exposures, camera changes or
  warming commands. See [Linear scripts](linear-scripts.md).
- **Calendar** reserves observing time. A saved linear script can be selected
  as the reservation's event type, alongside the existing observing workflows.

The controls you can operate depend on your account's observatory and global
roles. The relevant guide explains additional permissions for particular commands.

## Plan camera coverage

Project target right ascension is saved in hours and declination in degrees.
The project editor handles its form conversions for you. For a mosaic, grid
rotation and the camera's orientation have different roles: read
[Mosaic rotation](standard-mosaic-rotation.md) before choosing panel overlap.

## Follow a linear script

Open **Linear Script**, add commands, name the script and save it. **Run** queues
it after the active FIFO or calendar operation completes. The running row is
highlighted and an error pauses the script on the affected line.

The script runs on the observatory computer. You can leave the page or close
your browser and return to see its progress. A genuine command failure requires
an explicit **Resume** after the problem has been addressed.

**STOP** ends a script using the command-specific behaviour described in the
[linear scripting guide](linear-scripts.md). Cooling and warming progress is
reported every 30 seconds in the observatory logs.

## Observatory settings

Owners and administrators can adjust [filter flats](filter-flat-settings.md)
to change a filter's acquisition quantity or order. Directional observing maps
are explained in [Azimuth protection](azimuth-protection.md), including how their
colours affect queue selection and calendar warnings.

## Find an answer

Use **Search the documentation** above to search across these guides. Each
guide has a permanent address, section links and a Markdown version. Open
**Help & docs** from the Hub navigation to return here while observing.