Practical HPCQC Integration with QDMI: A Real-Hardware Case Study with IQM Systems
Fuente:
arXiv
Guardado en:
| Autores principales: | , , , , , , , , , |
|---|---|
| Formato: | Preprint |
| Publicado: |
2026
|
| Materias: | |
| Acceso en línea: | |
| Etiquetas: |
Agregar Etiqueta
Sin Etiquetas, Sea el primero en etiquetar este registro!
|
| _version_ | 1866914497693745152 |
|---|---|
| author | Burgholzer, Lukas Walter, Marcel Hopf, Patrick Sánchez, Álvaro Caride-Tabarés Mattsson, Teemu Hoffmann, Bernd Färkkilä, Noora Bulmash, Daniel Wille, Robert Mansfield, Eric |
| author_facet | Burgholzer, Lukas Walter, Marcel Hopf, Patrick Sánchez, Álvaro Caride-Tabarés Mattsson, Teemu Hoffmann, Bernd Färkkilä, Noora Bulmash, Daniel Wille, Robert Mansfield, Eric |
| contents | Quantum computers are moving into HPC centers, and the main challenge is now integration rather than pure hardware access. Many current software paths still depend on vendor-specific adapter chains between user SDKs, schedulers, and backend APIs. This pattern makes operations more complex than necessary and slows the transition from pilots to production workflows. We present a practical integration path centered on the Quantum Device Management Interface (QDMI). Using IQM superconducting systems as a hardware case study, we implement an IQM-backed QDMI layer and connect it to two software layers that HPC centers working with quantum computers already care about: Slurm-based job execution and Qiskit-facing user workflows. The implementation is publicly available at https://github.com/iqm-finland/QDMI-on-IQM. The key message is simple: integrating quantum hardware into HPC does not have to be a bespoke engineering effort for each backend. Once the software-hardware boundary is standardized, large parts of the stack become reusable across providers and deployment styles. Our results do not claim that standardization eliminates all HPCQC challenges. They show that this specific boundary can already be standardized today in a way that is practical for users, operators, and vendors. |
| format | Preprint |
| id |
arxiv_https___arxiv_org_abs_2604_19869 |
| institution | arXiv |
| publishDate | 2026 |
| record_format | arxiv |
| spellingShingle | Practical HPCQC Integration with QDMI: A Real-Hardware Case Study with IQM Systems Burgholzer, Lukas Walter, Marcel Hopf, Patrick Sánchez, Álvaro Caride-Tabarés Mattsson, Teemu Hoffmann, Bernd Färkkilä, Noora Bulmash, Daniel Wille, Robert Mansfield, Eric Quantum Physics Emerging Technologies Quantum computers are moving into HPC centers, and the main challenge is now integration rather than pure hardware access. Many current software paths still depend on vendor-specific adapter chains between user SDKs, schedulers, and backend APIs. This pattern makes operations more complex than necessary and slows the transition from pilots to production workflows. We present a practical integration path centered on the Quantum Device Management Interface (QDMI). Using IQM superconducting systems as a hardware case study, we implement an IQM-backed QDMI layer and connect it to two software layers that HPC centers working with quantum computers already care about: Slurm-based job execution and Qiskit-facing user workflows. The implementation is publicly available at https://github.com/iqm-finland/QDMI-on-IQM. The key message is simple: integrating quantum hardware into HPC does not have to be a bespoke engineering effort for each backend. Once the software-hardware boundary is standardized, large parts of the stack become reusable across providers and deployment styles. Our results do not claim that standardization eliminates all HPCQC challenges. They show that this specific boundary can already be standardized today in a way that is practical for users, operators, and vendors. |
| title | Practical HPCQC Integration with QDMI: A Real-Hardware Case Study with IQM Systems |
| topic | Quantum Physics Emerging Technologies |
| url | https://arxiv.org/abs/2604.19869 |