Stefan Krastanov
Stefan Krastanov
``` julia> random_destabilizer(5,6) |> stabilizerview |> MixedDestabilizer ERROR: TypeError: in typeassert, expected QuantumClifford.Tableau{SubArray{UInt8, 1, Vector{UInt8}, Tuple{UnitRange{Int64}}, true}, SubArray{UInt64, 2, Matrix{UInt64}, Tuple{Base.Slice{Base.OneTo{Int64}}, UnitRange{Int64}}, true}}, got a value of type QuantumClifford.Tableau{Vector{UInt8}, Matrix{UInt64}}...
Currently embed is implemented for `PauliFrames`. We need it for all tableaux, and for dense clifford operators, and for single- and two-qubit gates.
The documentation would probably better if most structs and functions have typedefs and signatures at the start of their docstrings.
Neat things to mention (ping contributors): - perturbative expansions - nonclifford circuits and states - pauli frames - gpu pauli frames - many different linear algebra tools (canonilicalization, traceout, inner...
We can already convert a code or a parity check tableau into a faults matrix or a tanner graph. But generalizations of the tanner graph to things like stim/pymatching's "detector...
We need to have "stim style" "relative" circuits: - [ ] `Repeat(::Vector, ::Int)` - [x] `sMRZ(::Int, ::Nothing)` - [ ] `ClassicalPairtyRelative(::NTuple{Int})` with negative numbers And QuantumClifford-style "absolute" circuits: - [x]...
This is something that should in parallel be fixed in Quantikz. Quantikz currently relies significantly on struct properties being vectors instead of tuples. That was a bad old decision --...
See the couple of places where `NoZeroQubit` is already used as an error message. Ensure all operations have that. Ensure all classical bits are also non-negative. For any other function...