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.

Sign up for GitHub

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

Jump to bottom

cudaq.translate API should adhere to the codegen of the set target #2643

Open
khalatepradnya opened this issue Feb 20, 2025 · 0 comments
Open

cudaq.translate API should adhere to the codegen of the set target #2643

khalatepradnya opened this issue Feb 20, 2025 · 0 comments
Labels
enhancement New feature or request OpenQASM codegen issue with generating OpenQASM 2 output

Comments

@khalatepradnya
Copy link
Collaborator

Issue

cudaq.translate API emits the same code irrespective of the target being set.

For example, braket and infleqtion are two targets that emit OpenQASM2.0, each has its own codegen pipeline. (See the respective configuration files). However using cudaq.set_target("braket") or cudaq.set_target("infleqtion") has no effect on the output of cudaq.translate(kernel, format='openqasm2').

Expected behavior

The output of translate should change according to the target being used. If a target does not emit OpenQASM2.0 then revert to the default pipeline.

Observed on main as of commit id 4c2e1c9.
@khalatepradnya khalatepradnya added OpenQASM codegen issue with generating OpenQASM 2 output enhancement New feature or request labels Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request OpenQASM codegen issue with generating OpenQASM 2 output
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@khalatepradnya