You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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").
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.
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?
The text was updated successfully, but these errors were encountered: