SOCS - Simons Observatory Control System
Overview
This repository, SOCS, contains hardware control code for the Simons Observatory. This code operates within the framework provided by OCS.
Installation
Install and update with pip:
$ python -m pip install -U socs
You may install optional dependencies by including one or more agent group names on installation, for example:
$ python -m pip install -U socs[labjack,synacc]
For a complete list of agent groups see the Installation Documentation.
If you would like to install all optional dependencies use the special varient “all”:
$ python -m pip install -U socs[all]
Note: Not all optional dependencies can be installed this way. See the Installation Documentation for more info on specific agent dependencies.
Installing from Source
If you are considering contributing to SOCS, or would like to use an unreleased feature, you will want to install from source. To do so, clone this repository and install using pip:
$ git clone https://github.com/simonsobs/socs.git
$ cd socs/
$ python -m pip install -r requirements.txt
$ python -m pip install .Docker Images
Docker images for SOCS and each Agent are available on Docker Hub. Official releases will be tagged with their release version, i.e. v0.1.0. These are only built on release, and the latest tag will point to the latest of these released tags. These should be considered stable.
Test images will be tagged with the latest released version tag, the number of commits ahead of that release, the latest commit hash, i.e. v0.0.2-81-g9c10ba6-dev. These get built on each commit to the main branch, and are useful for testing and development, but should be considered unstable.
Documentation
The SOCS documentation can be built using Sphinx. There is a separate requirements.txt file in the docs/ directory to install Sphinx and any additional documentation dependencies:
$ cd docs/ $ python -m pip install -r requirements.txt $ make html
You can then open docs/_build/html/index.html in your preferred web browser. You can also find a copy hosted on Read the Docs.
Tests
The tests for SOCS are run using pytest, and should be run from the tests/ directory:
$ cd tests/ $ python -m pytest --cov
For more details see tests/README.rst.
Contributing
For guidelines on how to contribute to SOCS see CONTRIBUTING.rst.
License
This project is licensed under the BSD 2-Clause License - see the LICENSE.txt file for details.
2 maintainers
Metadata
2 maintainers
Release files for socs 0.6.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| socs-0.6.4.tar.gz | 469.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| socs-0.6.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.0 MB
Release files / socs-0.6.4.tar.gz
| Download URL | socs-0.6.4.tar.gz |
|---|---|
| Size | 469.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ddfbc70f5e05e61a40f06f1df52ec0d60a47d6447f05ea5f489995d0e61da321
|
|
BLAKE2b-256 checksum How to use checksums |
c795eef356221aad4b356d0750464374f2cf4717c8cc3756497be4f7e8adcf45
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency logRelease files / socs-0.6.4-py3-none-any.whl
| Download URL | socs-0.6.4-py3-none-any.whl |
|---|---|
| Size | 560.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d90153ecaeded184df0af7bf322327f24bdb62f2c1b95d407ec7655670c4eefc
|
|
BLAKE2b-256 checksum How to use checksums |
18ac0ba16895a33544f88d14802a44d6f46f7d1e2cc4722f867e4522aa8b5359
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency log
