What's the problem this feature will solve?
At this level, pulses are queried at a QDMI site.
The following queries are proposed for inclusion:
Query which pulse shape type is supported?
- Standard Pulse
- Arbitrary Pulse
Query available pulse shapes
- This returns the available pulse shapes and a list of QDMI sites that support this e.g. List(Tuple(QDMI_PULSE_SHAPE, List(QDMI_Site)))
- AND/OR QDMI_Site can be queried to return the available pulse shapes
Pulse properties that need to be queried are:
- Sample Duration: The length of a single sample.
- PI Pulse Duration: changes between each calibration cycle, refers to 1/rabi_frequency
- Amplitude Constraints i.e. min and max amplitude
- Carrier Frequency
- Trap Frequency : Laser frequency of particular trap
Describe the solution you'd like
A more concrete solution can be presented once the open question regarding whether pulse shapes are specific to a site/channel or global to the device has been answered.
What's the problem this feature will solve?
At this level, pulses are queried at a QDMI site.
The following queries are proposed for inclusion:
Query which pulse shape type is supported?
- Standard Pulse
- Arbitrary Pulse
Query available pulse shapes
- This returns the available pulse shapes and a list of QDMI sites that support this e.g. List(Tuple(
QDMI_PULSE_SHAPE, List(QDMI_Site)))- AND/OR
QDMI_Sitecan be queried to return the available pulse shapesPulse properties that need to be queried are:
- Sample Duration: The length of a single sample.
- PI Pulse Duration: changes between each calibration cycle, refers to 1/rabi_frequency
- Amplitude Constraints i.e. min and max amplitude
- Carrier Frequency
- Trap Frequency : Laser frequency of particular trap
Describe the solution you'd like
A more concrete solution can be presented once the open question regarding whether pulse shapes are specific to a site/channel or global to the device has been answered.