AWS braket documentation change
Summary
Replaced gateshot limit description with explicit gate limits per circuit (2000 on-demand/5000 reservation) and maintained minimum shot requirements for error mitigation
Security assessment
Technical specification update for quantum computing tasks. No security controls, vulnerabilities, or security-related configurations are mentioned. Change is about performance limits, not security.
Diff
diff --git a/braket/latest/developerguide/error-mitigation-ionq.md b/braket/latest/developerguide/error-mitigation-ionq.md index 67bcfe4d3..9c1352389 100644 --- a//braket/latest/developerguide/error-mitigation-ionq.md +++ b//braket/latest/developerguide/error-mitigation-ionq.md @@ -15 +15 @@ Error mitigation involves running multiple physical circuits and combining their -For all IonQ's devices: When using an on-demand model, there is a 1 Million [gateshot](./braket-terms.html#gateshot-limit-term) limit, and a minimum of 2500 shots for [Error mitigation](https://docs.aws.amazon.com/braket/latest/developerguide/braket-error-mitigation.html) tasks. For a direct reservation, there is no gateshot limit, and a minimum of 500 shots for Error mitigation tasks. +For all IonQ's devices: When submitting tasks on-demand, the maximum number of gates per circuit is 2,000, and the minimum number of shots per [error mitigation](https://docs.aws.amazon.com/braket/latest/developerguide/braket-error-mitigation.html) task is 2,500. For a direct reservation, the maximum number of gates per circuit is 5,000, and the minimum number of shots per error mitigation task is 500.