-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Gate Validation incorrectly rejects supported SYC
gate
#6779
Comments
I think the problem might be that |
yes, you find the right spot! CC: @verult since he taught me about this file. I can create a simple PR to fix it |
wait, there is no such serialization representation of SYC gate. Cirq/cirq-google/cirq_google/api/v2/program.proto Lines 197 to 220 in 2975d10
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days |
cirq-sync: SYC serialization is not implemented directly since it can be converted to an FSimGate which is supported |
@NoureldinYosri it also fails for the corresponding fSim gate. See this colab. |
It looks like the failure of FSim gate validation is because they apparently require the I verified that including the tag passes validation, including when applied to the Example:
However, once the circuit is past validation and sent to the backends there are further issues that we should track on our internal repo. @eliottrosenberg - is there additional work you'd like done on the client-side regarding validation here? |
@wcourtney with that tag, it would get translated to an arbitrary-angle fSim gate (i.e. a different gate internally), which is not what we want. |
Description of the issue
Gate validation improperly rejects
SYC
gate. When running internally and bypassing validation e.gremote_sampler = qe.CirqServerSampler(connector.grpc_client, "SYC01_10A_BLACK", "current", "iswap7_lower", use_json_serialization=True)
I'm able to get back a result. Likely a logical mismatch is occuring incirq-google/cirq_google/devices/grid_device.py
How to reproduce the issue
The text was updated successfully, but these errors were encountered: