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

Qibo API Change #262

Closed
coreyostrove opened this issue Sep 7, 2022 · 3 comments
Closed

Qibo API Change #262

coreyostrove opened this issue Sep 7, 2022 · 3 comments
Assignees
Labels
bug A bug or regression
Milestone

Comments

@coreyostrove
Copy link
Contributor

The qibo devs pushed a new release to pypi on 9/3, and in this new release the seed kwarg has been removed from all of the Channel objects. There wasn't any explanation on the corresponding commit (SHA d182b9b if you're curious) on the rationale for this change, unfortunately.

As it stands the qibo evotype in pygsti won't work fully until we address this. I'm guessing we can either update the evotypes on our end to work around this or else update the requirements to use the previous release at the expense of whatever other new features/enhancements were included in this new one.

@enielse and @sserita, you both are the ones in the know on the qibo integration work, any thoughts on how to proceed?

@coreyostrove coreyostrove added the bug A bug or regression label Sep 7, 2022
@sserita sserita self-assigned this Sep 7, 2022
@sserita
Copy link
Contributor

sserita commented Sep 7, 2022

This has been currently avoided by limiting Qibo to version 0.1.7 in setup.py. Long-term, we probably want to reach out to the Qibo developers and understand why they made this change. It seems harder to get deterministic weak forward simulation now (since the RNG was important for sampling from operator "unravelings").

@sserita
Copy link
Contributor

sserita commented Nov 7, 2023

We will likely deprecate the Qibo interface in the upcoming release, and remove it in a future release. Qibo is moving in a different direction (towards a full stack package rather than just a forward simulator) and is no longer a good fit for a third-party integration.

@sserita sserita added this to the 0.9.13 milestone Nov 29, 2023
@sserita sserita added the fixed but not in release yet Bug has been fixed, but isn't in an official release yet (just exists on a development branch) label Sep 20, 2024
@sserita
Copy link
Contributor

sserita commented Sep 20, 2024

Closed with #490.

@sserita sserita closed this as completed Sep 20, 2024
@sserita sserita removed the fixed but not in release yet Bug has been fixed, but isn't in an official release yet (just exists on a development branch) label Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A bug or regression
Projects
None yet
Development

No branches or pull requests

2 participants