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

No public access to actually used measurement windows #789

Open
terrorfisch opened this issue Aug 25, 2023 · 0 comments
Open

No public access to actually used measurement windows #789

terrorfisch opened this issue Aug 25, 2023 · 0 comments
Labels
Framework integration Covers the integration of qupulse in measurement and experimental frameworks Implementation

Comments

@terrorfisch
Copy link
Member

As #780 shows there is the requirement to get the measurement windows that correspond to the measured data in a convinient and stable way.

I think the best way is to add a get_measure_times(self, program_name) -> Tuple[np.array, np.array] to the DAC interface.

However, this is not a general solution because the DAC might perform some analysis that obscures how the measurement times are related with the actual output.

@terrorfisch terrorfisch added Framework integration Covers the integration of qupulse in measurement and experimental frameworks Implementation labels Oct 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Framework integration Covers the integration of qupulse in measurement and experimental frameworks Implementation
Projects
None yet
Development

No branches or pull requests

1 participant