You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The value for loop_cnt (set to awgs_0_userregs_0) in the prepare function for the UHFQC_correlation_detector is set to nr_averages*nr_sweep_points. This seems odd, as loop_cnt should be the number of averages the UHFQC should loop through.
Questions:
Are we using this detector function?
Is the value for loop_cnt correct?
The text was updated successfully, but these errors were encountered:
Yes we are using this detector.
The loop_cnt is wrong. It should be the same as it is in the UHFQC_integrated_average_detector.
The correlation detector has not been used with the new wfm generation framework. I believe in the old framework (where we were not uploading several RO pulse segments, but just one), this was of setting loop_cnt was needed.
@stephlazar@MichKe95 has this been fixed somewhere/ is now outdated?
If it has been fixed, please point to the relevant commit and if it is no longer relevant, we can close this issue.
The value for loop_cnt (set to awgs_0_userregs_0) in the prepare function for the UHFQC_correlation_detector is set to nr_averages*nr_sweep_points. This seems odd, as loop_cnt should be the number of averages the UHFQC should loop through.
Questions:
The text was updated successfully, but these errors were encountered: