✨ Pulse Submission Interface

[mnfarooqi]

What's the problem this feature will solve?

The focus of this issue is job submission interface for the Pulse program to the device for execution.

Open questions:
What initial pulse format should be supported? OpenQasm 3.0?

How would one put in the feature of mid-circuit measurements in the pulse representation?

Describe the solution you'd like

In principle the Pulse-Level job submission should be same as a Gate-Level job. The only addition should be addition of a new enum in QDMI_PROGRAM_FORMAT_T
- e.g QDMI_PROGRAM_FORMAT_OPENPULSE or QDMI_PROGRAM_FORMAT_QIRPULSE

[HossamAhmed2]

Feel free to ignore this if it is not something we are interested in implementing. Still, it would be nice to support some sort of familiar visualisation for users to track their pulse operations. I showed one example from the IQM pulse documentation.

[burgholzer]

Feel free to ignore this if it is not something we are interested in implementing. Still, it would be nice to support some sort of familiar visualisation for users to track their pulse operations. I showed one example from the IQM pulse documentation.

That is not something to be handled by the QDMI interface. Higher levels of the stack are responsible for providing such functionality.

[HossamAhmed2]

Feel free to ignore this if it is not something we are interested in implementing. Still, it would be nice to support some sort of familiar visualisation for users to track their pulse operations. I showed one example from the IQM pulse documentation.

That is not something to be handled by the QDMI interface. Higher levels of the stack are responsible for providing such functionality.

Thanks for explaining. I thought it might be handled by the interface since IQM is already providing this visualization. We just need to specify if we need the pulse operations to be visualised or not.

[donsano33]

Feel free to ignore this if it is not something we are interested in implementing. Still, it would be nice to support some sort of familiar visualisation for users to track their pulse operations. I showed one example from the IQM pulse documentation.

That is not something to be handled by the QDMI interface. Higher levels of the stack are responsible for providing such functionality.

Thanks for explaining. I thought it might be handled by the interface since IQM is already providing this visualization. We just need to specify if we need the pulse operations to be visualised or not.

I think the visualization is not part of this, but an optional part of the stack.
What goes through the QDMI in both directions (if supported) should be the pulse representation. The visualization can then work with this format.