qcs_api/models/
translate_native_quil_to_encrypted_binary_request.rs

1/*
2 * Rigetti QCS API
3 *
4 * # Introduction  This is the documentation for the Rigetti QCS HTTP API.  You can find out more about Rigetti at [https://rigetti.com](https://rigetti.com), and also interact with QCS via the web at [https://qcs.rigetti.com](https://qcs.rigetti.com).  This API is documented in **OpenAPI format** and so is compatible with the dozens of language-specific client generators available [here](https://github.com/OpenAPITools/openapi-generator) and elsewhere on the web.  # Principles  This API follows REST design principles where appropriate, and otherwise an HTTP RPC paradigm. We adhere to the Google [API Improvement Proposals](https://google.aip.dev/general) where reasonable to provide a consistent, intuitive developer experience. HTTP response codes match their specifications, and error messages fit a common format.  # Authentication  All access to the QCS API requires OAuth2 authentication provided by Okta. You can request access [here](https://www.rigetti.com/get-quantum). Once you have a user account, you can download your access token from QCS [here](https://qcs.rigetti.com/auth/token).   That access token is valid for 24 hours after issuance. The value of `access_token` within the JSON file is the token used for authentication (don't use the entire JSON file).  Authenticate requests using the `Authorization` header and a `Bearer` prefix:  ``` curl --header \"Authorization: Bearer eyJraW...Iow\" ```  # Quantum Processor Access  Access to the quantum processors themselves is not yet provided directly by this HTTP API, but is instead performed over ZeroMQ/[rpcq](https://gitlab.com/rigetti/rpcq). Until that changes, we suggest using [pyquil](https://gitlab.com/rigetti/pyquil) to build and execute quantum programs via the Legacy API.  # Legacy API  Our legacy HTTP API remains accessible at https://forest-server.qcs.rigetti.com, and it shares a source of truth with this API's services. You can use either service with the same user account and means of authentication. We strongly recommend using the API documented here, as the legacy API is on the path to deprecation.
5 *
6 * The version of the OpenAPI document: 2020-07-31
7 * Contact: support@rigetti.com
8 * Generated by: https://openapi-generator.tech
9 */
10
11#[derive(Clone, Debug, PartialEq, Default, Serialize, Deserialize)]
12pub struct TranslateNativeQuilToEncryptedBinaryRequest {
13    /// Number of iterations to execute on the control hardware
14    #[serde(rename = "numShots")]
15    pub num_shots: i32,
16    /// The native Quil program to be translated for execution
17    #[serde(rename = "quil")]
18    pub quil: String,
19    /// ISO8601 timestamp of the latest settings to be used in translation. If omitted, latest settings will be used.
20    #[serde(rename = "settingsTimestamp", skip_serializing_if = "Option::is_none")]
21    pub settings_timestamp: Option<String>,
22}
23
24impl TranslateNativeQuilToEncryptedBinaryRequest {
25    pub fn new(num_shots: i32, quil: String) -> TranslateNativeQuilToEncryptedBinaryRequest {
26        TranslateNativeQuilToEncryptedBinaryRequest {
27            num_shots,
28            quil,
29            settings_timestamp: None,
30        }
31    }
32}
qcs_api/models/translate_native_quil_to_encrypted_binary_request.rs

qcs_api/models/
translate_native_quil_to_encrypted_binary_request.rs
