-
Notifications
You must be signed in to change notification settings - Fork 61
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
Move CPU fallback for frequencies #527
Conversation
I made some tests and the fix is working well, at least with the examples that were not working before. |
I also changed the warning log message after @stavros11 suggestion in PR qiboteam/qibojit#54. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, thanks.
Codecov Report
@@ Coverage Diff @@
## master #527 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 85 85
Lines 12284 12284
=========================================
Hits 12284 12284
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Can we merge this? |
Yes, I believe so. |
I moved the CPU fallback from
qibo.core.measurements.frequencies
toqibo.core.measurements._calculate_frequencies
, so that we call it with arguments and the CPU fallback implemented in PR qiboteam/qibojit#54 converts them, if needed.