You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+65-35Lines changed: 65 additions & 35 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,62 +6,71 @@
6
6
7
7
# devqubit
8
8
9
-
**Local-first experiment tracking for quantum computing.** Capture circuits, backend state, and configuration — runs are reproducible, comparable, and easy to share. Access your data via Python API, CLI, or Web UI.
9
+
**Local-first experiment tracking for quantum computing.**
10
+
11
+
Capture circuits, backend state, and configuration automatically — runs are reproducible, comparable, and easy to share. Access your data via Python API, CLI, or Web UI.
10
12
11
13
> [!WARNING]
12
14
> **Status:** Alpha — devqubit APIs may evolve in `0.x` releases.
13
15
> Users should expect frequent changes that are likely to be incompatible with previously published versions.
14
16
15
17
## Why devqubit?
16
18
17
-
General-purpose experiment trackers (MLflow, Weights & Biases, neptune.ai) are great for logging parameters, metrics, and artifacts. But quantum workloads need *extra structure* that isn't first-class there by default: capturing what actually executed (program + compilation), where it executed (backend/device), and how it executed (runtime options).
19
+
General-purpose experiment trackers (MLflow, W&B, neptune.ai) work well for classical ML, but quantum workloads need structure they don't provide out of the box: what actually executed (program + compilation), where it ran (backend/device), and how it ran (runtime options, calibration state).
Users install `devqubit` (plus optional extras). All public API lives in the `devqubit` namespace; engine internals are not part of the public API.
187
+
158
188
## Contributing
159
189
160
-
We welcome contributions of all kinds — bug fixes, docs, new adapters, or feature ideas.
190
+
We welcome contributions — bug fixes, docs, new adapters, or feature ideas.
161
191
162
192
1. Read [CONTRIBUTING.md](CONTRIBUTING.md) for setup and guidelines
163
193
2. Check [open issues](https://github.com/devqubit-labs/devqubit/issues) or start a [discussion](https://github.com/devqubit-labs/devqubit/discussions)
@@ -171,7 +201,7 @@ uv run pre-commit install
171
201
uv run pytest
172
202
```
173
203
174
-
Early project = high impact contributions. Jump in!
204
+
Early project — high impact contributions. Jump in!
Amazon Braket adapter for [devqubit](https://github.com/devqubit-labs/devqubit) — automatic circuit capture, device property snapshots, and result logging for Braket local simulators and managed QPUs.
6
+
7
+
> [!IMPORTANT]
8
+
> **This is an internal adapter package.** Install via `pip install "devqubit[braket]"` and use the `devqubit` public API.
4
9
5
10
## Installation
6
11
7
12
```bash
8
-
pip install devqubit[braket]
13
+
pip install "devqubit[braket]"
9
14
```
10
15
11
16
## Usage
@@ -25,9 +30,18 @@ with track(project="braket-exp") as run:
See the [Adapters guide](https://devqubit.readthedocs.io/en/latest/guides/adapters.html) for details on wrapping options, batch execution, and performance tuning.
Google Cirq adapter for [devqubit](https://github.com/devqubit-labs/devqubit) — automatic circuit capture, simulator snapshots, and result logging for Cirq samplers and simulators.
6
+
7
+
> [!IMPORTANT]
8
+
> **This is an internal adapter package.** Install via `pip install "devqubit[cirq]"` and use the `devqubit` public API.
4
9
5
10
## Installation
6
11
7
12
```bash
8
-
pip install devqubit[cirq]
13
+
pip install "devqubit[cirq]"
9
14
```
10
15
11
16
## Usage
@@ -26,11 +31,36 @@ with track(project="cirq-exp") as run:
See the [Adapters guide](https://devqubit.readthedocs.io/en/latest/guides/adapters.html) for parameter sweeps, performance tuning, and batch execution.
0 commit comments