Skip to content

Conversation

@beckykd
Copy link
Collaborator

@beckykd beckykd commented Jan 29, 2026

@qiskit-bot
Copy link
Contributor

One or more of the following people are relevant to this code:

  • @jakelishman
  • @miamico

]
```

You can also use a visualization (requires plotly) to help understand the timing. Use the sliders at the bottom, the controls at the top (hover over the image to reveal these), and the legend on the side of the output to customize the view.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this figure actually have anything to do with stretch? If not, then we should just add a Next steps section that points to the circuit schedule visualization page, and/or mention that page there (but not the figure).

If this figure has something to do with stretch, then we need to explain because it's not very obvious...

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It does - I'll ask Kavya to help me explain it.

Copy link

@KavyaVarma KavyaVarma Jan 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The visualization is useful to verify that the starts and ends of delay regions match the returned Stretch values (if you hover over the right elements and calculate the duration of white spaces in the plot).
Although - I'm not sure the image here is conveying this. Maybe something that specifically corresponds to the stretch values above would be helpful?

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.

Add info on returned stretch values

4 participants