OCS Timestream Aggregator

A time-series data aggregation service for the Simons Observatory that collects, normalises, and stores live detector sensor readings in a streamlined format…

  • Databases
  • Tools & Utilities
A time-series data aggregation service for the Simons Observatory that collects, normalises, and stores live detector sensor readings in a streamlined format for long-term scientific analysis.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score

Not enough data yet for a health score. It needs at least 2 of 4 factors: maintenance, popularity, ease of install, resource needs.

No GitHub repository data collected yet.

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install Apache and MariaDB first Use apt or yum, depending on your Linux version, to install Apache (the web server) and the MariaDB client before running setup. Without them, the OCS Inventory web console and database connection may not start, so the server will be unusable. source
  • Run setup.sh to start setup Run sh setup.sh in the OCS Inventory folder to begin the installation. It asks the required first-run questions and creates the base configuration; skipping it leaves the app unconfigured. source
  • Answer the path prompts during setup When setup asks where to put the web console files and where to keep writable/cache folders, use the default folders unless you have a specific reason. These folders hold the web interface, logs, caches, and deployment packages, so wrong or non-writable folders can break the console or background jobs. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How can I check whether the OCS timestream aggregator is running?

A sodetlib issue describes a health-check script that checks the OCS registry to see if the archiver, timestream aggregator, and monitor are all running. It notes that this check may need to be run in a slightly different way from other sodetlib scripts, possibly as a jackhammer sub-command.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads