Skip to content

Commit 4f9545f

Browse files
authored
Fix grammar and clarity in README section on benchmarks
Corrected grammatical errors and improved clarity in the README regarding the mqtbench package versioning and benchmark regeneration.
1 parent 95ea98c commit 4f9545f

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ pattern.to_bloch().draw()
3232

3333
## Supported benchmarks
3434

35-
The definitions in `_benchmark_names.py` depend on the version of the `mqtbench` package. In particular, `mqtbench` 2.2.3 introduced the new benchmarks `dynamic_qft` and `iqpe` which contain feed-forward primitives that are still unrepresentable on Graphix circuits, so `test_benchmark_names` fails if `mqtbench` 2.2.3 is used with the current code. We currently pin `mqtbench` to version 2.2.2 and provides the script `_generate_benchmark_names.py`, which developers can run to regenerate `_benchmark_names.py`. Running
35+
The definitions in `_benchmark_names.py` depend on the version of the `mqtbench` package. In particular, `mqtbench` 2.2.3 introduced the new benchmarks `dynamic_qft` and `iqpe` which contain feed-forward primitives that are still unrepresentable on Graphix circuits, so `test_benchmark_names` fails if `mqtbench` 2.2.3 is used with the current code. We currently pin `mqtbench` to version 2.2.2 and provide the script `_generate_benchmark_names.py`, which developers can run to regenerate `_benchmark_names.py`. Running
3636

3737
```bash
3838
uv run python _generate_benchmark_names.py

0 commit comments

Comments
 (0)