Skip to content
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

Autotune jules #3

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Autotune jules #3

wants to merge 2 commits into from

Conversation

julescraquelin
Copy link

Added 2 files to autotune a quantic circuit :

  • A script containing the class Autotune()
  • 2 files that serves as examples

@sjezouin
Copy link

Questions from a beginner in Pull Request :

  • can we remove all the commits that introduce personnal scripts of Manu ? These are indeed incompatible with the Autotune code so there is no reason to let them here.
  • there are many commits that I added on master a while ago. So should they be removed from this PR ?

Copy link

@nbourdau nbourdau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seb said:

* there are many commits that I added on master a while ago. So should they be removed from this PR ?

Yes, they should, they must be removed. The problem is that the content of external several branches rebased into the Autotune_Jules branch while they should not have.

I have not yet dived into the bulk the Autotune code but before starting we must have clean state:

  1. The autotune commit must start off from the QuanticParis master branch since it seems to be the main development branch. If it requires stuff from Manu's branches, they must be considered to be reviewed and merged into master.
  2. The history of development of Autotune does not matter as it is a single piece of code not requiring changes in pyEPR. Hence all commit regarding autotune should be squashed altogether.

I will go depeer in review in the commit days, but anyways, the comments I've just mentioned are orthogonal to the future comments I could makes so you can already start address them.

@nbourdau
Copy link

Also I would like to propose: what about doing some of the review of QuanticParis's pyEPR on http://gerrithub.io/ ?

Cherry-picked from Manu's work
Automatization of the tuning of a chip.

Recover and sort the HFSS data processed by pyEPR :
frequencies, Quality factors, Kers and Chis.

Defines a cost function with the user's criterion
and the previous HFSS data.

Fulfill the user's criterion by testing several values of
HFSS parameters until finding the zero of the cost function.
Current method is 'Bayesian Optimization' but please add
other methods.
@sjezouin
Copy link

In the end can we accept this PR ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants