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

IBM Accelerator to use calibration gate for pulse job submission #472

Open
1tnguyen opened this issue Jul 22, 2021 · 1 comment
Open

IBM Accelerator to use calibration gate for pulse job submission #472

1tnguyen opened this issue Jul 22, 2021 · 1 comment

Comments

@1tnguyen
Copy link
Member

Update IBM Accelerator to use this calibration gate for pulse job submission.
The old method will be phased out 'by the end of December'.

IBM Quantum has released pulse gates to all users on open systems to attach custom gates defined via their pulse representation, called "calibrations" in Qiskit, to QASM circuits. This allows for a streamlined way to incorporate pulse-level control with the simplicity of QASM circuit construction. A tutorial is available to help you implement this feature into your code. Please note that there is a limitation to 3 qubits and 9 channels per gate for all users.
This method will also become the preferred path for most workflows that previously submitted pulse jobs. The previous way of submitting pulse jobs will still work on non-open systems and ibmq_armonk; however, it is planned to be phased out by the end of December. Users will still be able to access their old pulse jobs even after December 2021.

@1tnguyen
Copy link
Member Author

Gate calibrations in the QObj looks like:

"config": {
        "calibrations": {
            "gates": [
                {
                    "name": "my_custom_gate",
                    "qubits": [
                        0
                    ],
                    "params": [
                    ],
                    "instructions": [
                        {
                            "name": "parametric_pulse",
                            "t0": 0,
                            "ch": "d0",
                            "pulse_shape": "gaussian",
                            "parameters": {
                                "duration": 64,
                                "amp": [
                                    0.2,
                                    0.0
                                ],
                                "sigma": 8
                            }
                        }
                    ]
                }
            ]
        }
    }

my_custom_gate can then be used as a digital gate in the subsequent instructions field.

1tnguyen pushed a commit to 1tnguyen/xacc that referenced this issue Sep 23, 2021
- Unless a gate has a specific pulse sequence defined, the pulse mapper will keep it as a gate instruction.

Signed-off-by: Thien Nguyen <[email protected]>
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

1 participant