Skip to content
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

AcquisitionType.RAW Qblox driver #663

Closed
PiergiorgioButtarini opened this issue Nov 16, 2023 · 1 comment · Fixed by #728
Closed

AcquisitionType.RAW Qblox driver #663

PiergiorgioButtarini opened this issue Nov 16, 2023 · 1 comment · Fixed by #728
Assignees
Labels
Milestone

Comments

@PiergiorgioButtarini
Copy link
Contributor

Should be implemented the AcquisitionType.RAW in qblox drivers in order to execute routine such as time_of_flight_readout.

@aorgazf
Copy link
Member

aorgazf commented Dec 21, 2023

Hi @PiergiorgioButtarini
qblox supports raw waveform acquisition, they call it scope acquisition, but it has certain limitations:


        # Qblox qrm modules only have one memory for scope acquisition.
        # Only one sequencer can save data to that memory.
        # Several acquisitions at different points in the circuit will result in the undesired averaging
        # of the results.
        # Scope Acquisition should only be used with one acquisition per module.
        # Several readout pulses are supported for as long as they take place symultaneously.
        # Scope Acquisition data should be ignored with more than one acquisition or with Hardware Demodulation.

        # Software Demodulation requires the data from Scope Acquisition, therefore Software Demodulation only works
        # with one acquisition per module.

        # The data is retrieved by storing it first in one of the acquisitions of one of the sequencers.
        # Any could be used, but we always use 'scope_acquisition' acquisition of the default sequencer to store it.

Let's discuss these points together to see what can be done.

@PiergiorgioButtarini PiergiorgioButtarini linked a pull request Dec 26, 2023 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants