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

Quilc Container timeout for rigetti M2 #860

Open
steven09200808 opened this issue Nov 2, 2022 · 2 comments
Open

Quilc Container timeout for rigetti M2 #860

steven09200808 opened this issue Nov 2, 2022 · 2 comments

Comments

@steven09200808
Copy link

Hi,
Previously for rigetti M1 device, we don't see this issue. But for rigetti M2 device, we found Quilc Container timeout more frequently. When do quil_to_native_quil, the running time of quilc for M2 is longer than M1.

@stylewarning
Copy link
Member

Could you provide an example program and chip spec that isn't behaving nicely?

@steven09200808
Copy link
Author

we are using compiler.quil_to_native_quil and saw timeout error like below:
Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='translation.services.production.qcs.rigetti.com', port=443): Read timed out. (read timeout=30)")': /devices/Aspen-M-2/get_version_info.
I can't give the a lot detail of program. So just give some characteristics of it. qubitCount is 3. gateCount is 618. 1Q is 588. 2q is 30. We don't have chip(M2) spec on our side. So the public info from here(https://www.rigetti.com/what-we-build) might be useful.

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

2 participants