How to handle different kinds of devices

[kayaercument]

Hello all 👋,

The number of QDMI devices is increasing. So far, we have IQM, DCDB, LRZ, and QLM's QDMI devices, and WMI's QDMI device will be available soon.

QLM is a simulator, LRZ and WMI are data centers, and DCDB is a database. These implementations are unique in their way. We encountered some problems with them. I would like to share them with you in order to improve the QDMI or the implementations.

1. QLM
   The problem we encountered is with the noise model. We used one custom parameter in the device session to flag if it is a noisy session, and two custom parameters in the job to define the noise model.

2. DCDB
   The problem is the parameterized querying. We started to develop ✨ QDMI Environment Implementation #154 a while back. I believe this led to more confusion and complexity. We need a better and more general solution.

3. LRZ
   The main problem is the hardware. Each device session requires hardware. Hence, we can initiate the QDMI device once and create multiple sessions to submit jobs to the hardware and query its properties.

My two cents are:

1. New device property: QDMI_DEVICE_PROPERTY_DEVICETYPE. The QDMI_device_session_query_device_property can query it and returns

• Simulator
• Database
• ISV
• Datacenter
• Quantum Accelerator.

2. New QDMI_PROGRAM_FORMAT_T: QDMI_PROGRAM_DATABASE_QUERY.
   To handle the job, new QDMI_DEVICE_JOB_PROPERTY_T entries:

• QDMI_DEVICE_JOB_DATABASE_TABLE
• QDMI_DEVICE_JOB_DATABASE_COLUMN
• QDMI_DEVICE_JOB_DATABASE_CONDITION

All the property entries can be strings, but I'm not sure how we can handle the condition.

3. New QDMI_DEVICE_SESSION_PARAMETER_T entries:

• QDMI_DEVICE_SESSION_PARAMETER_NOISEMODEL,
• QDMI_DEVICE_SESSION_PARAMETER_HARDWARE

What do you guys think?

FYI @burgholzer @ystade @mnfarooqi @echavarria-mqv

[echavarria-mqv]

@kayaercument: WMI is not a data center

[burgholzer]

Hey @kayaercument 👋🏼

Thanks for starting this discussion. I currently do not have all the answers for you (yet).
But we (@ystade and myself) are currently working on updates to QDMI that should make the realization of all three scenarios easier and cleaner.
We'll share updates once the respective work is consolidated a little more.