-
Notifications
You must be signed in to change notification settings - Fork 7
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
Fix bugs related to plotting #269
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #269 +/- ##
==========================================
- Coverage 36.26% 35.95% -0.32%
==========================================
Files 19 19
Lines 1456 1452 -4
==========================================
- Hits 528 522 -6
- Misses 928 930 +2
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
Thanks for fixing these issues. I tested after merging this to qmsweepers branch and spectroscopies, Rabi amplitude and length and allXY work for me.
For Ramsey I am still getting an error, now in builders.py update_platform_runcard
line 282, that int
cannot convert 1D array. It may be related to the fact that fitting failed and fits.csv does not have data for all qubits. It may be good to make this robust to fitting failures, because Ramsey fit fails quite often but we would still like to get the report.
I am now trying T1.
EDIT: More specifically what I have in mind is that update_platform_runcard
checks if fitting data exist for the qubit. If yes it proceeds as now, otherwise it could print a warning like "Fitting data for qubit {qubit} not found. Runcard was not updated." and proceed with the code without failing.
EDIT2: T1 seems to work too. So far the issue remains only for Ramsey.
@stavros11 you mean |
Sorry, I just saw this comment, I replied to the issue first. No, I am only using the normal |
except: | ||
log.warning("ramsey_fit: the fitting was not succesful") | ||
data_fit.add({key: 0 for key in data_fit.df.columns}) |
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.
This was the bug. For some reasons, when the fitting fails we were setting all the keys to 0 (including the qubit key). This can be very dangerous since you could have two columns with the same qubit.
Thanks for the clarification. |
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.
Thanks for the update, it appears to work now. Ramsey fit still fails for most qubits but the report is still generated.
Coverage is not passing because we are missing some tests for fitting methods. |
Closes #266.
Checklist: