Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Allow user to dispatch benchmark on list of machines #225

Open
vprusso opened this issue Feb 21, 2025 · 1 comment
Open

Feature: Allow user to dispatch benchmark on list of machines #225

vprusso opened this issue Feb 21, 2025 · 1 comment

Comments

@vprusso
Copy link
Contributor

vprusso commented Feb 21, 2025

Right now, when we dispatch a job, we dispatch a single benchmark to a single device:

python metriq_gym/run.py dispatch metriq_gym/schemas/examples/quantum_volume.example.json --provider ibm --device ibm_strasbourg 

We could support dispatching a single benchmark to a set of devices. For instance

python metriq_gym/run.py dispatch metriq_gym/schemas/examples/quantum_volume.example.json --provider ibm --device [ibm_strasbourg, ibm_kyiv, ibm_brussels]

Or even something like

python metriq_gym/run.py dispatch metriq_gym/schemas/examples/quantum_volume.example.json --provider [ibm, aws] --device [ibm_strasbourg, arn:aws:braket:us-west-1::device/qpu/rigetti/Ankaa-3]

We would want to be careful that we match the correct provider to the corresponding device (as there could potentially be some ambiguity in what provider is mapped to what device).

@cosenal
Copy link
Contributor

cosenal commented Feb 26, 2025

This has a very good value with enforcing that exactly the same benchmark (with the same parameters) is run across different devices (that is, same input json)

Perhaps instead of the third pattern, we want to support one that is easier to parse, that is,

... --provider ibm --device [ibm_strasbourg, ibm_kyiv] --provider aws --device arn:aws:braket:us-west-1::device/qpu/rigetti/Ankaa-3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants