Welcome to the documentation overview page of Atomiq ONE. Learn how to make your quantum hardware controllable like a single device with our orchestration stack. Below you will find links to the documentation for the different subsystems. These resources provide detailed information, guides, and references to help you understand and contribute to our projects.
Atomiq #
Atomiq is a convenience layer above the ARTIQ realtime experiment control layer. It mainly provides an abstraction layer that allows to move hardware specific information (like what device is plugged to what) into a configuration and to work with generic software objects that represent the actual hardware in the lab (like AOMs, Coils, Lasers, etc.).
HEROS #
HEROS is a decentralized object sharing service. In simple words it makes your software objects network transparent. To be fast and efficient, HEROS relies on the minimal overhead eclipse-zenoh protocol as a transport layer. It thus supports different network topologies and hardware transports. Most notably, it can run completely decentralized, avoiding a single point of failure and at the same time guaranteeing low latency and and high bandwidth communication through p2p connections.
BOSS #
BOSS is a service that instanciates python objects as HEROs based on a JSON configuration. The configuration can be read from a file, a URL (e.g. from a couchdb) or from an evironment variable. Basically, BOSS allows you to quickly mask your arbitrary python object as a HERO and to run it.
HEROS Devices #
This repository contains python representations (think drivers) of frequently used lab equipment. While these drivers can be perfectly used also locally on the system attached to the lab equipment, the real advantage arises, when the created python object is made available in the network via HEROS.
Learn about the HEROS Devices project with this comprehensive documentation. It includes detailed instructions and references to help you work with the devices associated with the HEROS project.