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
In #81 we now have a SwapperProt. It has a nodeL and nodeR properties which are then used by query to decide whether a pair of local slots are a valid target for a swap. It is done by findswapablequbits.
Currently, this is tested only for a long chain of repeaters, using the default "wildcard" values for these properties.
More complicated setups should be tested.
step 0
First, we need to make findswapablequbits sufficiently general. We need to support custom predicates, not only the <(node) and >(node) ones supported currently.
step 1
Run the current set of tests but on a grid. For instance, we have an entanglement generator between all nearest neighbors on a square grid, but only a chain through the diagonal is running swaps. In such a case, we will need a predicates that are not simply <(node) and >(node) but rather 'the other node is above and to the left of node' and 'the other node is below and to the right of node'.
step 2
Good animated examples added to the documentation.
The text was updated successfully, but these errors were encountered:
In #81 we now have a
SwapperProt
. It has anodeL
andnodeR
properties which are then used byquery
to decide whether a pair of local slots are a valid target for a swap. It is done byfindswapablequbits
.Currently, this is tested only for a long chain of repeaters, using the default "wildcard" values for these properties.
More complicated setups should be tested.
First, we need to make
findswapablequbits
sufficiently general. We need to support custom predicates, not only the<(node)
and>(node)
ones supported currently.Run the current set of tests but on a grid. For instance, we have an entanglement generator between all nearest neighbors on a square grid, but only a chain through the diagonal is running swaps. In such a case, we will need a predicates that are not simply
<(node)
and>(node)
but rather 'the other node is above and to the left ofnode
' and 'the other node is below and to the right ofnode
'.Good animated examples added to the documentation.
The text was updated successfully, but these errors were encountered: