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

Qasm interface #380

Open
yourball opened this issue Oct 9, 2020 · 5 comments · May be fixed by #381
Open

Qasm interface #380

yourball opened this issue Oct 9, 2020 · 5 comments · May be fixed by #381

Comments

@yourball
Copy link

yourball commented Oct 9, 2020

Hi!

It seems that ProjectQ doesn't fully support QASM interface for loading/saving algorithms in .qasm format.
The only related functionality I was able to find is the method .get_qasm() for IBMbackend. Also it works only for circuits that are appropriate for IBM backend.

QASM interface is a very important component in popular quantum compilation frameworks such as Qiskit, Cirq, tket, Quil.
And the absence of such limits potential audience and makes it very hard to use ProjectQ.
I was wondering if there were any attempts to create a proper OpenQasm interface in ProjectQ?

A related point about OpenQASMEngine was discussed in #345 by @Takishima.

Qiskit has OpenQasm parser that should be relatively easy to integrate to ProjectQ.

Thanks!

@Takishima
Copy link
Collaborator

If possible I would like to avoid introducing some more external dependencies to ProjectQ. Particularly with other quantum computing frameworks.
That being said, an OpenQASM interface for loading/saving .qasm files from ProjectQ is something that we would seriously consider. I can't make any precise promises when I could make that a reality, but I will try to implement and propose something going in that direction in the next few weeks.

@Takishima Takishima linked a pull request Nov 6, 2020 that will close this issue
@Takishima
Copy link
Collaborator

@yourball I have now pushed a new version of my feature/openqasm branch. Have a look at it and let me know if you encounter any issues.

The code is currently still rather experimental and does require qiskit to be installed. I might introduce a version that does not require qiskit some time in the next few days.

@Takishima
Copy link
Collaborator

Just pushed a few more changes which include some bug fixes and a parser based on Pyparsing (instead of Qiskit).

@pedromartinssouza
Copy link

@Takishima, @yourball, I know a long time has passed but is this still relevant? Are we still considering implementing QASM translation to ProjectQ?

@Takishima
Copy link
Collaborator

The PR is still open. I will try to ping @andreashehn to review it.

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

Successfully merging a pull request may close this issue.

3 participants