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

FIX #17/#26 #32

Merged
merged 1 commit into from Aug 30, 2016
Merged

FIX #17/#26 #32

merged 1 commit into from Aug 30, 2016

Conversation

mfeurer
Copy link
Contributor

@mfeurer mfeurer commented Aug 29, 2016

Supersedes #31

Fixes #17 and #26 (together with the latest version of the config space).

@mfeurer
Copy link
Contributor Author

mfeurer commented Aug 29, 2016

@mlindauer @KEggensperger please review and comment on this. @mlindauer if you agree on this, can you please close #31?

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.05%) to 62.523% when pulling 1b9b1e8 on fix/#17/#26 into efe9cc0 on development.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.05%) to 62.523% when pulling 1b9b1e8 on fix/#17/#26 into efe9cc0 on development.

@mlindauer
Copy link
Contributor

Hi,

Thanks for the fix. It is working with my examples and the code should be fine.

However, I would like to propose a further change (because of efficiency and consistency).
The method Runhistory.get_runs_for_config() should get the config_id of config and compare the ids in the if-statement.
Comparison of int should be more efficient and we only need one dictionary access (instead of many in Line 111). Furthermore, it is more consistent to use also here the config_id as we do it also in objective._cost()

Cheers,
Marius

@mfeurer
Copy link
Contributor Author

mfeurer commented Aug 30, 2016

Would it be okay to add this as an issue and solve in a separate PR?

@mlindauer
Copy link
Contributor

Would it be okay to add this as an issue and solve in a separate PR?

Yes.
I thought it is very related to your fix and it reduces the overhead to create again another PR with an additional review phase.

@mlindauer
Copy link
Contributor

Ok, I will submit a PR for #35, after this PR was merged.

There is no "approve" button in Github?

Cheers,
Marius

@mfeurer
Copy link
Contributor Author

mfeurer commented Aug 30, 2016

Correct, there is no "approve" button. We could adapt the scikit-learn policy of changing the PR names like this:

  • [WIP] name: pull request is work in progress
  • name: pull request is ready to be reviewed
  • [MRG] name: pull request is approved by one reviewer
  • [MRG+2] name: pull request is approved by two reviewers.

@KEggensperger
Copy link
Contributor

approved

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.

None yet

4 participants