-
Notifications
You must be signed in to change notification settings - Fork 6
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
Invalid circuit splitting for Badger #507
Comments
Was introduced by #493 |
Here's an MWE, using a single Rz rotation. Could it be an issue with handling gates with float inputs? I've pushed this example to the branch /// Just a one-qubit circuit with Rz gate
#[fixture]
fn rz() -> Circuit {
let json = r#"{"phase":"0.0","commands":[{"op":{"type":"Rz","n_qb":1,"params":["0.25"],"signature":["Q"]},"args":[["q",[0]]]}],"qubits":[["q",[1]],["q",[0]]],"bits":[],"implicit_permutation":[[["q",[0]],["q",[0]]],[["q",[1]],["q",[1]]]]}"#;
let ser: SerialCircuit = serde_json::from_str(json).unwrap();
ser.decode().unwrap()
}
#[rstest]
fn split_rz(rz: Circuit) {
let chunks = CircuitChunks::split_with_cost(&rz, 1, |_| 0);
assert_eq!(chunks.len(), 1);
} |
…flow nodes (#1350) The signature computation for a `SiblingSubgraph` takes the union of the nodes' extensions. This didn't contemplate non-dataflow nodes like constants, and caused a runtime panic if one was present. Most of the diff is adding a constant node in the tests. This is a fix for CQCL/tket2#507
This should get fixed with the upcoming |
…flow nodes (#1350) The signature computation for a `SiblingSubgraph` takes the union of the nodes' extensions. This didn't contemplate non-dataflow nodes like constants, and caused a runtime panic if one was present. Most of the diff is adding a constant node in the tests. This is a fix for CQCL/tket2#507
This seems to be fixed now, but the original |
The following code panics with the error "all nodes must have dataflow signature". This test can be run on the
bug/invalid-circ-split
branch in the filetket2/tests/badger.rs
.The text was updated successfully, but these errors were encountered: