-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to play custom pulses with QM #1100
Comments
Nope, it's just our fault, not really QM related... We need to name pulses for the upload, almost in every driver (actually, in all of them, ttbomk). Naming automatically is not completely trivial, and there are two main options:
Number 1. is cumbersome, since you need to always have access to a unique container, and grow it. Moreover, the second option is coming with the additional benefit of automatically deduplicating what we are uploading to the instrument (since identical pulses will have identical hashes). Unfortunately, NumPy arrays are unhashable by default, since they are mutable (thus unsuitable for places where hashes are typically used, e.g. What we can do is to manually define the |
Since there is already an indentier for pulses in |
After discussing offline, we've decided to fix the issue in the following way #1101
Using the pulse id doesn't work because it will duplicate the waveform for each pulse with the same waveform. |
The following code is failing using
main
.Here is the error.
I am guessing that the error might be caused by the fact that
Custom
accepts arrays which qm doesn't seems to like arrays when playing with custom pulses. Any ideas @alecandido @stavros11?The text was updated successfully, but these errors were encountered: