Skip to content
This repository was archived by the owner on Jan 10, 2025. It is now read-only.

Commit 6346453

Browse files
resolving issue #26
1 parent cb27508 commit 6346453

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

manuscript.tex

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -436,9 +436,7 @@ \subsection{Optimized quantum scheme for Hamming distance calculation}
436436
The Hamming distance measured in this way is bounded $0 \leq d_{i,j}^H \leq 1$,
437437
where $0$ indicates that $x_i$ are $y_j$ identical and $1$ means they are completely opposite in terms of their pairwise binary coordinates.
438438

439-
In comparison with the circuits for Hamming distance calculations proposed previously \cite{trugenberger2001},
440-
our method allows one to reduce the number of gates in the circuit (at least in $2n$ one-qubit NOT gates)
441-
and reconstruct all distance matrix in parallel and can be implemented with high fidelity.
439+
Currently available quantum platforms are still subject to substantial level of noise and extracting the exact distance from amplitude is still a difficult task. However, for most of algorithms, SOFM included, the information of nearest vectors is sufficient. Because of that property, those algorithms fall into a special case category for which, as there is only one input vector considered, the ``Decoding'' stage (Fig.\ref{fig:qcircuit}) can be removed as measurement no longer needs to indicate for which input vector the distance has been measured. In this special case scenario the circuit depth complexity is matching with \cite{shuld2014}, but in general case for multiple input vectors the ``Decoding`` stage still needs to be included leading to larger circuit depth and less attractive complexity in terms of number of controlled gate operations. The number of controlled gate operations in this general case of multiple input vectors is matching the number of controlled gate operations in \cite{trugenberger2001}.
442440

443441

444442
%%%%%

0 commit comments

Comments
 (0)