-
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
Improvements to ActionBuilder
#271
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #271 +/- ##
==========================================
+ Coverage 36.57% 36.74% +0.17%
==========================================
Files 44 44
Lines 3027 3029 +2
==========================================
+ Hits 1107 1113 +6
+ Misses 1920 1916 -4
Flags with carried forward coverage won't be shown. Click here to find out more.
|
@wilkensJ when you have time could you please check this PR? |
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.
So in general multiple things will happen in the next PR, which @vodovozovaliza and me are working on right now, this will also influence this PR:
- Use a global function for aggregate action function, because many module are sharing the same structure and functions, we will put them in the folder
basics
- The amount of fitting parameters will be flexible
- The plotly figure generation will be a bit different
Thanks for the feedback @wilkensJ. |
I think in the After the adjustments I (partially) left in the review comments (not the change from always Of course also this needs some adjustments (the width of the table is not ideal, I put it to 50%, the spacing between the plots is too big, this is fixed in #293, also there will be titles for the legend, thanks to Liza, also the naming of the table is not idea now) |
As I see it, one of the main features added to the Regarding the adjustments to the |
If you and @vodovozovaliza are going to modify a few things, to me it is fine. |
Hello Andrea, I would like to ask if you had a chance to look at the comments in the PR as they are still marked as pending. I am sorry if any of the comments lead to misunderstanding, if something is not helpful or confusing in any way, I will be glad to clarify it. Please let us know what we (@vodovozovaliza and me) can do such that we can merge this PR, sorry again for any confusion. |
Hi @wilkensJ, |
Hello @andrea-pasquale, thank you very much for the improvements to the |
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
Co-authored-by: Andrea Pasquale <[email protected]>
Co-authored-by: Andrea Pasquale <[email protected]>
Co-authored-by: Andrea Pasquale <[email protected]>
Co-authored-by: Andrea Pasquale <[email protected]>
NIGSC changes
@wilkensJ @vodovozovaliza after the fixes from #318 this should be ready to merge, right? |
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 very much @andrea-pasquale, everything looks good to me here
src/qibocal/cli/utils.py
Outdated
"""Generation of qq output folder | ||
Args: |
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.
Here has to be an empty line, right?
Hello @andrea-pasquale, I hope I did not mess up my review, I resolved the comment which are outdated, was that okay? Or is it making things complicated? There are two comments I did not resolve. It would be great if you could implement them. For example if this runcard is run: backend: numpy
qubits: [0,1,2]
actions:
simulfilteredrb:
nqubits: 3
depths: [1,3,5,7,10]
runs: 2
nshots: 1024
noise_model: PauliErrorOnAll
noise_params: [0.01, 0.01, 0.01] There will be three reports of the same plots. |
Co-authored-by: vodovozovaliza <[email protected]>
Thanks for the review @wilkensJ and @vodovozovaliza. |
The examples in the documentation will be outdated once the branch is merged. Is it okay if I create a separate PR for them when we merge this PR? |
This PR adds some improvements to the
ActionBuilder
includingI'm keeping this PR as draft for the moment since I also want to fix #267 here.
EDIT
Other things fixed by this PR:
Checklist: