Michael Hucka

That's correct, but they asked if someone else could take it over; they didn't say to close it. Moreover, the associated issue is still open. Since this PR was auto-closed...

For reference, I'm copying here the image from [a comment by the original author](https://github.com/quantumlib/Qualtran/issues/853#issuecomment-2927824630) in issue #853 that shows a screenshot of the output produced by the code in this...

@jbolns With respect to the output produced by your code currently (c.f. previous comment above), let's step back a bit and review some conventions of these "musical score diagrams": -...

Just noting in passing that this issue could probably be closed, as it appears to have been taken care of.

Just noting here the recent GH update to MacOS runner names: https://github.blog/changelog/2024-08-19-notice-of-upcoming-deprecations-and-breaking-changes-in-github-actions-runners/

It looks like this was meant to be closed, but accidentally wasn't. Closing now. Please reopen if I made a mistake!

@MichaelBroughton Do you know whether this is still an issue?

Discussed in Cirq Cynq 2025-10-15: This looks like it can be closed. (It probably could have been closed some time ago and was simply not followed up on.)

@RevanthGundala would you be able to take a look at the merge conflicts?

To help people find ways to contribute, we will start labeling issues with [`good first issue`](https://github.com/tensorflow/quantum/issues?q=sort%3Aupdated-desc+state%3Aopen+label%3A%22good+first+issue%22) and [`no QC knowledge needed`](https://github.com/tensorflow/quantum/issues?q=sort%3Aupdated-desc+state%3Aopen+label%3A%22no+QC+knowledge+needed%22).