Skip to content

Conversation

beckykd
Copy link
Collaborator

@beckykd beckykd commented Sep 22, 2025

Copy link

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

@abbycross abbycross added this to the 2025_11_14 QDC milestone Oct 7, 2025
@jyu00
Copy link
Collaborator

jyu00 commented Oct 7, 2025

We should also explain the X and Y axises in the generated figure. @RoyElkabetz is the following correct?

  • X axis is time in unit dt
  • Y axis is the channel
    • Receive channel is ???
    • Qubit x is the drive channel for qubit x
    • AWGRx_y (Arbitrary Wave Generator Readout) is used for readout channels communication for measuring qubits. The x and y arguments correspond to the readout instrument ID and the qubit number, respectively.
    • Hub controls broadcasting

Similarly, we should explain how to read the instructions on the figure - each instruction has the format of X_Y, where X is the name of the instruction and Y is the pulse type. A play type applies control pulses, and a capture records the qubit's state.

This would have been so much easier if we still have pulse library and can just point to that 😛

@RoyElkabetz
Copy link
Contributor

- X axis is time in unit dt
- Y axis is the channel
    - Receive channel is ???
    - Qubit x is the drive channel for qubit x
    - AWGRx_y (Arbitrary Wave Generator Readout) is used for readout channels communication for measuring qubits. The x and y arguments correspond to the readout instrument ID and the qubit number, respectively.
    - Hub controls broadcasting
  • So the X-axis is in units of hardware cycles, where each cycle should take a single dt of seconds, it may vary depending on the specific hardware you are using.
  • The Y-axis is for Channels. You can think of Channels as instruments that emit pulses.
  • The Receive channel is the only channel which is not an instrument by itself, it is an instruction which is played on all channels that are part of a communication procedure with the Hub in that moment in time.
  • All the rest of the statements are correct.

@mbhealy
Copy link
Contributor

mbhealy commented Oct 8, 2025

  • So the X-axis is in units of hardware cycles, where each cycle should take a single dt of seconds, it may vary depending on the specific hardware you are using.

This is what dt means, 1 dt == 1 scheduling cycle. dt is a defined increment of time and has unit seconds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

Wrong description of experimental.execution_path New page on timing visualization

6 participants