Sample-based Quantum Diagonalization (SQD) is a hybrid quantum-classical method that replaces variational optimization with a self-consistent recovery loop over QPU samples. Although SQD is considered robust to noisy samples and imperfect classical inputs, its robustness across practical deployment choices has not been systematically analyzed. As a result, shot budgets, qubit layouts, noise mitigation strategies, and the coupled-cluster singles and doubles (CCSD) amplitudes that initialize the ansatz are often chosen without clear empirical guidance. We analyze SQD robustness on IBM Heron hardware across these dimensions. Structured CCSD-amplitude perturbations, including complete zeroing, produce only modest energy shifts from the clean baseline. Differences across layouts and noise-mitigation settings are large in the first recovery iteration but narrow within a few iterations. Accuracy saturates at moderate shot budgets, while very large budgets slightly worsen recovered energies, likely because working-set selection limits the value of additional samples. These results identify where SQD provides genuine deployment robustness and where its limits remain.
Ahatesham Bhuiyan, Cheng Chu, Qian Lou et al.· 1 citation
CutBackdoor is presented, the first parameter-supply-chain backdoor that uses cut circuit execution from CutQC as the deployment-time trigger against VQAs, and poisoned parameters preserve full-circuit validation performance while substantially increasing cut-path reconstruction error under noisy finite-shot circuit-cut execution.
Ahatesham Bhuiyan, Hoang M. Ngo, Cheng Chu et al.· arXiv.org· 0 citations
Noise-induced attacks that manipulate the Zero-Noise Extrapolation pipeline are the most damaging, followed by the QTrojan circuit-level backdoor, while the QDoor parameter-level backdoor is the least effective, yielding only marginal amplification.
Ahmed Azaz Humdoon, Cheng Chu, Lei Jiang et al.· arXiv.org· 0 citations
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.