What's the problem this feature will solve?
At this level, pulses are queried on a channel.
We would need another type of abstraction: QDMI_Pulse_Channel. This would be similar to QDMI_Site and QDMI_Operation.
QDMI_Pulse_Channel
- ChannelType: e.g., DriveChannel, ReadoutChannel, …
- ID
- Constraints
The following queries are proposed to be included:
Query a list of QDMI_site that can be targeted by the channel.
Query list of predefined pulse shapes (QDMI_PULSE_SHAPE)
Pulse properties that need to be queried are:
- Sample Duration: The length of a single sample.
- Timing Constraints
- Granularity in dt: Minimum number of samples per pulse in dt
- Amplitude Constraints i.e. min and max amplitude
- Carrier Frequency
- Rise Time: Time required from minimal amplitude to max amplitude in dt
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 on a channel.
We would need another type of abstraction:
QDMI_Pulse_Channel. This would be similar toQDMI_SiteandQDMI_Operation.QDMI_Pulse_Channel- ChannelType: e.g., DriveChannel, ReadoutChannel, …
- ID
- Constraints
The following queries are proposed to be included:
Query a list of
QDMI_sitethat can be targeted by the channel.Query list of predefined pulse shapes (
QDMI_PULSE_SHAPE)Pulse properties that need to be queried are:
- Sample Duration: The length of a single sample.
- Timing Constraints
- Granularity in dt: Minimum number of samples per pulse in dt
- Amplitude Constraints i.e. min and max amplitude
- Carrier Frequency
- Rise Time: Time required from minimal amplitude to max amplitude in dt
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.