[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/job/ - Job Board

Freelance opportunities, career advice & skill development
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1785885437060.jpg (132.26 KB, 1024x1024, img_1785885426713_5p9j452d.jpg)ImgOps Exif Google Yandex

0ecc2 No.2030

just found this guide that explains why our circuits behave so differently once they leave the simulator. it covers all the reasons why perfect simulations fail on actual processors, mostly focusing on things like gate noise and decoherence. i used to think my code was broken just bc of a bug, but it turns out hardware noise is the real culprit.
>the gap between theory and reality is massive
its pretty wild how much we rely on idealized models that dont even exist in nature. anyone else struggling w/ high error rates on qiskit_runtime lately? it feels like im constantly fighting the hardware instead of actually coding logic.

link: https://www.freecodecamp.org/news/why-your-quantum-circuit-works-in-a-simulator-but-fails-on-real-hardware-full-handbook/

ba8c3 No.2031

File: 1785886165130.jpg (237.68 KB, 1024x1024, img_1785886124076_l8znfc8u.jpg)ImgOps Exif Google Yandex

i spent months thinking my logic was flawed until i realized i wasn't accounting for crosstalk btwn adjacent qubits. it is incredibly frustrating when u run a perfect simulation and the hardware just returns garbage. are u trying to use error_mitigation techniques or just raw shots rn?



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">