-
Notifications
You must be signed in to change notification settings - Fork 17
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
Remove offset initialization in QCM_BB #686
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #686 +/- ##
==========================================
+ Coverage 63.25% 63.58% +0.33%
==========================================
Files 48 49 +1
Lines 6596 6539 -57
==========================================
- Hits 4172 4158 -14
+ Misses 2424 2381 -43
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@PiergiorgioButtarini to simplify the review, is this PR still draft (meaning you are planning to work on it), ready or superseded by #702? I am asking because it is modifying the cluster which we are then removing, so there may be conflicts depending on how we merge these. |
Is it still draft, me and @alecandido will work on it in the next days. So maybe it will be useful if in the meantime we can merge #702. |
@stavros11 I would consider this at an early stage, while #702 is complete or close to completion. If there is any conflict, it will be fixed in here. |
for more information, see https://pre-commit.ci
…o remove_offset_setup
After the latest commits (especially b7a1efc) I would consider this as ready for review. |
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 @PiergiorgioButtarini, looks good to me and it works, only a minor comment below.
One issue before merging: did you try to run pytest
on qpu? I get the following error:
@pytest.fixture(scope="module")
def connected_qcm_rf(connected_controller, connected_cluster):
E fixture 'connected_cluster' not found
maybe this fixture is not properly defined? The errors are only in the qblox tests, the platform and backend tests are working.
@PiergiorgioButtarini before merging, it would be useful to also have a working runcard for this PR and testing it on hardware. E.g. the |
I used the qw5q_gold platform from the remove_offset branch of qibolab_platforms_qrc to test this on hardware. QPU tests are failing with the error I wrote above but other than that, it seems to work. |
Co-authored-by: Stavros Efthymiou <[email protected]>
Thanks @alecandido, as Stavros said there are already runcards to test it. |
This is because now the cluster object doesn't exist anymore. I'll fix the tests asap, thanks for spotting it. |
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.
Thank you for the updates, tests are now passing.
Thanks for the review @alecandido , I implemented your suggestions in the last commit. |
@PiergiorgioButtarini thanks for the updates, could you also please fix the conflict? |
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 @PiergiorgioButtarini, we can merge.
When you apply the comments (or solve them anyhow) close the corresponding conversation, to better keep track of things that are still opened (and, if possible, just add a final comment with the hash of the commit solving it).
Thanks for the suggestion, I'll be more organized next time and I will follow this tips! |
@PiergiorgioButtarini also after merging this, please remember to update the platforms in the qrc repository for the API changes so that they work when we cool down. |
Since the offset is already initialized as the qubit sweetspot this setting was removed from the runcard.
This PR introduce a
ClusterModule(Instrument)
class from which each module inherits, in order to describe some common properties between the three modules.Checklist: