Glossary

Qunicorn: The name of the application that serves as an API for quantum computing request.

Job: The data object that is used to run deployments with their quantum programs on specified provider and store their results.

Deployment: The data object that stores information about quantum programs and their configurations. Is used to register/deploy them, to use them later in multiple jobs.

Provider: An institution that provides quantum computers or simulators.

Device: A single quantum computer/simulator that belongs to a provider.

Pilots: They are run in a celery-task and are used to communicate with the provider APIs and run the jobs there.

Service: Files that belong to the service-layer or core. They calculate or process data, but do not directly communicate with the database.

Core: Files that belong to the service-layer or core. They calculate or process data, but do not directly communicate with the database.

QASM-Format: Widely used format to describe quantum circuits.

CLI: Abbreviation for command line interface, used for example to initially set up the database with custom commands.

Celery: A python library that is used to run tasks in the background in an asynchronous task queue based on messaging. It is used to run the quantum programs on the quantum computers.

Worker: Used as a synonym for a celery worker. That is a process that executes tasks in the background.

Broker: Used in the context of celery and docker. Manages the Celery Worker.

In-Request: Something that is done in a request. For example in-request-execution means that the quantum program that is executed is transmitted in the request.

DTOs: Abbreviation for “Data transfer object” is an object that carries data between processes.

Transpiler: A transpiler is a compiler that translates the source code of a program from one programming language to another.

PreProcessor: The preprocessor is used to preprocess quantum programs to produce output that can be used by a pilot or transpile manager.